2009/9/21 Philip Lowman phi...@yhbt.com:
Thankfully, the changes made to library naming in 1.40 do not break
FindBoost. :)
Philip, does this apply to the latest release (i.e. cmake 2.6.4)? Or
rather the latest revision in CVS? (See also below)
Could you post what you have in mind for the
2009/9/21 Philip Lowman phi...@yhbt.com:
Ultimately we can add anything to the search path of FindBoost that makes
sense. If you have suggestions, please feel free to submit them (preferably
with a tested patch) to the bugtracker.
In preparation of this, could you please clarify which file
On Mon, Sep 21, 2009 at 5:51 AM, Ingolf Steinbach
ingolf.steinb...@googlemail.com wrote:
2009/9/21 Philip Lowman phi...@yhbt.com:
Thankfully, the changes made to library naming in 1.40 do not break
FindBoost. :)
Philip, does this apply to the latest release (i.e. cmake 2.6.4)? Or
rather
On Fri, Sep 18, 2009 at 6:46 PM, Ingolf Steinbach
ingolf.steinb...@googlemail.com wrote:
2009/9/18 Bill Hoffman bill.hoff...@kitware.com:
If someone has a reasonable set of places to look we can add them. Does
the
boost installer set any registry values?
Not sure about that.
2009/9/18 John Drescher dresche...@gmail.com:
You set BOOST_ROOT in your windows environment variables.
Sorry, but I'd consider this just a workaround.
From the discussion in this thread, I have the impression that the
only purpose of setting the BOOST_ROOT environment variable is to tell
On Fri, Sep 18, 2009 at 5:01 PM, Ingolf Steinbach
ingolf.steinb...@googlemail.com wrote:
2009/9/18 John Drescher dresche...@gmail.com:
You set BOOST_ROOT in your windows environment variables.
Sorry, but I'd consider this just a workaround.
From the discussion in this thread, I have the
2009/9/18 John Drescher dresche...@gmail.com:
It's difficult on windows since there is no standard location for
stuff like this.
Seconded.
What is the FindBoost to do search all paths that
are valid for the current user?
Nevertheless, there *are* some hard-coded paths in FindBoost
Ingolf Steinbach wrote:
2009/9/18 John Drescher dresche...@gmail.com:
It's difficult on windows since there is no standard location for
stuff like this.
Seconded.
What is the FindBoost to do search all paths that
are valid for the current user?
Nevertheless, there *are* some hard-coded
2009/9/18 Bill Hoffman bill.hoff...@kitware.com:
If someone has a reasonable set of places to look we can add them. Does the
boost installer set any registry values?
Not sure about that. Unfortunately, there is no installer for 1.40.0
yet; and 1.40 seems to be somewhat different than previous
Hi,
I have encountered problems with Boost 1.40 (build on Windows using
Visual Studio 2008 and MinGW GCC 4.4.0) with CMake 2.6.4.
Boost was compiled for Visual Studio 2008 like this:
bjam --build-dir=c:\temp\boost toolset=msvc --build-type=complete install
and for MinGW GCC like this:
bjam
When you build boost use the --prefix=C:\boost_1_40 ... install
also you should specify toolset==msvc9.0 or the libraries will not be
named correctly.
Mike Jackson
On Sep 17, 2009, at 4:48 PM, Cristian Adam wrote:
Hi,
I have encountered problems with Boost 1.40 (build on Windows using
From FindBoost.cmake:
# These last three variables are available also as environment
variables:
#
# BOOST_ROOT or BOOSTROOT The preferred installation prefix for
searching for
#Boost. Set this if the module has
problems finding
#
Michael Jackson wrote:
When you build boost use the --prefix=C:\boost_1_40 ... install
also you should specify toolset==msvc9.0 or the libraries will not be
named correctly.
Hmm, I managed to compile a small program_options test program.
Program options libraries are named like:
James C. Sutherland wrote:
From FindBoost.cmake:
# These last three variables are available also as environment variables:
#
# BOOST_ROOT or BOOSTROOT The preferred installation prefix for
searching for
#Boost. Set this if the module has
problems
On Thu, Sep 17, 2009 at 6:10 PM, Cristian Adam cristian.a...@gmx.net wrote:
James C. Sutherland wrote:
From FindBoost.cmake:
# These last three variables are available also as environment variables:
#
# BOOST_ROOT or BOOSTROOT The preferred installation prefix for
searching for
#
John Drescher wrote:
You set BOOST_ROOT in your windows environment variables.
Thanks for the tip. Setting BOOST_INCLUDEDIR environment variable
to c:/boost/include/boost-1_40 resolved all the problems, no need
to set additional versions, it just worked.
I was a bit surprised to see that
16 matches
Mail list logo