Re: [Boost-build] bbv2: Multiple lib rules per project not possible?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-07-25 01:47:09

On Monday 24 July 2006 20:47, Roland Schwarz wrote:
> Vladimir Prus wrote:
> > If explanations there makes no sense, please post the complete
> > Jamfile.v2, as attachment, and I'll take a look.
>
> As it turned out I was studying an old version of the bbv2
> documentation. Thank you for having me pointed to the current one.
>
> Altough departing from your initial suggestion I would kindly ask you to
> have a look onto and comment the following attempt to solve the problem:
>
> import feature ;
> feature.feature platform : native pthread :  ;
...
> lib boost_thread_pthread
>
> 	: ## sources ##
>
> 	    pthread/thread.cpp
> 	    pthread/mutex.cpp
> 	    pthread/condition.cpp
> 	    pthread/exceptions.cpp
> 	    pthread/xtime.cpp
>
> 	: ## requirements ##
>
> 	    <platform>pthread
> 	;
>
> lib boost_thread
>
> 	: ## sources ##
>
> 	    linux/thread.cpp
> 	    linux/mutex.cpp
> 	    linux/condition.cpp
> 	    linux/exceptions.cpp
> 	    linux/xtime.cpp
>
> 	: ## requirements ##
>
> 	  <platform>native # native is default and may be omitted
> 	;

I see nothing particularly wrong with this approach. However, please give the 
feature some more obvious name, like "threading_platform". Just "platform" 
can mean so many things.

In fact, I don't see how that feature can affect anything ;-) And feature with 
a fixed set of values should probably have "propagated" attribute, but I'm 
not sure if that matters in this case, where you invent a feature just for 
one target.

- Volodya