Hi, Vladimir Prus wrote:

I know your message talks about V1, but with V2 this is a simple as:

install install-boost-libs-you-want : <path-to-boost>/libs/signals/build//boost_signals : <location>some-directory ;

for multiple variants:

install install-boost-libs-you-want : <path-to-boost>/libs/signals/build//boost_signals/<variant>release <path-to-boost>/libs/signals/build//boost_signals/<variant>debug : <location>some-directory ;

Thanks for the hint. I have tried it out with the Boost.Buildv2 that ships with 1.33.0 but unfortunately there were some problems: 1) examples/echo doesn't build at all 2) boost toplevel doesn't build because of an issue in iostreams 3) boost/libs/signals builds only a single subvariant and I couldn't figure out how to build all the others 4) contrary to v1 when I build in a subproject (like signals) v2 seems to always complain about missing python, ICU etc. Unless these are grave failures on my part (I've followed the documentation on boost.org which seems to be a bit outdated) I will presumably stay with v1 and more so because Rene Rivera provided me the clue I needed to get going. cheers, aa -- Andreas Ames | Programmer | Comergo GmbH | Voice: +49 69 7505 3213 | andreas . ames AT comergo . com