Re: [CMake] ExternalProject_Add Visual Studio build Install Target

On Sat, Aug 31, 2019 at 9:56 PM J Decker wrote: > Why does it seem I'm the only one with this problem? > This is an external CMakeLists.txt that fails. cmake_minimum_required(VERSION 3.15) set_property(GLOBAL PROPERTY USE_FOLDERS On) project( B ) include( ExternalProject )

Re: [CMake] ExternalProject_Add Visual Studio build Install Target

Why does it seem I'm the only one with this problem? I've recently updated this other portable system while I'm on the road, and the latest version of course fails the same way. The Current build output 1>-- Build started: Project: intershell

Re: [CMake] ExternalProject_Add() setting build command to run external project's makefile

It seems like the error might be related to the download/extract step. I think the fact that you are using the same dir for PREFIX, SOURCE_DIR and DOWNLOAD_DIR might be confusing things. I would try commenting out those three properties and see if it makes any difference, and then you can

[CMake] ExternalProject_Add() setting build command to run external project's makefile

Hello First off, much thanks to all the contributors of cmake. A truly invaluable build utility. Your efforts are greatly appreciated. I've been successfully using cmake to build an external project (the client library for redis, hiredis) that has already been downloaded. I was able to do this

[CMake] ExternalProject_Add() Trouble Invoking Build Command to run the projects makefile

set(HIREDIS_DIR ${CMAKE_CURRENT_SOURCE_DIR}/hiredis) set(HIREDIS_INCLUDE_DIRS ${HIREDIS_DIR}/include) ExternalProject_Add(hiredis URL https://github.com/redis/hiredis/archive/v0.9.0.tar.gz PREFIX ${CMAKE_CURRENT_BINARY_DIR}/hiredis SOURCE_DIR ${CMAKE_CURRENT_BINARY_DIR}/hiredis

[CMake] ExternalProject_Add Visual Studio build Install Target

I've had to make this modification the last few versions... cmake/share/cmake-3.14/Modules/ExternalProject.cmake line 1870 from if(step STREQUAL "INSTALL") list(APPEND args --target install) endif() to if(step STREQUAL "INSTALL") list(APPEND args --target

[CMake] externalproject_add & install( target ... )

hello, world!sorry for my english:I have several libraries that come to me in archives compiled with their header files. for unpacking and configuring the primary method I use externalproject_add(). next, I need to install them and create configuration scripts for further importing into several

Re: [CMake] ExternalProject_Add and Git Update? How do I make these work?

to the github version. Try a "git pull" there manually to see what happens then. HTH kris -Original Message- From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Michael Jackson Sent: 22 December 2017 19:51 To: CMake Mail List <cmake@cmake.org> Subject: [CMake] Ext

Re: [CMake] ExternalProject_Add and Git Update? How do I make these work?

> ExternalProject_Add(${extProjectName} > GIT_REPOSITORY "git://github.com/BlueQuartzSoftware/discount.git" > GIT_PROGRESS 1 > #GIT_TAG master > > TMP_DIR "${DREAM3D_SDK}/superbuild/${extProjectName}/tmp/${CMAKE_BUILD_TYPE}" > STAMP_DIR "${DREAM3D_SDK}/superbuild/${extProjectName}/Stamp" >

[CMake] ExternalProject_Add and Git Update? How do I make these work?

ExternalProject_Add(${extProjectName} GIT_REPOSITORY "git://github.com/BlueQuartzSoftware/discount.git" GIT_PROGRESS 1 #GIT_TAG master TMP_DIR "${DREAM3D_SDK}/superbuild/${extProjectName}/tmp/${CMAKE_BUILD_TYPE}" STAMP_DIR "${DREAM3D_SDK}/superbuild/${extProjectName}/Stamp"

[CMake] externalproject_add install_dir doesn't work

A smiple cmakelists like this. Without specifying the CMAKE_ARGS CMAKE_INSTALL_PREFIX this tries to install into c:\program files. - cmake_minimum_required(VERSION 3.6) include( ExternalProject ) ExternalProject_Add( external PREFIX ${CMAKE_BINARY_DIR}/tmpout SOURCE_DIR

[CMake] ExternalProject_Add fails with gcc-4.9.3

cmake version 3.4.3 Hi, I have ExternalProject_Add (attached), which works with gcc-4.4.7, but fails with gcc-4.9.3: ... ... [100%] Performing build step for 'ep_netcdf' CMake Error at /scratch/tesari/build/cee/gnu.dbg/netcdf/src/ep_netcdf-stamp/ep_netcdf-build -DEBUG.cmake:16

Re: [CMake] ExternalProject_Add and include_external_msproject dynamic duo... but what if their powers combined?

crickets crickets... crickets... That's the response I get from the internet? Here are some other interesting bits: https://cmake.org/cmake/help/v3.8/manual/cmake-packages.7.html Does not make any reference to configure_package_config_file in

Re: [CMake] ExternalProject_Add ... output directy (sln file directory)

Also, I have try with a sample, just a main and a lib. But it seems that the lib CMakeLists.txt file is not called ! The project is created, but it does not point to the source code by example and the "message" are not displayed in the console too ! The download link :

Re: [CMake] ExternalProject_Add ... output directy (sln file directory)

BTW, I notice this too, if I use the following command line with an empty cmakelists.txt file : cmake -G "Visual Studio 15 2017 Win64" And it also generate the .sln (and other files) in the same folder, but I don't request to build such a solution ! right ? In reality, I only need a

Re: [CMake] ExternalProject_Add and include_external_msproject dynamic duo... but what if their powers combined?

Apologies for not responding sooner... this fell off my radar and I found it in my email. On Thu, Jan 12, 2017 at 6:29 AM, David Cole wrote: > Why not just use a BUILD_COMMAND which builds the VS project using the > msbuild command line directly? Do you have an example of this? Even if this

Re: [CMake] ExternalProject_Add ... output directy (sln file directory)

Do give it a BINARY_DIR, but do NOT give it a BUILD_COMMAND. Giving it an empty BUILD_COMMAND means "do nothing" for the build step and using "cmake --build ./LibraryBuild" does not work unless cmake is in your PATH, and with a Visual Studio solution, you also need to specify "--config Release" or

[CMake] ExternalProject_Add ... output directy (sln file directory)

Hi, I'm currently using one CMakeLists.txt file that will execute an external CMakeLists.txt (and dependency). For this I use the ExternalProject_Add command, but I can't find a way to specify where the ".sln" file will be generated. I have also created StackOverflow question here with

[CMake] ExternalProject_add not buing launched

Hello, I am trying to set my Cmake project to build the "xmlrpc-c" library, which is built using autotools. I was somewhat able to set it up following this example: http://mirkokiefer.com/blog/2013/03/cmake-by-example/ My resulting CMakeList is the following: ExternalProject_Add(

Re: [CMake] externalproject_add and generating sources

Oh ok, I see how it works, it makes sense, but I'm somehow disappointed : in order to use it, I'm going to have to change my own project while I originally thought it was going to be a kind of FindXXX on steroid... I'll give it a try though, tx for pointing it out. David Le 26 janvier 2017

Re: [CMake] externalproject_add and generating sources

Hello, Yes, main reason is I had to hack FindProtobuf.cmake to make our existing project compile. Also since I need to make it "installable", I had to add some stuff to have the binaries and header installed automatically when referenced. The latter reason led me to experiment with

Re: [CMake] externalproject_add and generating sources

> On Jan 26, 2017, at 1:23 AM, David Jobet wrote: > > Hello, > > suppose I want to use protobuf and integrate it in my project with > externalproject_add. (actually, I just have precompiled binaries and libs + > header files, I don't have the full sources) > Once the

Re: [CMake] externalproject_add and generating sources

You'll also want to build your own project with ExternalProject, and use the DEPENDS option to control build order. This ensures that all dependencies are fully installed before your own project is even configured. The project with all the ExternalProject calls is typically called a superbuild,

[CMake] externalproject_add and generating sources

Hello, suppose I want to use protobuf and integrate it in my project with externalproject_add. (actually, I just have precompiled binaries and libs + header files, I don't have the full sources) Once the project has been 'built' (actually, installed by a custom rpm-like tool to a shared path),

Re: [CMake] ExternalProject_Add

That is a good point. I found that a side effect of the superbuild is that my project can be built independently and I can distribute it without the superbuild parent project. Thanks Nicholas! On Sun, Jan 22, 2017 at 10:33 PM Nicholas Braden wrote: > Yes, that is

Re: [CMake] ExternalProject_Add

Yes, that is what I do in my superbuilds. Generally I make is such that my project could be built without the superbuild, and the superbuild is just a convenience. On Sat, Jan 21, 2017 at 12:17 PM, Saad Khattak wrote: > >> One possibility is the often mentioned superbuild

Re: [CMake] ExternalProject_Add

>> One possibility is the often mentioned superbuild That is a tempting and I started to go down that route - however, I ran into a problem where my project (which is now also built using ExternalProject_Add) does not have access to the CMake variables. Is the only solution to pass them through

Re: [CMake] ExternalProject_Add

I found this solution helpful: https://crascit.com/2015/07/25/cmake-gtest It is unfortunate that CMake doesn't have a proper way to accomplish this. --James On Sun, Jan 8, 2017 at 10:07 PM, Hendrik Sattler wrote: > One possibility is the often mentioned superbuild,

[CMake] ExternalProject_Add and include_external_msproject dynamic duo... but what if their powers combined?

Every time I create a superbuild using ExternalProject_Add sooner or later a project will not support cmake, but will have buried within its bowels a visual studio solution project .sln and sometimes gobs of .vcxproj files (read CPython). Now ofcourse include_external_msproject can do this.

Re: [CMake] ExternalProject_Add

One possibility is the often mentioned superbuild, another is not using find_library() but setting the variables with the library file paths manually (that's static info anyway). Am 8. Januar 2017 22:49:52 MEZ schrieb Saad Khattak : >Hello, > >I have an external project

Re: [CMake] ExternalProject_Add

The way to solve this is to use a superbuild project layout - you use ExternalProject_Add to build your dependencies AND your own project, using the DEPENDS option to control build order. Thus by the time it gets around to configuring your project, the dependencies have already been built and

[CMake] ExternalProject_Add

Hello, I have an external project glfw that I added to my project like this: == include(ExternalProject) ExternalProject_Add(glfw GIT_REPOSITORY "https://github.com/glfw/glfw.git; GIT_TAG "master" SOURCE_DIR "${CMAKE_SOURCE_DIR}/dep/glfw" CMAKE_ARGS -DGLFW_BUILD_DOCS=OFF

Re: [CMake] ExternalProject_Add : set the location of CMakeLists.txt

It's not listed in changelog though : https://cmake.org/cmake/help/v3.7/release/3.7.html 2016-10-26 11:34 GMT+02:00 Benjamin Ballet : > Ok I'm quiet lucky : There is what I need in CMake 3.7 (SOURCE_SUBDIR) > > 2016-10-25 19:54 GMT+02:00 Konstantin Podsvirov

Re: [CMake] ExternalProject_Add : set the location of CMakeLists.txt

Ok I'm quiet lucky : There is what I need in CMake 3.7 (SOURCE_SUBDIR) 2016-10-25 19:54 GMT+02:00 Konstantin Podsvirov : > Hello again. > > 25.10.2016, 20:31, "Konstantin Podsvirov" : > > Hello, Benjamin. > > > > 25.10.2016, 19:41, "Benjamin

Re: [CMake] ExternalProject_Add : set the location of CMakeLists.txt

Hello again. 25.10.2016, 20:31, "Konstantin Podsvirov" : > Hello, Benjamin. > > 25.10.2016, 19:41, "Benjamin Ballet via CMake" : >>  Hi, >> >>  I'm trying to get GLEW (https://github.com/nigels-com/glew) with >> ExternalProject_Add >>  It's buildable

Re: [CMake] ExternalProject_Add : set the location of CMakeLists.txt

Hello, Benjamin. 25.10.2016, 19:41, "Benjamin Ballet via CMake" : > Hi, > > I'm trying to get GLEW (https://github.com/nigels-com/glew) with > ExternalProject_Add > It's buildable with cmake but the CMakeLists.txt is in build/cmake directory. > > Is there a way to specify the

[CMake] ExternalProject_Add : set the location of CMakeLists.txt

Hi, I'm trying to get GLEW (https://github.com/nigels-com/glew) with ExternalProject_Add It's buildable with cmake but the CMakeLists.txt is in build/cmake directory. Is there a way to specify the directory of the CMakeLists.txt file ? If I change SOURCE_DIR it will only clone the repo in

Re: [CMake] ExternalProject_Add not honoring the INSTALL_DIR argument.

Hmm, you're right, I just tested and it seems the INSTALL_DIR is ignored or not handled properly, I'm not sure why. But if you use the CMAKE_ARGS option to manually set "-DCMAKE_INSTALL_PREFIX=/tmp/Fusion/qhull-2015.2" it works, so at least there's an easy workaround. Maybe someone else knows how

Re: [CMake] ExternalProject_Add not honoring the INSTALL_DIR argument.

So that was a typo on my part but changing it had no effect after deleting every build/download/tmp/stamp directory and trying again. -- Michael A. Jackson BlueQuartz Software, LLC [e]: mike.jack...@bluequartz.net Nicholas Braden wrote: Have you tried changing the = to a space, as with the

Re: [CMake] ExternalProject_Add not honoring the INSTALL_DIR argument.

Have you tried changing the = to a space, as with the other parameters? On Mon, Aug 29, 2016 at 10:52 AM, Michael Jackson wrote: > I have the following CMake file: > > set(QHull_GIT_REPO "git://github.com/qhull/qhull") > set(QHull_GIT_TAG "") > set(QHull_INSTALL_NAME

[CMake] ExternalProject_Add not honoring the INSTALL_DIR argument.

I have the following CMake file: set(QHull_GIT_REPO "git://github.com/qhull/qhull") set(QHull_GIT_TAG "") set(QHull_INSTALL_NAME "qhull") set(QHull_INSTALL_NAME "qhull-2015.2") ExternalProject_Add(${QHull_INSTALL_NAME} PREFIX ${Fusion_SDK_ROOT} URL

Re: [CMake] ExternalProject_Add + imported targets: no rule to make yourlibrary.so

On 4/28/2016 4:31 PM, SnakE wrote: set_target_properties(foo PROPERTIES IMPORTED_LOCATION foo.so) https://cmake.org/cmake/help/v3.0/prop_tgt/IMPORTED_LOCATION.html?highlight=imported_location "Full path to the main file on disk for an IMPORTED target." You need to use a full path to foo.so,

[CMake] ExternalProject_Add + imported targets: no rule to make yourlibrary.so

Hello, I think I've found a bug in the ninja generator. I wonder if it's fixed already in a more recent cmake version. I'm using cmake 3.3.1. My project uses ExternalProject_Add() to pull some pre-built binaries from an internal repository in some configurations. In other configurations however

Re: [CMake] ExternalProject_Add with flexible install commands

ct: Re: [CMake] ExternalProject_Add with flexible install commands Do you need to do it indirectly through a variable like this? If you just use: INSTALL_COMMAND "" directly in the ExternalProject_Add call, it will work. If you really need to do it indirectly, there's probably a way,

Re: [CMake] ExternalProject_Add with flexible install commands

t separated from preceding token by whitespace. > > Kent > > ____ > From: Petr Kmoch <petr.km...@gmail.com> > Sent: Thursday, February 25, 2016 2:46 AM > To: Knox, Kent > Cc: cmake@cmake.org > Subject: Re: [CMake] ExternalProject_Add wi

Re: [CMake] ExternalProject_Add with flexible install commands

..@gmail.com> Sent: Thursday, February 25, 2016 2:46 AM To: Knox, Kent Cc: cmake@cmake.org Subject: Re: [CMake] ExternalProject_Add with flexible install commands Hi Kent, I believe it's not "empty quotes" that disables the install command, it's the empty string. So you should

Re: [CMake] ExternalProject_Add with flexible install commands

Hi Kent, I believe it's not "empty quotes" that disables the install command, it's the empty string. So you should not escape the quotes: ### # Default behavior is to NOT install library, empty quotes should disable install set( libxxx_inst_comm INSTALL_COMMAND "" ) # Build

[CMake] ExternalProject_Add with flexible install commands

I am having a problem passing parameters as a variable into ExternalProject_Add(). I seem to be fighting syntax, i've tried many different variants with the set() statement ### # Default behavior is to NOT install library, empty quotes should disable install set(

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Ah, I ran into this quirk too - the issue is that you have the quotes incorrect: -DCMAKE_CXX_FLAGS="-march=native" Should be like this instead: "-DCMAKE_CXX_FLAGS=-march=native" Try that and see if it helps, I am pretty sure I ran into the exact same problem. On Thu, Jan 21, 2016 at 8:27 AM,

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Thanks for clarifying that external projects are not aware of the project they are embedded in. The CMAKE_COMPILER_IS_GNUCXX variable should be set automatically by CMake as far as I understand it (see https://cmake.org/Wiki/CMake_Useful_Variables). I narrowed down the problem by creating a

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Nice, thank you very much! This solves my problem. On Thu, Jan 21, 2016 at 3:56 PM, Nicholas Braden wrote: > Ah, I ran into this quirk too - the issue is that you have the quotes > incorrect: > > -DCMAKE_CXX_FLAGS="-march=native" > > Should be like this instead: > >

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Thanks for your suggestion! I consider trying it soon. On Wed, Jan 20, 2016 at 11:44 PM, Craig Scott <audiofana...@gmail.com> wrote: > > From: fkillus <fkil...@googlemail.com> >> To: cmake@cmake.org >> Cc: >> Date: Wed, 20 Jan 2016 18:41:26 +0100 >> Su

Re: [CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

Where/how is that variable normally set? External projects have no awareness of the project they are in, they just run CMake as usual the same way you would. If the variable is normally set by CMake itself, make sure that your containing project and the external project both find the same

[CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

> From: fkillus <fkil...@googlemail.com> > To: cmake@cmake.org > Cc: > Date: Wed, 20 Jan 2016 18:41:26 +0100 > Subject: [CMake] ExternalProject_Add() macro does not set > CMAKE_COMPILER_IS_GNUCXX > I have been trying to compile Ogre [1] as external dependency

[CMake] ExternalProject_Add() macro does not set CMAKE_COMPILER_IS_GNUCXX

I have been trying to compile Ogre [1] as external dependency with ExternalProject_Add(). In theory this should be straightforward since Ogre itself also uses CMake as buildsystem. However, in the process I encountered the following problem: Ogre checks the value of the CMAKE_COMPILER_IS_GNUCXX

Re: [CMake] ExternalProject_Add support for git clone -o option

Why would you like to have names other than origin? I am struggling to think of a use case for this, seeing as you never directly interact with the cloned repository. I don't even think it's safe to assume that a git repository is involved at all, for all you know it could be changed to just

[CMake] ExternalProject_Add support for git clone -o option

Hello all, I am reading through the ExternalProject source for 3.2 at the moment (if updating to 3.4 is the answer, great!) and trying to determine if there is support for the -o option when using a git repository. Has anyone accomplished this? I would like to have names other than "origin"

Re: [CMake] ExternalProject_Add support for git clone -o option

ca> Cc: cmake@cmake.org Subject: Re: [CMake] ExternalProject_Add support for git clone -o option Why would you like to have names other than origin? I am struggling to think of a use case for this, seeing as you never directly interact with the cloned repository. I don't even think it's safe to a

Re: [CMake] ExternalProject_Add support for git clone -o option

holas11bra...@gmail.com] Sent: Friday, January 15, 2016 12:02 PM To: Adam Rankin <aran...@robarts.ca> Cc: cmake@cmake.org Subject: Re: [CMake] ExternalProject_Add support for git clone -o option Why would you like to have names other than origin? I am struggling to think of a use case for this, see

Re: [CMake] ExternalProject_Add and inheritance

ic.dou...@inria.fr>> Date: Friday 11 December 2015 at 10:05 To: SAP SAP <marc.chevr...@sap.com<mailto:marc.chevr...@sap.com>> Cc: "cmake@cmake.org<mailto:cmake@cmake.org>" <cmake@cmake.org<mailto:cmake@cmake.org>> Subject: Re: [CMake] ExternalProject_Ad

Re: [CMake] ExternalProject_Add and inheritance

ngs are defined in the "classical" way). Best, Cédric - Mail original - > De: "Marc CHEVRIER" <marc.chevr...@sap.com> > À: "Cedric Doucet" <cedric.dou...@inria.fr>, cmake@cmake.org > Envoyé: Vendredi 11 Décembre 2015 08:44:38 > Obje

[CMake] ExternalProject_Add and inheritance

Hello, I use the ExternalProject_Add command to manage third-party libraries. In the same time, I need to overcome some compatibility problems between GCC 4 and GCC 5 (strings are not defined in the same way in the STL). The solution I use is the one given here:

Re: [CMake] ExternalProject_Add and inheritance

dou...@inria.fr<mailto:cedric.dou...@inria.fr>> Date: Thursday 10 December 2015 at 18:21 To: "cmake@cmake.org<mailto:cmake@cmake.org>" <cmake@cmake.org<mailto:cmake@cmake.org>> Subject: [CMake] ExternalProject_Add and inheritance Hello, I use the ExternalProject_Add

Re: [CMake] ExternalProject_Add and proxy

On 2015-10-21 18:07 GMT+02:00 Cedric Doucet wrote: > Hello Denis! > > Thank you for your answer. > Actually, there is no login and no password. > It's an academic proxy. > So the initial syntax of http_proxy should to be correct. Hello, CMake uses libcurl, so check your proxy settings with curl

Re: [CMake] ExternalProject_Add and proxy

t; <cedric.dou...@inria.fr> > Cc: cmake@cmake.org > Envoyé: Mercredi 21 Octobre 2015 17:35:47 > Objet: Re: [CMake] ExternalProject_Add and proxy > > On 2015-10-21 14:58 GMT+02:00 Cedric Doucet wrote: > > > > Hello, > > > > I try to download a library wit

Re: [CMake] ExternalProject_Add and proxy

On 2015-10-21 14:58 GMT+02:00 Cedric Doucet wrote: > > Hello, > > I try to download a library with ExternalProject_Add. > The URL is correct and the CMake script works well, except when there is a > proxy to define. > > The URL is : http://bitbucket.org/eigen/eigen/get/3.2.4.tar.gz > > After

[CMake] ExternalProject_Add and proxy

Hello, I try to download a library with ExternalProject_Add. The URL is correct and the CMake script works well, except when there is a proxy to define. The URL is : http://bitbucket.org/eigen/eigen/get/3.2.4.tar.gz After having set http_proxy=http://proxy.name.fr:1234

Re: [CMake] ExternalProject_Add // git shallow clone

It's possible to do anything you want if you provide your own custom DOWNLOAD_COMMAND. I'm not aware of any depth options exposed via ExternalProject_Add, though. HTH, David C. On May 5, 2015, at 5:19 AM, Sergei Nikulov sergey.niku...@gmail.com wrote: Hello All, Is it possible to

Re: [CMake] ExternalProject_Add // git shallow clone

It's possible to do anything you want if you provide your own custom DOWNLOAD_COMMAND. I'm not aware of any depth options exposed via ExternalProject_Add, though. HTH, David On May 5, 2015, at 5:19 AM, Sergei Nikulov sergey.niku...@gmail.com wrote: Hello All, Is it possible to provide

Re: [CMake] ExternalProject_Add // git shallow clone

Of course. It would be useful. Perhaps you could propose a patch to add it? On Tuesday, May 5, 2015, Sergei Nikulov sergey.niku...@gmail.com wrote: Hello David, Thank you for answer. It could be useful feature for ExternalProject.cmake What do your think? 2015-05-05 16:13 GMT+03:00

Re: [CMake] ExternalProject_Add // git shallow clone

Hello David, Thank you for answer. It could be useful feature for ExternalProject.cmake What do your think? 2015-05-05 16:13 GMT+03:00 David Cole dlrd...@aol.com: It's possible to do anything you want if you provide your own custom DOWNLOAD_COMMAND. I'm not aware of any depth options

[CMake] ExternalProject_Add // git shallow clone

Hello All, Is it possible to provide git depth option for ExternalProject_Add command? I see no such option for GIT_... parameters in documentation. Thank you. -- Best Regards, Sergei Nikulov -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] ExternalProject_Add not re-building when source changes

I don't like my current solution for such problem, but it works for me well. Note file(GLOB_RECURSE ... and custom copy step in the end. Also you can try to google cmake super build which probably will provide you more ideas. include(ExternalProject) set(WEBSOCKETS_PATCH_DIR

[CMake] ExternalProject_Add not re-building when source changes

I've used ExternalProject_Add to trick CMake into supporting two compilers to build my project. Part of my project needs OpenMP, but other parts do not. So, on MacOS, I would prefer to build most of the project with CLang, but the OpenMP requiring part with gcc. I have CMake set up to detect

Re: [CMake] ExternalProject_Add contributing to top-level Package

Ok, I think I've answered my own question... I added the following after the ExternalProject_Add command... ExternalProject_Get_Property( ALTBUILD BINARY_DIR ) INSTALL( PROGRAMS ${BINARY_DIR}/myprogram DESTINATION . ) Rob On Sat, Apr 4, 2015 at 12:57 PM, Rob McDonald rob.a.mcdon...@gmail.com

[CMake] ExternalProject_Add contributing to top-level Package

All, I have a project that is typically compiled with CLang/LLVM. However, I'm now adding a component that is preferentially built with OpenMP. CLang doesn't support OpenMP, so I'd like to build that component with GCC while still building everything else with CLang. So far, I'm approaching the

Re: [CMake] ExternalProject_Add, static library, Ninja generator

On 04/02/2015 07:15 AM, Charles Nicholson wrote: I'm assuming that I'm not correctly expressing the dependencies. Would anyone mind taking a quick look? I'd really appreciate it! Try adding the following to your ExternalProject_Add call: BUILD_BYPRODUCTS ${HIDAPI_ROOT}/bin/lib/libhidapi.a

Re: [CMake] ExternalProject_Add, static library, Ninja generator

On 04/02/2015 04:05 PM, Charles Nicholson wrote: Thanks for the quick response, Nils, that fixed it! I'm curious, though, why wasn't simply marking my lib as depending on the externalproject_add target enough? I like using the byproducts line since it's more exact and descriptive, but shouldn't

Re: [CMake] ExternalProject_Add, static library, Ninja generator

I see now; thank you for the explanation. Best, Charles On Thu, Apr 2, 2015, 7:17 AM Nils Gladitz nilsglad...@gmail.com wrote: On 04/02/2015 04:05 PM, Charles Nicholson wrote: Thanks for the quick response, Nils, that fixed it! I'm curious, though, why wasn't simply marking my lib as

Re: [CMake] ExternalProject_Add, static library, Ninja generator

Thanks for the quick response, Nils, that fixed it! I'm curious, though, why wasn't simply marking my lib as depending on the externalproject_add target enough? I like using the byproducts line since it's more exact and descriptive, but shouldn't it work without that? Thanks again, Charles On

[CMake] ExternalProject_Add, static library, Ninja generator

Hi all- I'm using ExternalProject_Add to pull down, configure, build, and install the OSS hidapi project. The output of the hidapi build is, among other things, a library called libhidapi.a. I'm creating an imported static library using add_library, and then using add_dependency to indicate that

[CMake] ExternalProject_Add + find_package

Hello, I am using cmake(I am a novice) for a big project, this contain multiple independent projects(no use add_subdirectory), so take an example: Project A depend of B, when I run cmake for A this check for B with find_package(), if this fail the user is notified and need install B, I think that

[CMake] ExternalProject_Add: directing cmake to a different path-to-source

I'm trying to get ExternalProject_Add to build a TPL that doesn't have a CMakeLists.txt file in the top-level directory. The TPL untars as foo/{A,B} where A and B each contain a CMakeLists.txt file and are independent of each other. I only want to build A and would like to have cmake run with

Re: [CMake] ExternalProject_Add: directing cmake to a different path-to-source

Specify a patch command that creates a toplevel cmake list with one 'add_subdirectory(A)' line. On Sun, 8 Feb 2015 4:14 am Neil Carlson neil.n.carl...@gmail.com wrote: I'm trying to get ExternalProject_Add to build a TPL that doesn't have a CMakeLists.txt file in the top-level directory. The

Re: [CMake] ExternalProject_add and add_subdirectory in one step

Hi Franz. The canonical approach to ExternalProject is to use a superbuild setup. Design your top-level CMakeList so that it *only* contains ExternalProject_add() calls, treating your original project as just another external project. Build the superbuild once, getting all the dependencies

[CMake] ExternalProject_add and add_subdirectory in one step

Hi, I try to clone an repository from my bare-repository and to build my project tree. Therefore I use the following commands: ExternalProject_Add ( demoA PREFIX ${MAIN_PATH}/demoA GIT_REPOSITORY ${REPOSITORY_PATH}/demoA GIT_TAG origin/master UPDATE_COMMAND

[CMake] ExternalProject_Add with custom build/make command for Boost

Hi, I am trying to build Boost (1.47.0) using CMake's ExternalProject_Add() I got it to build and install via it's bjam ./b2 install However, there is an implicit make install generated by CMake which will fail because there is no Makefile so to speak with an install target.

Re: [CMake] ExternalProject_Add with custom build/make command for Boost

INSTALL_COMMAND should work. (Assuming you're doing ./b2 install as the BUILD_COMMAND...?) Check out how the open chemistry project builds boost as an ExternalProject as a reference point: https://github.com/OpenChemistry/openchemistry/blob/master/cmake/External_boost.cmake HTH, David C. On

Re: [CMake] ExternalProject_Add dependency graph (dot/graphviz?) ?

On 09/22/2014 04:59 PM, Nicholas Yue wrote: Hi, CMake has graphviz output capability for dependency within a project. Is there a way to graph dependency at the ExternalProject_Add() level ? Cheers Hello Nicholas, Can you clarify your question a bit more? Do you mean 'show me the

Re: [CMake] ExternalProject_Add dependency graph (dot/graphviz?) ?

Hi Micha, My interest is in show me the dependencies the external project depends on I am considering migrating an in-house build system to build opensource projects to using CMake. As there are many external packages and versions (close to 100), I'd like to be able to visualize their

[CMake] ExternalProject_Add dependency graph (dot/graphviz?) ?

Hi, CMake has graphviz output capability for dependency within a project. Is there a way to graph dependency at the ExternalProject_Add() level ? Cheers -- Nicholas Yue Graphics - RenderMan, Visualization, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows

Re: [CMake] ExternalProject_Add always try to connect to SVN server

If you are using SVN_REVISION with a specific revision number like that, you can do: UPDATE_COMMAND because there is never any need to update after the initial checkout at that revision. If you then later change to another revision, the parameters to the svn checkout (dowload) step

[CMake] ExternalProject_Add always try to connect to SVN server

Hello, I'm wondering if I'm doing something wrong using ExternalProject_Add for a subversion repository. I would expect the following behavior: - First run, see if local copy of code has been checked out. If not 'svn checkout'. Fails if not connected to internet. - Consecutive runs: - if

Re: [CMake] ExternalProject_Add show sources in Visual Studio

. -Original Message- From: NoRulez noru...@me.com To: David Cole dlrd...@aol.com Cc: cmake cmake@cmake.org Sent: Wed, Mar 19, 2014 9:48 am Subject: Re: [CMake] ExternalProject_Add show sources in Visual Studio Ok, so the only workaround to archive this is to use file(GLOB_RECURS

Re: [CMake] ExternalProject_Add show sources in Visual Studio

Because the external projects depends on different library versions than the SuperProject. Maybe I misconfigured something, but i don't know an alternative. E.g.: super project (AA) builds with version 9 of library X. The external project B requires version 5 of library X and had some source

Re: [CMake] ExternalProject_Add show sources in Visual Studio

Well, that sounds like the perfect way to use ExternalProject. But why do you want to show the sources in Visual Studio? Just for ease of looking at them? As I said in my earlier reply... even if we showed the sources, editing them would not trigger a rebuild of the external project. The

Re: [CMake] ExternalProject_Add show sources in Visual Studio

Ok, so the only workaround to archive this is to use file(GLOB_RECURS...) and rebuild the changed external project. Right? Best Regards Am 19.03.2014 um 12:44 schrieb David Cole dlrd...@aol.com: Well, that sounds like the perfect way to use ExternalProject. But why do you want to show

Re: [CMake] ExternalProject_Add show sources in Visual Studio

/install in there, then go back to your containing project, and it's already up to date. To each his own... Good luck. HTH, David C. -Original Message- From: NoRulez noru...@me.com To: David Cole dlrd...@aol.com Cc: cmake cmake@cmake.org Sent: Wed, Mar 19, 2014 9:48 am Subject: Re: [CMake

[CMake] ExternalProject_Add show sources in Visual Studio

Hello, if I add an external project with ExternalProject_Add, is it possible to show the sources of that project in Visual Studio too? I don't know if this is the reason, but currently the projects type is set to utility. Best Regards -- Powered by www.kitware.com Please keep messages

Re: [CMake] ExternalProject_Add show sources in Visual Studio

I've added the source files with file(GLOB_RECURSE... and set source file property for each of these files with HEADER_FILE_OLY to TRUE. It seems to work, but I'm not sure if this is the right way. Am 17.03.2014 um 08:49 schrieb NoRulez noru...@me.com: Hello, if I add an external

  1   2   >