|
Boost-Build : |
From: Ilya Sokolov (fal_delivery_at_[hidden])
Date: 2006-05-12 05:41:37
Hello, Brian!
you wrote:
> In simp_envelopes/Jamfile I have this:
> ------------
> project simplify-libs
> : usage-requirements <include>simp_envelopes
> ;
>
> lib simplify : [ glob *.cc ]
> : <include>simp_envelopes ;
> ------------
> which I believe should tell my_libs to include
> simp_envelopes/simp_envelopes, if only my_libs can know that it should
> depend on the simp_envelopes project.
you right
> My my_libs Jamfile:
> ------------
> project my_libs
> : requirements <include>../simp_envelopes
> : usage-requirements <include>include
> ;
>
> lib my_libs : [ glob *.cc ] /simplify-libs//simplify
> : <include>include
> ;
> -------------
> I had to add the requirements <include>../simp_envelopes for my_libs
> to find the include files for simp_envelopes... is there a way to get
> my_libs to depend on simp_envelopes (or simplify-libs) and take care
> of this automatically?
We have this feature already, so you dont need `: requirements
<include>../simp_envelopes' in the example above
> Finally, I have defined a library name open-mesh to point to my
> external library, but I don't know how to have my my_libs essentially
> require linking against open-mesh. This is in fact even more
> important because I don't currently have a way of making my
> application build rule depend on open-mesh.
place open-mech to my_libs source list
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