Update regarding lib prefixing in BoostCore.cmake:
earlier I wrote:
--snip--
3>Linking...
3>LINK : fatal error LNK1104: cannot open file 'libboost_filesystem-vc90-mt-
>
> sgd-1_41.lib'
>
> Now except for hte 'lib" preceeding
> 'libboost_filesystem-vc90-mt-sgd-1_41.lib' as only:
>
> boost_filesys
In BoostConfig.cmake I had to comment out the following (from a previous
post on the CMake users mailing list):
# Clear out the built-in C++ compiler and link flags for each of the
# configurations.
#~ set(CMAKE_CXX_FLAGS_DEBUG "" CACHE INTERNAL "Unused by Boost")
#~ set(CMAKE_SHARED_LINKER_FLAGS
In BoostConfig.cmake I had to comment out the following (from a previous
post on the CMake users mailing list):
# Clear out the built-in C++ compiler and link flags for each of the
# configurations.
#~ set(CMAKE_CXX_FLAGS_DEBUG "" CACHE INTERNAL "Unused by Boost")
#~ set(CMAKE_SHARED_LINKER_FLAGS
I've had good success using the Boost "in a subdirectory" recipe,
> which builds only the parts I need. This is on linux/mac with gcc and
> make, so YMMV, but I think the relevant parts of my CMake file are:
>
>
Sweet all I need to do is switch to Linux... this is now reason 10463 on my
reasons to
On Wed, Mar 24, 2010 at 4:04 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> I have been playing with "ExternalProject_Add" and I don't think you are
> going to be able to do what you are trying to do. I was using the following:
>
>
Yes exactly which is why I switched to "with an unins
On 24 March 2010 14:31, Brian Davis wrote:
>
>
> I am currently trying the boost "With an uninstalled build" variety:
>
I've had good success using the Boost "in a subdirectory" recipe,
which builds only the parts I need. This is on linux/mac with gcc and
make, so YMMV, but I think the relevant
Hello,
The following is in boost "getting started" documentation:
Auto-Linking
Most Windows compilers and linkers have so-called
“auto-linking support,” which eliminates the second
challenge. Special code in Boost header files detects your
compiler options and uses that information to encode
With ExternalProject_Add, you have to specify the location of boost that you
have built/installed directly to the thing that wants to know where it is.
It cannot use FIND_PACKAGE to find boost until after boost is
built/installed.
So you would specify boost's location to the later projects that de
I have been playing with "ExternalProject_Add" and I don't think you
are going to be able to do what you are trying to do. I was using the
following:
project (Combined)
cmake_minimum_required(VERSION 2.8)
include(${CMAKE_ROOT}/Modules/ExternalProject.cmake)
SET (CMAKE_LIBRARY_OUTPUT_DIRECTOR
On Wed, Mar 24, 2010 at 2:44 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> The Boost-CMake (IMHO) sort of "abused" the cmake system somewhat in order
> to make it more "bjam" like.
>
> In practice if the first pass of FindBoost.cmake does not find anything
> then I usually have to ma
The Boost-CMake (IMHO) sort of "abused" the cmake system somewhat in
order to make it more "bjam" like.
In practice if the first pass of FindBoost.cmake does not find
anything then I usually have to manually go into the CMakeCache.txt
file and remove all the boost variables and re-run CMake
I was snooping around in FindBoost.cmake and found
IF (Boost_${basename}_LIBRARY_DEBUG AND
Boost_${basename}_LIBRARY_RELEASE)
# if the generator supports configuration types then set
# optimized and debug libraries, or if the CMAKE_BUILD_TYPE has a
value
IF (CMAKE_CONFIGURATIO
Welcome to Boost world. I don't think the Boost-CMake guys have
tackled the use-case that you are using so I hate to say it, BUT you
may be "ahead of the curve" on this one. All I can tell you is what
setup works for me. Theoretically you can do what you are trying to
do. Practically there
>> I still remain "old" school. I build* boost and install it somewhere. I
then use the following in my CMakeLists.txt file.
I am trying (in vain) to build only the parts of boost I need. Also is an
interesting chicken-and-the-egg problem with FindBoost or really find
whatever in CMake if doing
There are going to be some "growing pains" with Boost-cmake as some
new infrastructure is introduced to the Boost build system.
I still remain "old" school. I build* boost and install it
somewhere. I then use the following in my CMakeLists.txt file.
SET (Boost_FIND_REQUIRED TRUE)
SET (Boos
I am currently trying the boost "With an uninstalled build" variety:
# Boost Related
SET( BOOST_LIB_INSTALL_DIR ${BUILD_DIR}/ouput/lib CACHE STRING "" FORCE )
SET( BOOST_EXPORTS_INSTALL_DIR ${BUILD_DIR}/ouput/lib CACHE STRING "" FORCE
)
SET( BOOST_INCLUDE_INSTALL_DIR ${BUILD_DIR}/ouput/include CA
16 matches
Mail list logo
