Thank you so much, this works perfectly.
>
> -- Forwarded message --
> From: Mateusz Loskot
> To: cmake@cmake.org
> Cc:
> Bcc:
> Date: Tue, 16 Apr 2019 01:10:44 +0200
> Subject: Re: [CMake] Boost 1.70.0 -- FindBoost issues? No linker libraries
> found
On Tue, 16 Apr 2019 at 01:01, Andrew Maclean wrote:
>
> In build.ninja all the requested linker libraries are there e.g.
> /usr/local/lib/libboost_date_time.so>
> Boost 1.70
> When using Boost 1.70 all I get in the CMakeLists.txt file are entries like:
> //The directory containing a CMake config
Has anyone else got issues using Boost 1.70 in their code.
I'm using CMake 3.14.2
I have done the usual build/install of Boost in linux and everything seems
to be installed Ok in /usr/local/include and /usr/local lib.
The problem is the no linker libraries are being found.
I use this in my CMakeLi
I am having a problem with make 3.12 (windows) and cmake version 3.13.0-rc2
(linux). I am attempting to link boost headers privately to a static library,
which is then linked by a client executable, that I do not want to depend on
boost.
According to the docs, the find_package(Boost) provides a
Boost Library developers are taking a serious look at making Boost more
friendly for users of CMake. This discussion is taking place on the
Boost Developer's mailing list.
https://www.boost.org/community/groups.html
Those who have an interest in this topic are encouraged to observe
and/or pa
-italian.co.uk On Behalf Of
Chris Wilson
Sent: 08 August 2018 12:29
To: Wheeler, Gavin
Cc: cmake@cmake.org
Subject: Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?
Hi all,
I solved this problem (or a very similar one) by using a CMake
superbuild<https://
ssage-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Mateusz Loskot
Sent: 07 August 2018 17:34
To: cmake@cmake.org
Subject: Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?
On 7 August 2018 at 18:15, Wheeler, Gavin wrote:
> [...]
> 1. Look in C:\Program
>
On 7 August 2018 at 18:15, Wheeler, Gavin wrote:
> [...]
> 1. Look in C:\Program
> Files\CMake\share\cmake-3.9\Modules\FindBoost.cmake
Rule #1: never use CMake older than the latest release!
Rule #2: if you die hard for old CMake, force use of the latest FindBoost.cmake
if (CMAKE_VERSION
d make a nice cup of tea
Best Regards,
Gavin
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Dvir Yitzchaki
Sent: 15 July 2018 08:27
To: Innokentiy Alaytsev ; cmake@cmake.org
Subject: Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?
I recommend using Hunter package manager:
I recommend using Hunter package manager:
https://docs.hunter.sh/en/latest/quick-start/boost-components.html
Regards,
Dvir
-Original Message-
From: CMake On Behalf Of Innokentiy Alaytsev
Sent: Thursday, July 12, 2018 13:29
To: cmake@cmake.org
Subject: Re: [CMake] Boost + CMake
Hello!
First of all, I suggest you use Boost imported targets instead of
Boost_INCLUDE_DIRS and Boost_LIBRARY_DIRS and the
target_include_directories() and target_link_libraries() functions. Al this
is to better support exporting CMake package if you need it. If you do not
produce CMake package fo
Hello! First the short version...
Can anyone give me a set of instructions to download, build and setup the
latest Boost (currently 1.67) on Windows 10 for VS 2017 64bit such that the
following will work...
find_package(Boost REQUIRED COMPONENTS system filesystem thread date_time
iostreams
Let's hope this try actually works. It was tried 8 years ago but some of
the boost developers really fought the transition. Hopefully with the
support of the steering committee it will work. Let's all welcome the
boost devs into the CMake community with wide open arms.
--
Mike Jackson [mike.ja
Good news !
Hopefully the bcp would also work with CMake so only requires component
would be installed.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. F
Very exciting news... hopefully it works out! Congratulations to CMake
for this; this is huge support for CMake and shows it is becoming way
more popular (not that it wasn't already!)
https://lists.boost.org/boost-interest/2017/07/0162.php?utm_content=buffera6a82&utm_medium=social&utm_source=plus.
Hello all! 18.07.2017, 20:48, "Gonzalo Garramuño" :> Just posted in the boost mailing list. Congratulations to both teams!> It seems that we are talking about this thread: https://lists.boost.org/Archives/boost/2017/07/237248.php > --> Gonzalo Garramuño>> -->> Powered by www.kitware.com>> Please ke
Just posted in the boost mailing list. Congratulations to both teams!
--
Gonzalo Garramuño
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
in
Does anyone know of the happening around Boost 2 and its possible adoption of
CMake? I know Boost and CMake have a very long and very sad history, but I
recall someone reporting on this list that he/she will attend a Boost 2 related
conference and will again promote the benefits of CMake as oppo
Hi David.
Probably something in your CMakeList is set up incorrectly. If you share
that CMakeList, someone might be able to tell what.
Petr
On 10 June 2016 at 13:09, Xi Shen wrote:
> I created a simple command line tool on Windows, using the Boost library.
> I use the CMake tool to generate th
I created a simple command line tool on Windows, using the Boost library. I
use the CMake tool to generate the build file for MSBuild.
I set the BOOST_INCLUDEDIR environment variable and CMake generated the
build file without any error.
However the solution cannot be built by MSBuild. It complain
You will find a list of CMake "Module Maintainers" here:
http://www.cmake.org/Wiki/CMake:Module_Maintainers
If a module is not listed, it is not currently claimed. (Meaning
either nobody is currently maintaining it, or "everybody" is pitching
in a little bit as things important to them arise.)
Un
Ryan,
Thanks for the helper script - I'll try that out on Monday.
Does anybody know if the FindBoost.cmake file is maintained by the CMake
developers, or does it have a 3rd party maintainer ? It would be nice to
see some logic similar to your script incorporated by default so that other
people e
I've used a script to help it out a bit. I think these Windows installers
are new. Here's the script I use - it basically sets BOOST_ROOT and
BOOST_LIBRARYDIR automatically in some cases.
https://gist.github.com/rpavlik/586f1fda6e32777623e1
Ryan
On Fri, Nov 14, 2014 at 6:56 AM, Glenn Coombs
wr
Hi,
I have installed Boost on Windows 7 for Visual Studio 2013 by running these
installers:
boost_1_56_0-msvc-12.0-32.exe
boost_1_56_0-msvc-12.0-64.exe
downloaded from
http://sourceforge.net/projects/boost/files/boost-binaries/1.56.0/.
I'm using CMake 2.8.12.1 and when I try to build a simple B
On Tue, Apr 16, 2013 at 3:16 PM, Andreas Haferburg wrote:
> > I can't guarantee where the boost libraries are installed, that's why I
> use FindBoost.
> Just make the CMake error message clear, e.g. "Boost 1.50 expected to be
> found in ". Most people know how to rename a directory.
That's what
On 11.10.2012 12:16, Klaim - Joël Lamotte wrote:> 2. find a way for CMake FindBoost to automatically
find the 64 bit binaries instead of the 32 bit
> binaris.
> I don't see a clear solution to achieve this, because it depends a lot on how boost have been
compiled.
Use a naming convention, e.g.
On Tue, Apr 16, 2013 at 12:32 PM, Slava
wrote:
>
> You build 64-bit stuff (including boost if you wish) in 64-bit
> environment, 32-bit stuff (including boost if you wish) in a separate
> 32-bit environment. The environment is native for build tools, so you need
> no crosscompiling (-m32), no spec
On Tue, Apr 16, 2013 at 9:15 AM, Slava wrote:
>
> In my experience finding/adapting packages for crosscompiling 64->32 is
> much more troublesome than setting up 32-bit chroot and using it for 32-bit
> builds.
Sorry but I don't understand, certainly because I'm still a noob at linux
stuffs.
I do
On Mon, 15 Apr 2013 16:59:25 +0200, Klaim - Joël Lamotte
wrote:
For now I think the simplest solution would be to make b2 use a default
64bit lib directory
when the directory is unspecify. Then FindBoost cmake module can rely on
this knowledge to try to find the right binaries,
based on BOOS
On Thu, Oct 11, 2012 at 2:19 PM, Klaim - Joël Lamotte wrote:
> My current understanding is that boost don't have a specific default lib
> dir for different address models, which is the source of the problem as
> FindBoost script can't rely on a protocol to find these lib files.
>
> Am I correct?
>
Júlio Hoffimann said:
>
> I don't know if i understood correctly, but you can set the library
> directory by hand, please refer to
> /usr/share/cmake-/Modules/FindBoost.cmake, in particular the
> variable BOOST_LIBRARYDIR.
On Thu, Oct 11, 2012 at 1:29 PM, Miller, Frank wrote:
> A simple solut
Júlio Hoffimann said:
>
> I don't know if i understood correctly, but you can set the library
> directory by hand, please refer to
> /usr/share/cmake-/Modules/FindBoost.cmake, in particular the
> variable BOOST_LIBRARYDIR.
On Thu, Oct 11, 2012 at 1:29 PM, Miller, Frank wrote:
> A simple solut
...@cmake.org] on behalf of Klaim -
Joël Lamotte [mjkl...@gmail.com]
Sent: Thursday, October 11, 2012 5:16 AM
To: Boost users list; cmake@cmake.org
Subject: [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using
CMake.
I am having a problem with b2 on Windows using Visual Studio (2010
I am having a problem with b2 on Windows using Visual Studio (2010 & 2012
but it is irrelevant):
Until now I was building boost with b2 in a way that would first build 32
bit version in the default library directory, then the 64bit version in
lib/64 .
I wasn't using the 64bit version until this mor
Problem fixed. Thanks :)
On Wed, Aug 8, 2012 at 3:35 PM, Nick Overdijk wrote:
> No, as far as I know you need to specify the components for boost always.
> I know of some find_boost that just put everything in there when you didn't
> name components, but as a rule, just specifiy the components.
No, as far as I know you need to specify the components for boost always. I
know of some find_boost that just put everything in there when you didn't
name components, but as a rule, just specifiy the components. ;-)
On Wed, Aug 8, 2012 at 1:29 PM, Sumit Adhikari wrote:
> Thanks for the reply. But
Thanks for the reply. But is this is a Bug ?
Regards,
Sumit
On Wed, Aug 8, 2012 at 1:28 PM, Nick Overdijk wrote:
> Try again with this example:
>
>
> http://stackoverflow.com/questions/3897839/how-to-link-c-program-with-boost-using-cmake
>
>
> On 2012-08-08, at 12:52:06 , Sumit Adhikari wrote:
Try again with this example:
http://stackoverflow.com/questions/3897839/how-to-link-c-program-with-boost-using-cmake
On 2012-08-08, at 12:52:06 , Sumit Adhikari wrote:
> I am searching boost like as follows :
>
> # Boost Library Search
> find_package (Boost)
> if (Boost_FOUND)
> include_dire
I am searching boost like as follows :
# Boost Library Search
find_package (Boost)
if (Boost_FOUND)
include_directories(${Boost_INCLUDE_DIRS})
link_directories(${Boost_LIBRARY_DIRS})
set(LIBS ${LIBS} ${Boost_LIBRARIES})
else()
message(FATAL_ERROR "Boost Not Found")
endif (Boost_FOUND)
I
Hi
I'm trying to build a project that uses boost::asio for serial comms. I get
the following error when I try to build:
/usr/include/boost/system/error_code.hpp:208: undefined reference to
`boost::system::get_system_category()'
A copy of the CMake file is located here: http://ideone.com/nRxvK
Y
Yes, target_link_libraries works well, I had problem before because I used
find_package(Boost) instead of find_package(Boost COMPONENTS thread), so
when I used target_link_libraries( MyProject ${Boost_LIBRARIES} ), it
didn't link anything, after I specify the components in find_package, it
has no p
On May 1, 2012, at 11:37 AM, Mourad Boufarguine wrote:
>
> On Tue, May 1, 2012 at 9:10 AM, Rolf Eike Beer wrote:
> On Di., 1. Mai. 2012 00:20:58 CEST, Mourad Boufarguine
> wrote:
>
> > Hi,
> >
> > add this :
> >
> > link_directories(${Boost_LIBRARY_DIRS})
> >
> > after the include_director
On Tue, May 1, 2012 at 9:10 AM, Rolf Eike Beer wrote:
> On Di., 1. Mai. 2012 00:20:58 CEST, Mourad Boufarguine <
> mou...@boufarguine.name> wrote:
>
> > Hi,
> >
> > add this :
> >
> > link_directories(${Boost_LIBRARY_DIRS})
> >
> > after the include_directories command.
>
> No, please don't. Th
On Di., 1. Mai. 2012 00:20:58 CEST, Mourad Boufarguine
wrote:
> Hi,
>
> add this :
>
> link_directories(${Boost_LIBRARY_DIRS})
>
> after the include_directories command.
No, please don't. The target_link_libraries command is what you really want.
Please stop advertising link_directories,
st right there in the directory I installed boost. Could anyone help me
>>> understand where the problem is?
>>>
>>> Thanks!
>>> --
>>> Sophie Wang
>>> www.sophiehuiwang.com
>>>
>>>
>>> --
>>>
>>>
Could anyone help me
>> understand where the problem is?
>>
>> Thanks!
>> --
>> Sophie Wang
>> www.sophiehuiwang.com
>>
>>
>> --
>>
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>&g
Thanks to David & Daniel for the replies, but I was
already doing everything by the book, so their replies
didn't help. It seems to be a bug, or flaky feature, in boost; I had
to disable "auto-linking". Here's the final, working CMakeLists.txt:
cmake_minimum_required(VERSION 2.8)
# Turn off boos
On Sun, Oct 30, 2011 at 5:46 AM, Daniel Dekkers wrote:
> find_package() searches for a package, and sets variables. Typically
> variables like...
>
> _FOUND # package found or not
> _INCLUDE_DIR # path to the libraries include directory
> _LIBRARY # name of the library
>
> You still have to link
find_package() searches for a package, and sets variables. Typically variables
like...
_FOUND # package found or not
_INCLUDE_DIR # path to the libraries include directory
_LIBRARY # name of the library
You still have to link in the library yourself:
target_link_libraries(${TARGET} ${_LIBRARY})
I'm slowly learning cmake and converting some real software to it,
targeting Linux, Windows, and Mac OS X.
Along the way, I'm making minimal working examples (they're a lot
easier to debug them than the real thing) and putting them up at
http://code.google.com/p/winezeug/source/browse/#svn/trunk/cm
I tend to use the online documentation:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#module:ExternalProject
But I agree that an example would also be useful. Perhaps the wiki
could have examples of how to use external project with common 3rd
party libs (e.g. boost, Qt).
On Wed, Oct 26, 201
On Wed, Oct 26, 2011 at 11:56 AM, Ben Medina wrote:
> David,
>
> Yes, adding "call" to the front of the command works. Thanks! Would be
> great to get that fixed for 2.8.7, as I spent a good portion of
> yesterday racking my brain about this.
>
> I also discovered that, if using a variable to buil
David,
Yes, adding "call" to the front of the command works. Thanks! Would be
great to get that fixed for 2.8.7, as I spent a good portion of
yesterday racking my brain about this.
I also discovered that, if using a variable to build the
CONFIGURE_COMMAND, that variable should be a list, rather t
Try changing the configure command to "call bootstrap.bat" instead.
I suspect this is related to the symptoms reported in these bugs:
http://public.kitware.com/Bug/view.php?id=12445
http://public.kitware.com/Bug/view.php?id=12461
Related to using "bat" or "cmd" files as custom commands. We n
Hello all,
I'm trying to build Boost as an external project, but it won't build
if I use the VS2010 generator. I've whittled the code down to the
following CMakeLists.txt:
cmake_minimum_required(VERSION 2.8)
project (boost-external)
set (Boost_Source "E:/boost_1_47_0")
include(ExternalProject)
On 02/10/2011 09:17 PM, Adams, Brian M wrote:
> I'm curious if the behavior I'm seeing with respect to FindBoost.cmake is
> expected. (I realize I'm using these macros in a convoluted way, so
> understand if I can't make it work more cleanly.)
>
> What I'd like to be able to do is something lik
I'm not entirely sure why FindBoost uses the cache in the way it does, as it
seems to cause a fair amount of issues. I've made an experimental
modification of FindBoost.cmake that doesn't use internal cache variables
here: [1] It seems to work in my initial tests, but it's probably not ideal
and I
I'm curious if the behavior I'm seeing with respect to FindBoost.cmake is
expected. (I realize I'm using these macros in a convoluted way, so understand
if I can't make it work more cleanly.)
What I'd like to be able to do is something like the following to probe for a
system-provided or user-
Hello all,
I have a library that depends on boost. One user of this library compiles
only x32 version. Second user compiles x64. Third user compiles both x32 and
x64.
First user has only x32 version of the boost in the BOOST_LIBRARYDIR.
Second user only x64 version in the BOOST_LIBRARYDIR.
Third
On Wed, Oct 6, 2010 at 7:55 PM, assume_R wrote:
> Hey all. So I noticed a possible bug with the way boost is searched in
> findboost.cmake.
>
> Essentially, if you have the boost static runtimes installed, that's what
> Visual Studio will require. For example, using the thread library, it will
Philip Lowman recently took the mantle for the FindBoost maintenance. He
fixed a bunch of stuff just now for the upcoming (now in release candidate
phase) CMake 2.8.3 release...
Are you reporting this based on CMake 2.8.3-rc2 or an earlier release of
CMake?
Try using the release candidate. I know
Hey all. So I noticed a possible bug with the way boost is searched in
findboost.cmake.
Essentially, if you have the boost static runtimes installed, that's what
Visual Studio will require. For example, using the thread library, it will
need libboost_thread*-sgd*
Yet the non-static-runtime vers
>. I guess those 32.lib libraries are 64 bit, even though the names suggest
>otherwise (yay for Microsoft).
>
I did not know that. Sorry. I admit, I have not looked at the lib
names on my 64 bit builds.
John
___
Powered by www.kitware.com
Visit other K
otherwise (yay
for Microsoft).
So... Any other suggestions? :)
Jodi
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: dinsdag 24 augustus 2010 16:20
To: Oenen, Jodi van; CMake mailing list
Subject: Re: [CMake] Boost lib error when linking executable
> T
> True :)
>
> As I said, I'm just replicating the current Make system, in which those same
> 32 bit libs are used -- and it works. CMake even adds some extra 32 bit libs
> to the command line; I think they are added in Windows-icl.cmake
> (CMAKE_C_STANDARD_LIBRARIES_INIT). So I'd say it should a
On Tue, Aug 24, 2010 at 9:57 AM, Oenen, Jodi van
wrote:
> Hi,
>
> We are migrating an 'old' Make project into the CMake world, and I am
> encountering a problem during the link phase of one of our executables: the
> linker cannot open a boost library.
>
> I am using CMake 2.8.2 on WinXP x64, Boo
Hi,
We are migrating an 'old' Make project into the CMake world, and I am
encountering a problem during the link phase of one of our executables: the
linker cannot open a boost library.
I am using CMake 2.8.2 on WinXP x64, Boost regex library 1.33.1, with Intel
C++/Fortran 9.1 compilers (icl/i
On 23.06.09 16:51:05, Michael Jackson wrote:
> Boost uses the following version scheme:
>
> If the sub minor version is "0" then leave it off all versions. If the
> subminor version is NOT zero then add it on. So for versions like 1.38.1
> FindBoost will work just fine. But for 1.38 (the current
On 23.06.09 16:23:21, Bill Hoffman wrote:
> Christopher Harvey wrote:
>> define BOOST_ROOT and point it at the root install location for boost. I
>> had the same problem, that fixed it. I only had to do that on windows.
>>
> There seems to be a bug in the FindBoost, BOOST_ROOT should not be
> req
John Drescher wrote:
On Tue, Jun 23, 2009 at 4:23 PM, Bill Hoffman wrote:
Christopher Harvey wrote:
define BOOST_ROOT and point it at the root install location for boost. I
had the same problem, that fixed it. I only had to do that on windows.
There seems to be a bug in the FindBoost, BOOST_R
On Jun 23, 2009, at 4:23 PM, Bill Hoffman wrote:
Christopher Harvey wrote:
define BOOST_ROOT and point it at the root install location for
boost. I
had the same problem, that fixed it. I only had to do that on
windows.
There seems to be a bug in the FindBoost, BOOST_ROOT should not be
req
Hi Bill,
Thanks, adding another line to _boost_LIBRARIES_SEARCH_DIRS without the
Boost_SUBMINOR_VERSION fixes the problem for me as well. I agree that this
is a special case for 0, though -- there is some question whether the line
without the subminor version should be appended to the list if the
On Tue, Jun 23, 2009 at 4:23 PM, Bill Hoffman wrote:
> Christopher Harvey wrote:
>>
>> define BOOST_ROOT and point it at the root install location for boost. I
>> had the same problem, that fixed it. I only had to do that on windows.
>>
> There seems to be a bug in the FindBoost, BOOST_ROOT should
On 23.06.09 16:17:21, Curtis Rueden wrote:
> > Also, Looking at the CMakeLists.txt file it seems you are trying to parse
> > the Boost_THREAD library variable for something? If you are trying to
> > differentiate between the Release and Debug versions there are the following
> > variables for each
Christopher Harvey wrote:
define BOOST_ROOT and point it at the root install location for boost. I
had the same problem, that fixed it. I only had to do that on windows.
There seems to be a bug in the FindBoost, BOOST_ROOT should not be
required. I got it to work by adding this:
SET(_boo
On Jun 23, 2009, at 4:17 PM, Curtis Rueden wrote:
Hi Mike,
I use the boost pre-compiled all the time and I don't have any of
these issues BUT I do set the BOOST_ROOT environment variable in "My
Computer->Advanced Settings" after I install which may be the
difference. I use threads, progr
>
> define BOOST_ROOT and point it at the root install location for boost. I
> had the same problem, that fixed it. I only had to do that on windows.
>
Thanks Christopher, but I am aware of that fix. Actually, that's what my
hack does -- it uses CMake to set BOOST_ROOT programmatically. What I'm
g
Hi Mike,
> I use the boost pre-compiled all the time and I don't have any of these
> issues BUT I do set the BOOST_ROOT environment variable in "My
> Computer->Advanced Settings" after I install which may be the difference. I
> use threads, program_options, testing, filesystem and system.
>
Yes,
define BOOST_ROOT and point it at the root install location for boost. I
had the same problem, that fixed it. I only had to do that on windows.
Curtis Rueden wrote:
> Hi everyone,
>
> I am using CMake to build some code cross-platform. This code requires
> Boost Thread to compile. I am having seve
I use the boost pre-compiled all the time and I don't have any of
these issues BUT I do set the BOOST_ROOT environment variable in "My
Computer->Advanced Settings" after I install which may be the
difference. I use threads, program_options, testing, filesystem and
system.
I did notice in
Hi Andreas,
Well, then most probably the layout of that binary installation differs
> from what the FindBoost.cmake file expects. So where is the boost thread
> library and how is it named?
The latest available version of Boost offered by BoostPro is v1.38. The
libraries are placed in:
C:\Pro
On 23.06.09 13:09:25, Curtis Rueden wrote:
> First, I installed Boost using BoostPro's precompiled binaries at
> http://www.boostpro.com/download.
>
> Then I tried the following CMakeLists.txt file:
>
> --
> # Simple CMake build file for testing FindBoost. Fails on Windows with
> # Boost
Hi everyone,
I am using CMake to build some code cross-platform. This code requires Boost
Thread to compile. I am having several problems with FindBoost on Windows.
First, I installed Boost using BoostPro's precompiled binaries at
http://www.boostpro.com/download.
Then I tried the following CMak
On Sun, Mar 15, 2009 at 12:03 PM, Bart Janssens
wrote:
> On Fri, Mar 13, 2009 at 1:13 PM, Geir Erikstad wrote:
> > 09/3/13 Philip Lowman :
> >> I've logged a bug report for it here. I'm pretty sure the best fix
> would be
> >> to get FindBoost to ignore the system component when it's detected a
On Fri, Mar 13, 2009 at 1:13 PM, Geir Erikstad wrote:
> 09/3/13 Philip Lowman :
>> I've logged a bug report for it here. I'm pretty sure the best fix would be
>> to get FindBoost to ignore the system component when it's detected a version
>> less than 1.35. I've attached a new FindBoost.cmake to
John
Thanks for this info. The version I compiled from the boost-cmake svn
repository was 1.36 so I didn't realize that the main branch had it
included.
I'll give 1.38 a try.
JB
Will standard releases of Boost
contain CMakeLists files in my lifetime?
They do
On Fri, Mar 13, 2009 at 3:09 PM, John Drescher wrote:
> On Fri, Mar 13, 2009 at 3:08 PM, John Drescher wrote:
>>> Will standard releases of Boost
>>> contain CMakeLists files in my lifetime?
>>
>> They do already. 1.38.0 did. Although I did not have good success
>> building it that way.
>>
> Here
On Fri, Mar 13, 2009 at 3:08 PM, John Drescher wrote:
>> Will standard releases of Boost
>> contain CMakeLists files in my lifetime?
>
> They do already. 1.38.0 did. Although I did not have good success
> building it that way.
>
Here is a link to the release notes (look at the bottom of the page):
> Will standard releases of Boost
> contain CMakeLists files in my lifetime?
They do already. 1.38.0 did. Although I did not have good success
building it that way.
John
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:/
I would ask on the boost-cmake mailing list. You will probably get
good replies from notable people from the boost project.
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.n
I just did an svn update of a very old boost-cmake folder and ran cmake.
Everything built with no errors (Visual studio 2008) (lots of warnings,
but no errors).
I wonder.
How well is CMakeification of Boost going? Will standard releases of
Boost contain CMakeLists files in my lifetime? and if
09/3/13 Philip Lowman :
> On Thu, Mar 12, 2009 at 7:39 PM, Bart Janssens
> wrote:
>>
>> Not sure if this ever came up, but I'm struggling with FindBoost and
>> the boost system library. The system library is required from boost
>> 1.35 onwards, but doesn't exist in earlier versions. Is there a way
On Thu, Mar 12, 2009 at 7:39 PM, Bart Janssens wrote:
> Not sure if this ever came up, but I'm struggling with FindBoost and
> the boost system library. The system library is required from boost
> 1.35 onwards, but doesn't exist in earlier versions. Is there a way to
> make CMake only look for the
Hi all,
Not sure if this ever came up, but I'm struggling with FindBoost and
the boost system library. The system library is required from boost
1.35 onwards, but doesn't exist in earlier versions. Is there a way to
make CMake only look for the system library if the boost version is
greater than o
uBLAS is part of the 'numeric' library and is NOT a compiled library
so just having the boost headers installed correctly is enough.
On Nov 6, 2008, at 4:56 PM, Christopher Harvey wrote:
Hi list,
Sometimes when using the FindBoost.cmake package I have a very hard
time figuring out what val
On 06.11.08 16:56:52, Christopher Harvey wrote:
> Hi list,
> Sometimes when using the FindBoost.cmake package I have a very hard time
> figuring out what valid names for the components list are. Normally I
> just do a google code search but now I can't find what I'm looking for.
> I'd like to
Hi list,
Sometimes when using the FindBoost.cmake package I have a very hard time
figuring out what valid names for the components list are. Normally I
just do a google code search but now I can't find what I'm looking for.
I'd like to check to make sure that the boost uBLAS library is installe
FIXED..
Thanks for the feedback
Mike
On Nov 2, 2008, at 3:49 AM, Maik Beckmann wrote:
2008/11/1 Michael Jackson <[EMAIL PROTECTED]>:
Hi Michael,
If you want to have a look try reading the following wiki page for
more
details:
https://svn.boost.org/trac/boost/wiki/CMakeConfigAndBuild
Th
Daniel Stonier wrote:
> 2008/11/2 Esben Mose Hansen <[EMAIL PROTECTED]>:
>> On Saturday 01 November 2008 20:16:42 Michael Jackson wrote:
>>> Just wanted to let the cmake community know that very early CMake
>>> support has been added to the Boost trunk. Currently only some of the
>>
>> That is gre
2008/11/2 Esben Mose Hansen <[EMAIL PROTECTED]>:
> On Saturday 01 November 2008 20:16:42 Michael Jackson wrote:
>> Just wanted to let the cmake community know that very early CMake
>> support has been added to the Boost trunk. Currently only some of the
>
> That is great news! Occasionally I strugg
1 - 100 of 119 matches
Mail list logo
