I tried to use <include> in the jam file, as part of the toolset definition, but it didn't work - maybe I didn't do it correctly.
Here's how I tried to do it:

using android : x86 : $(NDK_PATH)/toolchains/x86-4.4.3/prebuilt/linux-x86/i686-android-linux/bin/c++ :
<archiver>$(NDK_PATH)/toolchains/x86-4.4.3/prebuilt/linux-x86/i686-android-linux/bin/ar
<include>$(NDK_PATH)/platforms/android-9/arch-x86/usr/include
...

But the <include> directive was ignored - the include directory did not appear in the compilation. Should it be placed outside the toolset definition (maybe above it)?

It works fine when I provide it on the bjam command line using "include=", but since this include path must be specified whenever I use this toolset, I'd like it to be specified as part of the toolset.

Shlomy


On Fri, Aug 5, 2011 at 10:24 AM, Holger Joukl <Holger.Joukl@lbbw.de> wrote:
Hi,

> I'd like to specify an include path to be used by the compiler. I
> tried to use:
>        <compileflags>-I...
> where "-I" specifies an include directory, but "bjam" seems to
> ignore it and omit it from the compilation (all other compileflags
> are passed correctly).
>
> Is there a way to specify the include path as part of the toolset,
> so I don't need to specify it on each build command (using
"include=...")?

You can use <include> directives in your Jam file:

<include>/path/to/headers

IIRC you can also use it as a command line feature arg to bjam, like
include=-I/path/to/headers.

Holger

Landesbank Baden-Wuerttemberg
Anstalt des oeffentlichen Rechts
Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz
HRA 12704
Amtsgericht Stuttgart

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build