On Thursday 30 March 2006 20:34, John Maddock wrote:
> > with information about *using* header-only
libraries, as opposed to
> > declaring them.
>
> What advantage does that have over just
<include>path-to-boost ?
>
> In any case it completely misses the point: I know
where Boost is on my
> machine, I don't know where it is on someone elses
machine (who may be
> running my examples). bjam on the other hand *does*
know where boost is,
> because it's located the build system. It's that
information I want to
> pull out.
So, you want Boost.Build to get Boost root directory based
on the path where
Boost.Build itself is found.
That can be made to work, but:
1. It will break if your users happen to use system-wide
Boost.Build. FWIW,
there's already Boost.Build package for Debian, and users
might install it
from source themselfs too.
2. This will work only for Boost, but not for any
third-party libraries.
The general solution seems to either set some environment
variable what will
be read by Jamroot, or hardcode paths in Jamroot and modify
Jamroot when you
move the source to a different machine.
- Volodya
--
Vladimir Prus
http://vladimir_pru
s.blogspot.com
Boost.Build V2: http://boost.org/boost-
build2
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|