forked from pocb/boost
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
44 lines (33 loc) · 1.9 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
CMake-ified Boost
-----------------
First of all, the (pristine/official) Boost project can be found on:
http://www.boost.org
The CMake build framework (set of CMakeLists.txt and module.cmake files)
is then added on top of the official Boost release, thanks to a
dedicated patch.
That CMake framework (and patch) is hosted and maintained on GitHub,
in the following Git repository: https://github.com/pocb/boost
POCB stands for Plain Old CMake-ified Boost, as opposed to the new Ryppl
initiative towards a modularised Boost, also using extensively CMake.
However, as of today (June 2011), that framework does not allow
easily building Boost for Linux distributions.
[A clone also exists on Gitorious, where CMake-related work was formely done:
http://gitorious.org/boost/cmake]
Upstream work is synchronised thanks to the Ryppl's hosted Git clone:
https://github.com/ryppl/boost-svn/tree/trunk
A discussion explaining the details can be read on the Ryppl Google Group:
https://groups.google.com/group/ryppl-dev/browse_thread/thread/4e2ffe397d03eaee/b619c95964b0e003?hl=en&#b619c95964b0e003
The Ryppl project (http://www.ryppl.org) is maintained by Eric Niebler and
Dave Abrahams, from the Boost project, and is itself a lot more than just
about synchronisation:
"Ryppl aims to be a distributed cross-platform software management system
designed to accommodate both end-users and developers. Ryppl unites
version control, test management, package management, release management,
reporting, and other sub-systems into a coherent and scalable software
management system."
That current CMake-ification (sub-)project aims to be fully integrated
into the Ryppl project. There is still some work to be done on the
CMake-ification of modularised Boost. If you would like to contribute,
do not hesitate to subscribe to the Ryppl mailing list:
http://groups.google.com/group/ryppl-dev/subscribe
Denis Arnaud (June 2011)