This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFA 1/2] do not use python<version> subdir when including Python .h file

From: Tom Tromey <tromey at redhat dot com>
To: Joel Brobecker <brobecker at adacore dot com>
Cc: gdb-patches at sourceware dot org
Date: Fri, 28 Jan 2011 07:36:50 -0700
Subject: Re: [RFA 1/2] do not use python<version> subdir when including Python .h file
References: <1295739863-1006-1-git-send-email-brobecker@adacore.com> <1295739863-1006-2-git-send-email-brobecker@adacore.com> <m34o8ti8a5.fsf@fleche.redhat.com> <20110128140947.GB2467@adacore.com>

Tom> How does this work when srcdir != builddir?  In that case isn't our
Tom> python.h found only via a -I option?  Thus causing a clash?

Joel> I discovered while working on this that there is actually no -I option
Joel> for the gdb/python directory (I thought that we did and I was looking
Joel> at that in an attempt to eliminate it).  Files from the gdb/ directory
Joel> include our python headers using #include "python/python-internal.h",
Joel> while files in the gdb/python/ directory include them more directly
Joel> using #include "python-internal.h". 

Aha, that's what I was forgetting.
Thanks.

Tom

References:
- Allow building GDB with Python support on Windows/MinGW
  - From: Joel Brobecker
- [RFA 1/2] do not use python<version> subdir when including Python .h file
  - From: Joel Brobecker
- Re: [RFA 1/2] do not use python<version> subdir when including Python .h file
  - From: Tom Tromey
- Re: [RFA 1/2] do not use python<version> subdir when including Python .h file
  - From: Joel Brobecker

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]