Re: [Boost-build] RFC: Rootless projects..

Subject: Re: [Boost-build] RFC: Rootless projects..
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-06-17 14:00:29

Aaron,

On 6/16/2015 6:08 PM, aaron_at_[hidden] wrote:
> I have two use cases for such a feature:
>
> 1) In order to test our custom boost.build jam library I have created a repo that contains boost.build as a
> submodule as well as submodules for all of the tools and extra libs that it needs. I am using BoostBuild.py
> <http://BoostBuild.py> for the system testing which creates the temp files in the temp directory. The directory
> structure of each is similar to the following:
>
> some/where/to/test_repo/
>      boost.build/
>      libs/
>          some_lib/
>              build.jam
>      tests/
>      tools/
>
> dynamically/created/directory/to/temp/TestProject/
>      Jamroot.jam
>      tests/
>          build.jam
>          my_test/
>              build.jam
>
> Our jam library provides support for our unit testing framework. That framework exists in
> test_repo/libs/some_lib and there is a use-project that points to the build.jam in that framework. In order to
> be able to call use-project on some_lib's build.jam, a Jamroot.jam must exist somewhere in its parent hierarchy.
> I currently have created an empty Jamroot.jam in the test_repo to satisfy that condition.

I suppose it's possible to create Jamroot under libs/some_lib?

>
> 2) In the event that I want to make a library available to install via a package manage (like apt-get) and
> provide boost.build support, it would be nice to include a build.jam with that library. The way it currently
> stands, i would also have to create a wrapper directory structure that contains a Jamroot.jam so that I can
> actually point to the library's build.jam

Or you can also put an empty Jamroot.jam alongside build.jam, or just put everything into Jamroot.jam?

Thanks,
Volodya