Re: [CMake] A simple website to get started on new CMake projects

Well it's interesting but clearly you are providing help in only one kind of organisation. For example: - if you are doing a library that have public and private headers, it helps A LOT to have the public headers in an "include" directory - you don;t support this option; - you do not support

Re: [CMake] Installing a list of components

On 18 August 2016 at 17:32, Klaim - Joël Lamotte <mjkl...@gmail.com> wrote: > The discussion led to a ticket for a potential feature: https://gitlab. > kitware.com/cmake/cmake/issues/15450 > Discussion ended there: http://public.kitware.com/pipermail/cmake/2015- > March/0

Re: [CMake] Installing a list of components

On 18 August 2016 at 17:26, wrote: > I’m working on an application which consists of many different components > surrounding a common core. We ship multiple products from the same source > tree by adding and/or removing components from the output application >

Re: [cmake-developers] CMake Daemon blog

roken when I added some basic protocol features > earlier in the same fork). > > I could use some help in this task that does not involve C++ coding:-) > > Best Regards, > Tobias > Am 14.02.2016 12:58 schrieb "Klaim - Joël Lamotte" <mjkl...@gmail.com>: > >&

Re: [cmake-developers] CMake Daemon blog

I'm surprised too that there isn't more feedback around here. This seems to be a marjor potential improvement and definitely necessary if CMake need to be usable in the coming years. On 10 February 2016 at 09:42, Tobias Hunger wrote: > Hey, I did send a MR on github:-)

Re: [CMake] Cannot set FOLDER property to an interface (header-only) target

gt; Sincerely, Jakob > > > On 02 Jan 2016, at 13:12, Klaim - Joël Lamotte <mjkl...@gmail.com> wrote: > > > > On 1 January 2016 at 11:00, Jakob van Bethlehem <jsvanbethle...@gmail.com> > wrote: > >> Hej Joël, >> >> The command you’re loo

Re: [CMake] Cannot set FOLDER property to an interface (header-only) target

On 31 December 2015 at 17:19, Nils Gladitz wrote: > On 31.12.2015 14:19, David Cole via CMake wrote: > >> I can't think of a reason why we would not whitelist the FOLDER >> property... Unless somebody else chimes in with one, perhaps you could >> submit a proposed patch to

Re: [CMake] Cannot set FOLDER property to an interface (header-only) target

files, not with targets. With targets you need to set the FOLDER property. > Sincerely, > Jakob > > > On 30 Dec 2015, at 20:52, Klaim - Joël Lamotte <mjkl...@gmail.com> wrote: > > The following CMake script: > > cmake_minimum_required(VERSION 3.4) > >

[CMake] Cannot set FOLDER property to an interface (header-only) target

The following CMake script: cmake_minimum_required(VERSION 3.4) add_library( mylib INTERFACE ) set_property( TARGET mylib PROPERTY FOLDER /some/dir ) Will trigger this error on configuration: CMake Error at CMakeLists.txt:4 (set_property): INTERFACE_LIBRARY targets may

Re: [CMake] Protobuf Libraries not found on OS X

On 3 September 2015 at 19:48, Michael Jackson wrote: > I have compiled the Protocol Buffer library on OS X and I am using the > following CMake code to try and find the compiled libraries: > > find_package(Protobuf REQUIRED) > > > but when configuring I get the usual

Re: [CMake] How to use lib from include_external_msproject

On 20 August 2015 at 17:33, Howard Rubin howard.ru...@hl.konicaminolta.us wrote: I have a C++/CLI LIB (and DLL) that I generate with include_external_msproject. I need to link to it from my C++ project, which I’m trying to do with target_link_libraries. This gives the below error message.

Re: [CMake] Modern superbuild template including support for

On 21 August 2015 at 00:43, Klaim - Joël Lamotte mjkl...@gmail.com wrote: On 21 August 2015 at 00:35, Andrey Pokrovskiy wonder.m...@gmail.com wrote: And are you able to browse the source code of all your dependencies (that were downloaded)? I forgot to say that indeed if you use

Re: [CMake] Modern superbuild template including support for

On 20 August 2015 at 22:11, Knox, Kent kent.k...@amd.com wrote: I can vouch that the superbuild project works fine both for visual studio and for xcode. Using visual studio as an example, you generate a visual studio solution which downloads and compiles all dependencies, inclulding the

Re: [CMake] Modern superbuild template including support for

On 21 August 2015 at 00:35, Andrey Pokrovskiy wonder.m...@gmail.com wrote: And are you able to browse the source code of all your dependencies (that were downloaded)? I forgot to say that indeed if you use ExternalDependencies OR any non-source based way of linking your dependencies to your

[cmake-developers] [patch] ExternalProject: Removed implicit hg update on hg clone.

Please find attached a patch fixing ExternalProject_Add() which update mercurial repositories _twice_, which can lead to too long cloning transactions (in particular when there are subrepos in the default branch), which can lead transaction abort by repository servers. I found the issue in such

[CMake] ExternalProject_Add_StepDependencies parallel download/cloning

I am setting up a bunch of dependencies using ExternalProject module. One of the dependencies, say A, needs another dependency B to be built before A can be built. ExternalProject_Add_StepDependencies solves the problem fine. However, I did it this way: ExternalProject_Add_StepDependencies( A

Re: [CMake] Using ExternalProject_Add when CMakeFiles.txt is not in the root directory.

, 2015, at 5:14 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote: I am attempting to use ExternalDependencies_Add with the last Protobuf version (v3.0.0) which is in alpha3 (I'm using the master branch actually)[1]. If you don't already know: contrary to previous Protobuf version, v3.x provides

Re: [CMake] ExternalProject_Add_StepDependencies parallel download/cloning

(for example, ALL configurations for ALL architectures, each combination of which is a separate EP_Add call...) HTH, David C. Very interesting, I didn't think about that. I'll experiment with it ASAP, thanks for the suggestion. On Fri, Jul 17, 2015 at 12:53 PM, Klaim - Joël Lamotte mjkl

[CMake] Using ExternalProject_Add when CMakeFiles.txt is not in the root directory.

I am attempting to use ExternalDependencies_Add with the last Protobuf version (v3.0.0) which is in alpha3 (I'm using the master branch actually)[1]. If you don't already know: contrary to previous Protobuf version, v3.x provides cmake scripts (and also makes CMake's FindProtobuf module unusuable

Re: [CMake] How does :: actually works?

On 17 June 2015 at 22:58, Stephen Kelly steve...@gmail.com wrote: Klaim - Joël Lamotte wrote: Thinking about boost, if package files works well with header-only libraries (which I suppose it should as long as the boost define header-only targets) then it would be very useful indeed

Re: [CMake] How does :: actually works?

On 17 June 2015 at 20:50, Stephen Kelly steve...@gmail.com wrote: Klaim - Joël Lamotte wrote: I didn't realize at all that the FindPackage way is supposed to be obsolete now. It is not obsolete, but it is not a good approach (since CMake 2.6.0 already) if the upstream uses cmake, because

Re: [CMake] How does :: actually works?

On 16 June 2015 at 11:49, Johannes Zarl-Zierl johannes.zarl-zi...@jku.at wrote: On Monday 15 June 2015 22:43:41 you wrote: Just a last question: I assume that most find module scripts distributed with cmake are not using this feature at the moment, right? Sadly, no. After reading your

Re: [CMake] How does :: actually works?

On 13 June 2015 at 22:29, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Thursday, June 11, 2015 19:18:55 Klaim - Joël Lamotte wrote: On 11 June 2015 at 15:22, Johannes Zarl-Zierl johannes.zarl-zi...@jku.at wrote: Hi, I tried several times now to find documentation about

Re: [CMake] How does :: actually works?

On 15 June 2015 at 18:20, Johannes Zarl-Zierl johannes.zarl-zi...@jku.at wrote: On Monday 15 June 2015 16:40:10 Klaim - Joël Lamotte wrote: So far I didn't get what imported targets helps with, so I'm a bit lost on the usefulness of namespaces but I am sure that I am missing something

Re: [CMake] How does :: actually works?

On 11 June 2015 at 15:22, Johannes Zarl-Zierl johannes.zarl-zi...@jku.at wrote: Hi, I tried several times now to find documentation about how to define and use target names which seem to have namespaces, like Qt ones. For example: add_executable( MyProject::some_target ... ) AFAIK

[CMake] How does :: actually works?

Hi, I tried several times now to find documentation about how to define and use target names which seem to have namespaces, like Qt ones. For example: add_executable( MyProject::some_target ... ) I can't find any documentation or even name for this. Is it considered a namespace? In any way I

Re: [cmake-developers] Virtual folders in Visual studio get expanded on reload

I did notice it quite a lot but I don't think CMake can do anything about it. I might be wrong though. On Tue, Jun 2, 2015 at 1:00 AM, Roman Wüger roman.wue...@gmx.at wrote: Hi, I noticed that sometimes when a target is reloaded, that the virtual folders and targets for the complete visual

Re: [CMake] [cmake-developers] Virtual folders in Visual studio get expanded on reload

I did notice it quite a lot but I don't think CMake can do anything about it. I might be wrong though. On Tue, Jun 2, 2015 at 1:00 AM, Roman Wüger roman.wue...@gmx.at wrote: Hi, I noticed that sometimes when a target is reloaded, that the virtual folders and targets for the complete visual

Re: [CMake] Using the FindBoost package

I might be wrong but maybe you mixed up BOOST_INCLUDEDIR and Boost_INCLUDE_DIR? (note the additional underscore) From the documentation the first one is read to deduce the second one. Their name is unfortunately very close. I never tried to use BOOST_INCLUDEDIR directly, I only set a BOOST_ROOT

Re: [CMake] Using the FindBoost package

On Sat, May 9, 2015 at 12:22 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote: I might be wrong but maybe you mixed up BOOST_INCLUDEDIR and Boost_INCLUDE_DIR? (note the additional underscore) From the documentation the first one is read to deduce the second one. To clarify: BOOST_INCLUDEDIR

Re: [CMake] FindBoost.cmake issue while targeting 32-bit build on Linux 64-bit

I believe that this issue is with Boost not having a way to specify which target architecture is the build, which prevent any CMake script to be able to identify which build is installed. Assuming that the build arch is the same than the OS is not useful on Windows where most applications still

Re: [CMake] External Packages?

On Sun, Apr 12, 2015 at 3:48 PM, Ruslan Baratov via CMake cmake@cmake.org wrote: Take a look at this project: https://github.com/ruslo/hunter Interesting, it have some similarities with CPM: https://github.com/iauns/cpm -- Powered by www.kitware.com Please keep messages on-topic and check

Re: [CMake] Running custom executable

On Mon, Apr 6, 2015 at 8:47 PM, Daniel Dilts dilts...@gmail.com wrote: I have a custom executable that does some codegen to produce an enumeration and a couple of tables. I need this to be run against each source file before actual compilation. It needs include directories and macro

Re: [CMake] List all binaries associated with a target.

On Sun, Mar 22, 2015 at 12:49 PM, Roman Bolshakov rool...@gmail.com wrote: Unfortunately, if my understanding is correct, this code cannot work with external dependencies as they are not targets. It should work with external dependencies which are imported targets. You just need to check

Re: [CMake] List all binaries associated with a target.

On Sun, Mar 22, 2015 at 1:22 PM, Roman Bolshakov rool...@gmail.com wrote: 2015-03-16 23:22 GMT+03:00 Klaim - Joël Lamotte mjkl...@gmail.com: Then you can invoke top-level cmake_install.cmake to install a subset of your project: DESTDIR=/destination/install/path cmake -DCOMPONENT=A -P

Re: [CMake] List all binaries associated with a target.

On Sat, Mar 14, 2015 at 9:51 PM, Roman Bolshakov rool...@gmail.com wrote: Here's an example function which addresses 1. It creates a string of generator expressions for direct and indirect dependencies of a target recursively. When all recursive invocations are done, it spits target-name-deps

Re: [CMake] List all binaries associated with a target.

On Mon, Mar 16, 2015 at 7:11 PM, Roman Bolshakov rool...@gmail.com wrote: I'm not totally sure install() does exactly what I need. My use case is that I need to debug each executable in an installed-like context (with data), which imply that each time it is compiled it should be installed

Re: [CMake] List all binaries associated with a target.

On Mon, Mar 16, 2015 at 7:36 PM, Stephen Kelly steve...@gmail.com wrote: There might be space for a first class feature in cmake for 'make something that looks like the install tree at build time'. Please file an issue to track it. Thanks, Done:

Re: [CMake] List all binaries associated with a target.

On Mon, Mar 16, 2015 at 7:48 PM, Stephen Kelly steve...@gmail.com wrote: Klaim - Joël Lamotte wrote: I am looking for a (hopefully simple) way to do the following: 1. gather a list of paths of all the binaries associated with a target, that is all the linked dll/so and executable

Re: [CMake] List all binaries associated with a target.

is built so that it's always up to date while debugging. Now, I use post-build command (add_custom_command) to do this indeed but I didn't find a way yet to trigger install() a specific binary on post-build yet, but I suppose I just missed it so far. Roman 2015-03-14 4:24 GMT+03:00 Klaim - Joël

[CMake] List all binaries associated with a target.

I am looking for a (hopefully simple) way to do the following: 1. gather a list of paths of all the binaries associated with a target, that is all the linked dll/so and executable the target link or depend on. 2. copy these somewhere else. 3. take into account the build modes so that the right

Re: [cmake-developers] Review request: FindTBB module

​Hi, did you manage to improve over the DaxToolkit FindTBB module? Thanks for your time. -- 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

Re: [CMake] Building for 64 bit with Visual Studio 2013

I think adding a simple check (fatal-error) on the value of CMAKE_SIZEOF_VOID_P in your cmake files would help the user realise that they are not using the right generator? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] cmake-gui crash in Windows 8.1

On Fri, Jul 4, 2014 at 9:50 AM, Andrew Maclean andrew.amacl...@gmail.com wrote: Hi All, Has anyone noticed a problem with CMake 3.0 in Windows? I switched recently to CMake 3.0 for my project (uninstalled previous cmake, installed new cmake, changed cmake scripts version requirement to 3.0) I

Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?

My way of dealing with this problem is similar to other people here: 1. I have a separate Python post-build script designed to be driven through command line. This script read somewhere the list of direct binary dependencies of the target[1] and copy them in the output directory. The

Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?

On Mon, May 26, 2014 at 5:08 PM, Dan Kegel d...@kegel.com wrote: On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte mjkl...@gmail.com wrote: - Why can't I use the install command from CMake? My understanding is that it's used to install the application in the system Not really. It's

Re: [CMake] CMake Tools for Visual Studio 1.1 RC1 Available

On Tue, Jan 28, 2014 at 2:32 AM, David Golub golu...@gmail.com wrote: I just put out the first release candidate of CMake Tools for Visual Studio 1.1. This release will add support for CMake 2.8.12 and Visual Studio 2013. It also contains a number of minor enhancements and bug fixes. It is

Re: [CMake] CMake Tools for Visual Studio 1.1 RC1 Available

Looks like the right download page was http://cmaketools.codeplex.com/releases/view/117807 Installing now. -- 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

Re: [CMake] The Visual Studio project file inclusion problems.

Hi, CMake 2.8.11 solves a lot of dependency tracking issues with normal CMake targets, which helps a lot! Unfortunately, the above issues I described months ago are still there. It wouldn't be a problem if I didn't need, for example, source versions of Protobuf and Intel TBB to work, which both

Re: [cmake-developers] [CMake] Announcing CMake Tools for Visual Studio

On Wed, May 15, 2013 at 1:04 AM, David Golub golu...@gmail.com wrote: I’m pleased to announce the first release candidate of CMake Tools for Visual Studio, an extension adding support for syntax highlighting and IntelliSense in CMake code using Microsoft Visual Studio. The extension is open

Re: [CMake] Announcing CMake Tools for Visual Studio

On Wed, May 15, 2013 at 1:04 AM, David Golub golu...@gmail.com wrote: I’m pleased to announce the first release candidate of CMake Tools for Visual Studio, an extension adding support for syntax highlighting and IntelliSense in CMake code using Microsoft Visual Studio. The extension is open

Re: [CMake] [Boost-users] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.

On Tue, Apr 16, 2013 at 9:15 AM, Slava viatcheslav.sysolt...@h-d-gmbh.dewrote: 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

Re: [CMake] [Boost-users] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.

On Tue, Apr 16, 2013 at 12:32 PM, Slava viatcheslav.sysolt...@h-d-gmbh.dewrote: 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

Re: [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.

On Tue, Apr 16, 2013 at 3:16 PM, Andreas Haferburg ahaferb...@scopis.comwrote: 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 dir. Most people know how to rename a

Re: [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.

On Thu, Oct 11, 2012 at 2:19 PM, Klaim - Joël Lamotte mjkl...@gmail.comwrote: 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

Re: [CMake] Potential bug to set a working directory for test

On Thu, Apr 4, 2013 at 4:56 PM, Klaim - Joël Lamotte mjkl...@gmail.comwrote: I didn't file the ticket(s?) yet, I'm a bit pressed by time, but I'll do it before tomorrow. Sorry for the delay, I did it today: http://www.cmake.org/Bug/view.php?id=14089 Joel Lamotte -- Powered

Re: [CMake] Potential bug to set a working directory for test

On Thu, Apr 4, 2013 at 2:53 PM, Martin Weber m.we...@razorcat.com wrote: If your binary dir resides on a different drive than E:, the generated command will not work. Remember, cd on windows does not change the drive. The generated command should be cd /D E:/projects... No all the file

Re: [CMake] Potential bug to set a working directory for test

No feedback yet, so I suppose I should post a issue ticket. Joel Lamotte -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

[CMake] Potential bug to set a working directory for test

Hi, I'm using CMake 2.10.2 the VS2012(VC11) generator. I summed-up my problem in the last paragraph. I'm trying to do this: add_test( NAME ${TEST_PROJECT_NAME} WORKING_DIRECTORY ${TEST_WORKING_DIR} COMMAND ${TEST_PROJECT_NAME} ) In my current setup, I need ${TEST_WORKING_DIR} to be

Re: [CMake] Static and DLL builds in single solution

For example: add_library( mylibStatic STATIC ${MYLIB_ALL_SOURCES} ) # generate the static version of the lib add_library( mylibDLL SHARED ${MYLIB_ALL_SOURCES} ) # generate the dll loaded at startup version of the same lib, same sources add_library( mylibExtension MODULE ${MYLIB_ALL_SOURCES} ) #

Re: [CMake] The Visual Studio project file inclusion problems.

Sorry to bump this, but I would really like some feedback on either I'm being wrong or correct on these points? Thanks for your time. Joel Lamotte -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages

Re: [CMake] cmake trouble

Hi, On Mon, Oct 22, 2012 at 5:35 PM, 张峰 fangler2...@126.com wrote: 1.if i put TARGET_LINK_LIBRARIES(fan test) before ADD_EXECUTABLE command,this does not work ,why?? Because until yout call add_executable(), the target name doesn't exist. You have to use the target name as first parameter

[CMake] The Visual Studio project file inclusion problems.

I'm use CMake 2.8.9. Here is a summary of my understanding of what problem occurs when you try to add a library that only have a visual studio project file, in your project that is based on CMake. I would like to have confirmations and also maybe some help about the global issues I didn't find a

[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 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

Re: [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.

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-version/Modules/FindBoost.cmake, in particular the variable BOOST_LIBRARYDIR. On Thu, Oct 11, 2012 at 1:29 PM, Miller, Frank fmil...@sjm.com wrote:

Re: [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.

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-version/Modules/FindBoost.cmake, in particular the variable BOOST_LIBRARYDIR. On Thu, Oct 11, 2012 at 1:29 PM, Miller, Frank fmil...@sjm.com wrote:

Re: [CMake] Boost_DIR

I might be wrong but my understanding is that it's the other way arround: you provide Boost_DIR (root of your boost installation) and it finds the rest itself. I've been using it like that. I have a custom build of boost in a specific directory and an environnement variable Boost_DIR set to it. I

Re: [CMake] cmake + VS 2012

On Tue, Sep 4, 2012 at 11:20 AM, Biddiscombe, John A. biddi...@cscs.chwrote: I had a lot of trouble with cmake and VS 2010 due to the IDE crashing when projects were regenerated by cmake and having to click reload millions of times. Can anyone tell me if things are better with visual studio

Re: [CMake] cmake + VS 2012

On Tue, Sep 4, 2012 at 1:16 PM, Biddiscombe, John A. biddi...@cscs.chwrote: Thanks. that’s good to know. (I suspect that because I do a lot of cmakelists.txt editing on large projects that I get hit harder than most by the macro problem). Maybe, also if you don't have very big

[CMake] [Cmake] Retrieve all runtime dependencies

Hi, Is there any way in CMake to get a list of all binaries related to one target? What I mean is that assuming I have a target, say a library lib_a, that depends on lib_b and lib_c which are either SHARED or MODULE (so they produce a .dll/.so), is there a way or macro to get a string with the

Re: [CMake] [Cmake] Retrieve all runtime dependencies

On Mon, Sep 3, 2012 at 6:45 PM, John Drescher dresche...@gmail.com wrote: take a look at the GetPrerequisites cmake module. Thanks, I didn't know about this. Joel Lamotte -- Powered by www.kitware.com Visit other Kitware open-source projects at

[CMake] Cmake 2.8.9 : finding boost library files

Hi, I just switch form CMake 2.8.8 to 2.8.9. The CMake files worked before. I'm using a (non-modified) build from source of Boost 1.50, finding it with FindBoost module. I'm using VS2011 RC on Win 7 64bit. (the project I generate isn't 64 bit though). Now I got this error: CMake Error: The

Re: [CMake] Cmake 2.8.9 : finding boost library files

I forgot to add: I don't know if it is related to this last bugfix: http://public.kitware.com/Bug/view.php?id=13195 The problem is that i downloaded CMake 2.8.9 Win32 Installer about an hour ago, so I'm not sure if this bugfix is in or not - so I don't know if it fixes my problem. Joel Lamotte

Re: [CMake] Cmake 2.8.9 : finding boost library files

I misread, it is in the version I use and don't fix the problem. I'm surprised nobody else have the problem. Here is the parts of the log related to Boost while generating the project: 1. There is a first find done in one CMakeLists.txt file: [ C:/Program Files (x86)/CMake

Re: [CMake] Cmake 2.8.9 : finding boost library files

Okay I was intrigued and added Boost debug info in the CMake file of the project that is generating the initial error. I had this: find_package( Boost COMPONENTS system date_time filesystem chrono thread program_options log log_setup ) if( NOT Boost_FOUND ) message( Boost was NOT

Re: [CMake] UTILITY library?

I apparently fixed the problem by using add_dependencies() instead of target_link_libraries() ... Klaim / Joel Lamotte -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake

[CMake] UTILITY library?

, but I don't understand at all this error... Thanks for your attention. Klaim / Joël Lamotte. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http

Re: [CMake] CMake creates incompatible VS 2012 (VS 11) solution

I'm using CMake 2.8.8 to generate VS2012 RC projects in Win 7 (with last updates), I have no such problem. The only problems I have seems to have been fixed in the trunk for CMake 2.8.9 but I didn't try. I never seen the problem you present, but if you use the same version of CMake than me, then

Re: [CMake] Visual Studio 2012 Beta: unable to compile individual files

Hi, I'm having the same problem with a project generated with CMake 2.8.8 to VS2010 open with VS2012 RC. On Wed, Jun 13, 2012 at 3:20 AM, Ben Medina ben.med...@gmail.com wrote: - Using the VS2010 generator, the project files have relative paths. VS2012RC can load 2010 project files without

Re: [CMake] Mastering CMake: which cmake version?

Thanks for the info. I just wanted to add that my interest in the book is not to understand the basics of CMake, but to get more info on how to manage big complex projects. I don't know for others but I tend to use CMake only on big projects only. Still I have a hard time sometime understanding

Re: [CMake] Mastering CMake: which cmake version?

On Sun, May 6, 2012 at 4:58 PM, Rahul Garg rahulgar...@gmail.com wrote: Hi. Just wondering, which version of CMake does Mastering CMake 5th edition cover? I am greatly interested too by an answer to this question. Joel Lamotte -- Powered by www.kitware.com Visit other Kitware open-source

Re: [CMake] Add IDE-specific projects

On Mon, Apr 30, 2012 at 13:56, Michael Wild them...@gmail.com wrote: You are looking for the MSVC [1] variable and the include_external_msproject [2] command Thank you very much, I can't believe I missed this one! Joël Lamotte -- Powered by www.kitware.com Visit other Kitware open-source

[CMake] Visual Studio project groups not working after conversion

Hi, I used the following code to add protobuf project to my solution: $-- script --$ if( MSVC ) include_external_msproject( libprotobuf ${CMAKE_CURRENT_SOURCE_DIR}/protobuf/vsprojects/libprotobuf.vcproj ) else() message( No project file set for protobuf for this

[CMake] Add IDE-specific projects

Hi, I'm having a hard time finding documentation about this: I have a library that provide IDE-specific project files, for example Visual Studio project files. Instead of writing CMake file for it, I just want to write in my CMakeFiles.txt that if the target compiler is MSVC, I want to include

[CMake] Dependency on library in a separate branch

A include+link B? The real code is open source so I can show you exactly what is my current setup if it helps (but I guess it's a noob question...) Klaim - Joël Lamotte ___ Powered by www.kitware.com Visit other Kitware open-source projects at http

Re: [CMake] Dependency on library in a separate branch

obvious but can't find why it don't work with aosdesigner project that now requires aoslcpp Klaim - Joël Lamotte ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep

Re: [CMake] Dependency on library in a separate branch

2011/6/27 Klaim - Joël Lamotte mjkl...@gmail.com The full repostory is up to date now there: http://code.google.com/p/art-of-sequence/source/browse/ In tools directory, project A is aosdesigner, project B is aoslcpp, project C is the test project under aoslcpp. In case it helps, what I