Re: third-party library dependencies

AMDG

On 05/20/2018 02:03 PM, Stefan Seefeld via Boost-build wrote:
> 
> I'm trying to add a few library dependencies to a (boost) project.
> https://boostorg.github.io/build/tutorial.html#best_practices explains
> how to add
> 
> lib xml : : <name>libxml <search>C:/lib : : <include>C:/include ; 
> 
>   to a user-config.jam file, then use it from a Jamfile via
> `<library>/user-config//xml`. This approach seems to require the
> user-config.jam file to contain a call to `lib xml`. Is there a way to
> make that optional (so a default `xml` target gets instantiated with
> default paths, only to be overridden if any custom paths or requirements
> are needed ? Or would that require an `xml` module to be created, as is
> done for a few other third-party packages b2 has builtin support for
> (zlib, libpng, etc.) ?
> 

  You really should use a module.  All the module needs to
do is wrap up the logic for tracking whether the target
has been created yet.  The lib rule is not really designed
to handle this.  Hypothetically, I suppose you could make
a module that searches config files for targets.

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