On Friday 19 October 2007 02:20:10 Darren Kessner wrote:
> Hi all,
>
> I've just about finished the Boost.Build setup for my
> project -- I'm now successfully building my codebase on
Windows
> (msvc and gcc/cygwin) and on a few different types
> of Linux (gcc). I'm extremely happy with how simply
the
> various project and external dependencies can be
expressed in the Jamfiles.
>
> I have a couple of questions:
>
> 1) I have a number of <toolset>-conditional
requirements in my Jamfiles.
> When I build on Linux, Boost.Build complains about any
<toolset>msvc:<property>...
> The workaround is to include "using msvc ;"
in my user-config,
> but this seems odd since obviously msvc isn't
installed. Is there a better way to handle this?
I believe such better way might be to use either Milestone
12 release or nightly
built version -- I believe it has special code to not care
about undefined properties
in conditional requirements.
>
> 2) I have a library that should only be built with
msvc --
> how do I tell Boost.Build to exit gracefully when
> someone tries to build that library with gcc?
<toolset>gcc:<build>no
Again, use M12 for better results -- M11 might not even have
<build>no.
It would be nice to express this like:
<toolset>!msvc:<build>no
but we don't such syntax yet.
- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
