Re: [Boost-cmake] Problem building NSIS installer.

Subject: Re: [Boost-cmake] Problem building NSIS installer.
From: Doug Gregor (doug.gregor_at_[hidden])
Date: 2009-07-22 10:09:47

On Wed, Jul 22, 2009 at 12:12 AM, Miguel A.
Figueroa-Villanueva<miguelf_at_[hidden]> wrote:
> On Wed, Jul 22, 2009 at 1:06 AM, Doug Gregor wrote:
>> The URL for downloading packages can be set in the configuration. When
>> the full CPack process completes, the CPackUploads directory will
>> contain a bunch of files that will need to be made available at that
>> URL. Alternatively, you can set the "monolithic" option to build all
>> of the packages into the installer itself.
>
> How do you set this monolithic option? By having
> BOOST_INSTALLER_ON_THE_FLY set to OFF?

Yes.

> Ok, I've traced the problem to the following:
>
> -- libs/python/CMakeLists.txt: is encapsulated in a "if (PYTHON_LIBRARIES)"
> -- libs/parameter/module.cmake states a dependency on the python lib
>
> So, I think the solution is to wrap the macro call in
> libs/parameter/CMakeLists.txt with the "if (PYTHON_LIBRARIES)"?

... and you don't have Python installed, or CMake isn't finding Python.

> BTW, does this mean that a header-only library (parameter) depends on
> a compiled lib (python)?

It's an odd dependency. One header file in the parameter library
depends on Boost.Python. If you don't have Boost.Python, you just
can't use that header.

  - Doug