Well that's it. Isn't it?
IMHO this example or something like should be considered for mentioning in some documentation. It's clear, a bit tricky and real.
And bjam solves it. With some Jurko help of course.
By the way is there a place where to have a complete list of <features>. I am well aware I am missing a lot of them.
Hi.Hmmm... how about something like:
I tried this:
project boost : requirements
<address-model>
: usage-requirements <include>"C:\\Program Files
(x86)\\Boost\\include\\boost-1_35" <library-path>"C:\\Program Files (x86)\\Boost\\lib"
;
project boost : requirements
<address-model>32
: usage-requirements <include>"C:\\Program Files
(x86)\\Boost\\include\\boost-1_35" <library-path>"C:\\Program Files (x86)\\Boost\\lib"
;
project boost : requirements
<address-model>64
: usage-requirements <include>"C:\\Program Files\\Boost\\include\\boost-1_35" <library-path>"C:\\Program Files\\Boost\\lib"
;
alias program_options : # no sources
: # no build requirements
: # no default build
: # no additional usage requirements
;
> <address-model>32:<library-path>"C:\\Program Files (x86)\\Boost\\lib"
> project boost
> : usage-requirements
> <include>"C:\\Program Files
> (x86)\\Boost\\include\\boost-1_35"
> <address-model>64:<library-path>"C:\\Program Files\\Boost\\lib"
> ;
Or you might actually mean requirements instead of usage-requirements here.
Note that I have not read the whole thread so I might be off the mark here, in which case - just ignore my blabbering... :-)
Best regards,
Jurko Gospodnetiæ
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build