Dear Thomas,
Sorry for the delay, I was on vacation for some days.
It is not advisable to add the line as supposed. As I understand the
deletion of the FindBoost component in the trunk, it was intended to be
free of some fixed components, e.g. the SDK, and to change the Boost
dependency if more than one instance is available.
If you set the variable BOOST_ROOT in cmake script the environment
variable is not evaluated any more.
I think it is better to use a similar pattern as in the original
FindBoost script as shipped with cmake:
# If BOOST_ROOT was defined in the environment, use it.
if (NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
set(BOOST_ROOT $ENV{BOOST_ROOT})
else(NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
set(BOOST_ROOT ${SOURCE_BASE_DIR}/boost_1_39_0)
endif(NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
In this case the variable is only set with value that matches with the
SDK (let say as fall back) if the variable is not set before or
available as windows environment variable.
I didn't tested the pattern, but I expect it will work.
Guido
T. Modes schrieb:
>
> On 24 Jul., 11:43, Guido Kohlmeyer <[email protected]> wrote:
>
>> I commited a small fix in CMakeLists.txt to find the static libraries in
>> the SDK.
>> I don't know how do you start CMake. You can even pass this as a
>> parameter at call of CMake "-D BOOST_ROOT=D:/usr/src/SDK/boost_1_39_0"
>> For instance I do a build based in batch files which call CMake and all
>> other tools. Here it is possible to set the environment variable right
>> before the call of CMake or to pass the path as a parameter.
>>
>
> Hi Guido,
>
> thank for your help.
>
> After adding the line (about line 180, in the IF(WIN32)-ENDIF
> condition)
> SET(BOOST_ROOT ${SOURCE_BASE_DIR}/boost_1_39_0)
> to CMakeList.txt it works without problems.
> So I don't need to change a environment variable when the library gets
> updated, because then I forgot that I have to change the environment
> variable.
>
> Does this line breaks something other (maybe in your batch files)?
> If not, we can commit it to trunk.
>
> Thomas
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
