Boost.Build commit heads up
Here is the commit message for revision 86392: Add Boost.Build support for the Git modular layout, using links to to new header locations, thus preventing breakage to vast amounts of user code and build setups. Being added to SVN so that changes will automatically propagate to Git and modular Boost. Thanks to Steven Watanabe, Jürgen Hunold, Vladimir Prus, and Bjørn Roald for developing this patch. Steven in particular conceived the approach and did the initial implementation, which was further refined by the other contributors. In theory this commit won't break any existing boost builds. To verify that, on Win 7 and Ubunto I've done a fresh SVN checkout of trunk and verified bootstrap.bat, bootstrap.sh, and a b2 build work both before and after the patch is applied. On Windows, I verified that after the patch is applied a b2 build using an unpatched prior compilation of b2 still works. These tests increase confidence that committing the patch to trunk now isn't likely to cause breakage, but please post to this list right away if you spot any build breakage or other odd behavior. The files modified are listed below. Thanks, --Beman Modified: D:\boost\trunk\Jamroot Modified: D:\boost\trunk\libs\geometry\index\example\Jamfile.v2 Modified: D:\boost\trunk\libs\numeric\odeint\examples\vexcl\Jamfile.v2 Modified: D:\boost\trunk\libs\parameter\doc\html\index.html Modified: D:\boost\trunk\libs\parameter\doc\index.rst Modified: D:\boost\trunk\libs\python\example\Jamroot Modified: D:\boost\trunk\libs\python\example\quickstart\Jamroot Modified: D:\boost\trunk\libs\python\example\tutorial\Jamroot Modified: D:\boost\trunk\libs\signals2\example\Jamfile.v2 Modified: D:\boost\trunk\libs\spirit\example\qi\json\build\Jamfile Modified: D:\boost\trunk\libs\units\test\Jamfile.v2 Modified: D:\boost\trunk\tools\Jamfile.v2 Modified: D:\boost\trunk\tools\regression\build\Jamroot.jam
On Tue, Oct 22, 2013 at 5:35 PM, Beman Dawes <bdawes@acm.org> wrote:
These tests increase confidence that committing the patch to trunk now isn't likely to cause breakage, but please post to this list right away if you spot any build breakage or other odd behavior. The files modified are listed below.
Are VS2013 build reports helpful too or is it out of scope right now?
On Tue, Oct 22, 2013 at 12:30 PM, Klaim - Joël Lamotte <mjklaim@gmail.com>wrote:
On Tue, Oct 22, 2013 at 5:35 PM, Beman Dawes <bdawes@acm.org> wrote:
These tests increase confidence that committing the patch to trunk now isn't likely to cause breakage, but please post to this list right away if you spot any build breakage or other odd behavior. The files modified are listed below.
Are VS2013 build reports helpful too or is it out of scope right now?
In scope, particularly if it is related to this patch. --Beman
AMDG On 10/22/2013 08:35 AM, Beman Dawes wrote:
These tests increase confidence that committing the patch to trunk now isn't likely to cause breakage, but please post to this list right away if you spot any build breakage or other odd behavior. The files modified are listed below.
I think there was at least one file in the patch (libs/Jamfile.v2) that needs to be svn added. (This shouldn't affect svn, but dependency tracking won't work correctly in git without it)
Modified: D:\boost\trunk\Jamroot Modified: D:\boost\trunk\libs\geometry\index\example\Jamfile.v2 Modified: D:\boost\trunk\libs\numeric\odeint\examples\vexcl\Jamfile.v2 Modified: D:\boost\trunk\libs\parameter\doc\html\index.html Modified: D:\boost\trunk\libs\parameter\doc\index.rst Modified: D:\boost\trunk\libs\python\example\Jamroot Modified: D:\boost\trunk\libs\python\example\quickstart\Jamroot Modified: D:\boost\trunk\libs\python\example\tutorial\Jamroot Modified: D:\boost\trunk\libs\signals2\example\Jamfile.v2 Modified: D:\boost\trunk\libs\spirit\example\qi\json\build\Jamfile Modified: D:\boost\trunk\libs\units\test\Jamfile.v2 Modified: D:\boost\trunk\tools\Jamfile.v2 Modified: D:\boost\trunk\tools\regression\build\Jamroot.jam
In Christ, Steven Watanabe
Hi Steven, On Tuesday, 22. October 2013 10:17:28 Steven Watanabe wrote:
On 10/22/2013 08:35 AM, Beman Dawes wrote:
These tests increase confidence that committing the patch to trunk now isn't likely to cause breakage, but please post to this list right away if you spot any build breakage or other odd behavior. The files modified are listed below.
I think there was at least one file in the patch (libs/Jamfile.v2) that needs to be svn added. (This shouldn't affect svn, but dependency tracking won't work correctly in git without it)
Thanks for spotting this. Added in 86398. Now waiting for the commits to be converted. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany
On Tue, Oct 22, 2013 at 3:19 PM, Jürgen Hunold <jhunold@gmx.eu> wrote:
Hi Steven,
On Tuesday, 22. October 2013 10:17:28 Steven Watanabe wrote:
On 10/22/2013 08:35 AM, Beman Dawes wrote:
These tests increase confidence that committing the patch to trunk now isn't likely to cause breakage, but please post to this list right away if you spot any build breakage or other odd behavior. The files modified are listed below.
I think there was at least one file in the patch (libs/Jamfile.v2) that needs to be svn added. (This shouldn't affect svn, but dependency tracking won't work correctly in git without it)
Thanks for spotting this. Added in 86398.
And thank you for taking care of that.
Now waiting for the commits to be converted.
And doubly so because the gitflow branch names change has now been applied by Daniel, and the svn revision number added to commit history by Dave. Note that since the patches were applied to trunk, but not yet to branches/release, they will show up in modular boost develop but not master. I'll merge 86392 and 86398 to release on Thursday, assuming no serious bug reports surface. --Beman
2013/10/22 Beman Dawes <bdawes@acm.org>:
On Tue, Oct 22, 2013 at 3:19 PM, Jürgen Hunold <jhunold@gmx.eu> wrote:
Now waiting for the commits to be converted.
And doubly so because the gitflow branch names change has now been applied by Daniel, and the svn revision number added to commit history by Dave.
Note that since the patches were applied to trunk, but not yet to branches/release, they will show up in modular boost develop but not master.
The conversion now successfully finished.
participants (5)
-
Beman Dawes -
Daniel Pfeifer -
Jürgen Hunold -
Klaim - Joël Lamotte -
Steven Watanabe