[CMake] FindBoost (once again...)

[Andreas Pakulat]

On 23.11.08 18:58:57, Christian Ehrlicher wrote:
> Andreas Pakulat schrieb:
>> On 23.11.08 14:43:19, Christian Ehrlicher wrote:
>>> Hi,
>>>
>>> FindBoost does not work for me on windows because of a wrong pathname:
>>>
>>>       if (WIN32 AND NOT CYGWIN)
>>>         set(_boost_PATH_SUFFIX boost_${_boost_VER})
>>>       else (WIN32 AND NOT CYGWIN)
>>>         set(_boost_PATH_SUFFIX boost-${_boost_VER})
>>>       endif (WIN32 AND NOT CYGWIN)
>>>
>>> I installed boost with bjam and a directory 
>>> <prefix>/include/boost-1_37/  is created. Therefore the above 
>>> assumption that it's boost_1_37 is wrong.
>>
>> I suspect that the author used a binary boost package, but IIRC it wasn't
>> me, so don't really know.
>>
> But why should the binary packages use another include dir? Strange... :(

That was just a wild guess, because I know people did test FindBoost.cmake
quite a bit on win32 before cmake 2.6.0 was released.

>>> Also the latest cvs binary for win32 still does not have support for  
>>> boost 1.37.
>>
>> Thats not a problem, see the top of FindBoost.cmake, you can set
>> Boost_ADDITIONAL_VERSIONS prior to find_package to use newer boost
>> packages.
>>
> Good idea but the sources are not mine.

Well, thats something that you should use when calling find_package(Boost)
and know that boost 1.37 is supported. Unfortunately its the only easy way
to support future versions, because Boost includes the version in library
names and include dirs.

> And I don't care that 2.6.2 did not find it but 1.37 is out since three  
> weeks and cmake cvs still doesn't contain this version so I wanted to  
> make sure it's in 2.6.3 :)

Did you file a bugreport? Thats the safest way to notify the maintainer of
Findboost.cmake of this (though hopefully he also monitors boost releases)

Andreas

-- 
There is a fly on your nose.