There may possibly be renewed support for a "CMakeified" version
of Boost. Boost 1.44 was just released and it looks like at least one
individual "http://gitorious.org/~denisarnaud/boost/denisarnauds-zeuners-boost-cmake/commits/1.44.0-denis
" is keeping the boost-cmake up-to-date with the latest boost from
SVN. The problem that occurs is that with the defaults that the boost-
cmake project uses for installation there is some deviation from the
official Boost-bjam based builds. Namely boost-cmake uses versioned
include and library directories: $BOOST_ROOT/include/boost-1.44.0/ and
$BOOST_ROOT/lib/boost-1.44.0
The current FindBoost.cmake does not know to look for these
directories and so if someone builds boost with boost-cmake and then
tries to use that installation with CMake 2.8.2 to
"find_package(Boost ....)" it will not find boost.
There are just a few extra lines to be added to the FindBoost.cmake
file to alleviate this "disconnect". There are also
"BoostConfig.cmake" and "BoostConfigVersion.cmake" files included in
the boost-cmake distribution which I supposed is useful.
Thoughts?
___________________________________________________________
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Tuesday 06 Jul 2010 12:01:17 am David Cole wrote:
Hi all,
Now that we have released CMake 2.8.2 last Monday, and we have
switched to
this new workflow using branches in the git repository, *now* would
be a
great time to prioritize bug fixes for the next release of CMake.
We are leaning towards quarterly releases from now on, scheduling them
every 3 months. That would make the next release of CMake version
2.8.3
and scheduled to have an "rc1" release candidate in approximately
mid-September, 2010.
If you have a particular issue that you think should be fixed for
inclusion
in 2.8.3, please bring it up now. Ideally, each issue will be
discussed as
needed on the mailing list to come to any consensus about what
should be
done to fix it, and then an entry in the bug tracker may be used to
keep it
on the radar screen, and to track activity related to it.
Patches are always welcome. Patches that include testing of any new
features, or tests that prove a bug is really fixed on the dashboards,
basically any patch with testing is preferred over a patch with no
testing.
Also, if you are *adding* code, then you also probably need to add
*tests*
of that code, so that the coverage percentage stays as is or rises.
Please discuss issues here as needed, and add notes to existing
issues in
the bug tracker that you are interested in seeing fixed for 2.8.3 --
we
will be looking at the mailing list and activity in the bug tracker to
help prioritize the bug fixes that will occur in the next several
weeks.
Thanks,
David Cole
Kitware, Inc.
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
