Re: [Boost-build] Language specific include paths

Subject: Re: [Boost-build] Language specific include paths
From: Robert (r.firl_at_[hidden])
Date: 2018-02-23 15:49:36

On 2/19/2018 12:39 PM, Steven Watanabe via Boost-build wrote:
> AMDG
> 
> On 02/19/2018 11:03 AM, Robert via Boost-build wrote:
>>
>> I would like to add that in order for zlib to successfully be part of
>> the build, I have to use option "-s" on the b2 invocation:
>>
>> -s ZLIB_SOURCE="E:\ZLibSource\zlib-1.2.11" -s
>> ZLIB_INCLUDE="E:\ZLibSource\zlib-1.2.11"
>>
> 
> ZLIB_SOURCE is enough.  ZLIB_INCLUDE is actually
> ignored if you pass ZLIB_SOURCE.

On my next build, I will remove the ZLIB_INCLUDE and update this thread 
with the results.

> 
>> Whether I can now build with zlib via user-config.jam, I have not tested
>> it since roughly Boost 1.62.  Keep in mind that I construct Boost for
>> two different Windows compilers on Windows 8.1 Pro, x64 (e.g. Microsoft
>> and Intel C++).
>>
> 
> The problem is that the library name is not mangled, right?
> This can be worked around by setting a <tag> rule that
> does the mangling (with -s, it's added implicitly by
> Boost.IOStreams).
> 
> I just tried:
> 
> import boostcpp ;
> using zlib : : <source>C:/path/to/zlib <tag>@boostcpp.tag ;
> 
> but that breaks because boostcpp.jam has bugs that
> prevent it from being imported outside of Boost's
> Jamroot.

I suppose the importing outside of Boost's Jamroot bug is the reason 
zlib fails via user-config.jam.  Regardless, I am perfectly happy using 
the command line option.  It always succeeds with zlib-Boost output 
files. :)

Thank you very much for your help. I appreciate your knowledge and feedback.

> 
> In Christ,
> Steven Watanabe
> _______________________________________________
> Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
>