Here's the beginning of a port for the boost C++ libraries. One of these, libboost_thread, will be required by the upcoming release of Gnash ( www/gnash ). This port seems to work for that, but there's much more to it.
If this is to be used for more than satisfying a dependency, I think some feedback from actual C++ programmers would help in deciding how it should be created. Some questions like: - The default naming scheme is atrocious. I've given them much simpler names, which I hear is what Linux packagers do and what most gnu configure scripts will look for. Will this be a problem? - Should shared archs have the static libs installed? - Are the debug versions wanted, necessary? Besides that there's the whole question of how it should be structured. I think one port per lib would be best, since it takes hours and GBs of scratch space to build and test the whole thing. Input would be appreciated. http://deanna.freeshell.org/boost.tar.gz **** Information for boost-1.33.1 Comment: peer-reviewed portable C++ source libraries Description: Boost provides free peer-reviewed portable C++ source libraries. Boost emphasizes libraries that work well with the C++ Standard Library. Boost libraries are intended to be widely useful, and usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. Boost aims to establish "existing practice" and provide reference implementations so that Boost libraries are suitable for eventual standardization. Ten Boost libraries are already included in the C++ Standards Committee's Library Technical Report (TR1) as a step toward becoming part of a future C++ Standard. More Boost libraries are proposed for the upcoming TR2. WWW: http://www.boost.org/
