Boost logo

Boost-Build :

From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2004-10-14 03:25:19


Vladimir Prus wrote:
>
> I've just made a final (I hope) tweak to the "lib" rule. Now it's possible to
> do
>
> lib png : z : <name>png ;
> lib z : : <name>z ;
>
> or
>
> lib png : z : <file>png.a ;
> lib z : : <file>z.a ;
>
> and if you link to 'png', the 'z' library will be picked up too. Previously,
> this required non-intuitive syntax.
>
> At the same time, the prebuilt.jam module which used to implement <file> was
> removed. The <file> feature now works only for "lib" targets, and you should
> use "alias" in other cases

What if one uses <file> and <name>? Would'nt it be more consistent to
have <path> and <name>. This way there is no overlap between the two
properties. The <path> only needs to be used if the library is not in
the default path and than will be passed as a -L option.

>
> Finally, I've expanded the documentation on libraries (and other builtin
> rules):
>
> http://boost.org/boost-build2/doc/html/bbv2.advanced.builtins.targets.html

In the first example on that page:

<quote>
exe hello : hello.cpp some_library.lib /some_project//library
: <threading>multi
;
<unqoute>

using 'some_library.lib' suggest to me that for library dependencies,
one needs to specify the real name of the library (with the file-name
extension which is '.lib' on windows) instead of the target-name
corresponding to the library.

Anyway the documentation is really improving!!! Keep up the good work!!!

 


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk