Re: boost-build support for pre-built boost libraries?

Another subtle issue:

on linux this usually would imply to copy a file with name
Jamroot to 
/usr/lib, right?

I don't think this would be a good idea. Jamroot might clash
with other 
libs, once Boost.Build is getting better recognized as a
cross platform 
build tool.

Would a different Name be possible? Say e.g. BoostJamroot.
(I am asking this because I believe only Jamfile and Jamroot
are allowed 
for this purpose.)

Roland

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Roland Schwarz wrote:

> Another subtle issue:
> 
> on linux this usually would imply to copy a file with
name Jamroot to
> /usr/lib, right?

No, to /usr/share/boost/Jamroot
 
> I don't think this would be a good idea. Jamroot might
clash with other
> libs, once Boost.Build is getting better recognized as
a cross platform
> build tool.
> 
> Would a different Name be possible? Say e.g.
BoostJamroot.
> (I am asking this because I believe only Jamfile and
Jamroot are allowed
> for this purpose.)

Per above, 'boost' is encoded in directory path, so no
confusion. The
only problem is that Boost N and Boost M are both installed,
and naming
scheme is different in Boost N and Boost M. But I don't
think we should
bother about that.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build