boost modularization questions
Hi all, Out of curiosity, is the plan to move to a git pull-request model once the modularization process is complete? Or is github being used simply as a convenient mirror and interface for browsing code and history? Also, I have some changes to the Jamroot and boostcpp.jam files for improving modularization builds, which aggregate all the public headers from modules into the standard boost/... layout within the install/include directory, as well as implicitly setting up include paths during the initial build process. https://github.com/EricMCornelius/boost/commit/cdc08a1afa4b3df85997d54d9e6a4... Cheers, Eric Cornelius
on Fri May 10 2013, Eric Cornelius
Hi all,
Out of curiosity, is the plan to move to a git pull-request model once the modularization process is complete? Or is github being used simply as a convenient mirror and interface for browsing code and history?
Except in cases where individual maintainers take exception to the github pull request system (I've seen that before, not that I understand it), all maintainers will be using it.
Also, I have some changes to the Jamroot and boostcpp.jam files for improving modularization builds, which aggregate all the public headers from modules into the standard boost/... layout within the install/include directory, as well as implicitly setting up include paths during the initial build process.
https://github.com/EricMCornelius/boost/commit/cdc08a1afa4b3df85997d54d9e6a4...
I'm not sure to whom this should be directed. Daniel, how well does this work match up with your plans? -- Dave Abrahams
Hi Eric, Can you please post Boost.Build changes to the Boost.Build ML for discussion? I fear this might drown in the noise on the main list. On Saturday, 11. May 2013 01:39:58 Eric Cornelius wrote:
Hi all, Also, I have some changes to the Jamroot and boostcpp.jam files for improving modularization builds, which aggregate all the public headers from modules into the standard boost/... layout within the install/include directory,
This is a good idead.
as well as implicitly setting up include paths during the initial build process.
Well, I do not like the include path explosion resulting from this. I think the correct way is to improve Boost.Build to generate correct forward headers or symlinks. See my patches based on Stevens work on the Boost.Build lists for a start.
https://github.com/EricMCornelius/boost/commit/cdc08a1afa4b3df85997d54d9e6a4 72a6319dd68
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
participants (3)
-
Dave Abrahams -
Eric Cornelius -
Jürgen Hunold