Re: [CMake] ADD_CUSTOM_TARGET USES_TERMINAL not printing out stuff

El 05/06/19 a las 11:51, Brad King escribió: On 6/5/19 8:27 AM, Gonzalo Garramuño wrote: This used to print out all that cpack was doing while it was doing it. Now with v3.15.0-rc1 it just sits there and outputs all the text at the end when it finishes, which sucks as it looks like it has hun

Re: [CMake] ADD_CUSTOM_TARGET USES_TERMINAL not printing out stuff

On 6/5/19 8:27 AM, Gonzalo Garramuño wrote: > This used to print out all that cpack was doing while it was doing it.  > Now with v3.15.0-rc1 it just sits there and outputs all the text at the > end when it finishes, which sucks as it looks like it has hung. Thanks for trying the release candidat

Re: [CMake] add_custom_target

Oh good point on OpenSSL, their official build steps are awkard enough, let alone trying to emulate them in CMake! For what it's worth, we've upgraded boost-cmake to Boost 1.65 so far with no changes required to any of the modules we use. The other 3rd party module manager we're looking into is

Re: [CMake] add_custom_target

Interesting project, so thanks for the link! The problem we have is that changing the build system for external projects isn’t really acceptable. In this boost-cmake build they ripped out jam and replaced it with cmake, which is kind of cool, but such action is not a good plan for OpenSSL. If I

Re: [CMake] add_custom_target

Hi Cameron, For boost integration into our cmake project, we're using this (slightly customised for our use): https://github.com/Orphis/boost-cmake It unzips boost into your build folder, and builds the required packages on demand (not all of boost, just the boost modules you use). It works

Re: [CMake] add_custom_target: COMMAND embedded make code

Solved problem from another post with similar space escaping. set(PARAMS "$(if $(verbose), --verbose)" "$(if $(xml-output), --xml-output)" "$(if $(run), --run=$(run))" "$(if $(suite), --suite=$(suite))" ) string(REPLACE " " ";" PARAMS ${PARAMS}) add_

Re: [CMake] Add_Custom_Target to copy a directory not working with Ninja on Windows

I dug through the ninja build files and found the exact command into a command prompt. The first time it worked. The second time it did not. Here is the output: C:\Users\admin>cmd.exe /C "cd /D C:\Users\admin\Workspace\DREAM3D_Rewrite\ninja\ Applications\DREAM3D && C:\DREAM3D_SDK\cmake-3.0.2-win32

Re: [CMake] add_custom_target: Compiling a Matlab function into a binary with mcc

On 26.07.2014 12:18, Ramón Casero Cañas wrote: Dear all, I have a Matlab function vmu2png.m (this is the source code), and I'd like to compile it into an executable/binary using a CMake project (cmake 2.8.11.2 on linux). To compile the function, I need to run Matlab's mcc program, e.g. "mcc

Re: [CMake] ADD_CUSTOM_TARGET

On 01/16/2013 02:21 PM, Andreas Pakulat wrote: Hi, On Wed, Jan 16, 2013 at 11:01 PM, wrote: The problem is that the script fails when using cmake 2.6. I want to know if this is expected or a bug ? I filed a bug report with Red-Hat 6, but they just decided to ignore it. See https://b

Re: [CMake] ADD_CUSTOM_TARGET

Hi, On Wed, Jan 16, 2013 at 11:01 PM, wrote: > The problem is that the script fails when using cmake 2.6. I want to know > if this is expected or a bug ? > > I filed a bug report with Red-Hat 6, but they just decided to ignore it. See > https://bugzilla.redhat.com/show_bug.cgi?id=896116

Re: [CMake] ADD_CUSTOM_TARGET

The problem is that the script fails when using cmake 2.6. I want to know if this is expected or a bug ? I filed a bug report with Red-Hat 6, but they just decided to ignore it. See https://bugzilla.redhat.com/show_bug.cgi?id=896116 Perhaps someone knows a way around this problem ? > On

Re: [CMake] ADD_CUSTOM_TARGET

On Tuesday 15 January 2013, Brad Bell wrote: > I am trying to build a project for Red-hat 6 which uses the following > cmake version > bradbell@gorst trash]$ cmake --version > cmake version 2.6-patch 4 > > While doing so I am having trouble with the ADD_CUSTOM_TARGET. To be > specifc, af

Re: [CMake] add_custom_target and PRE_BUILD commands added in sub-dir not executing

On 12 September 2012 14:50, Rolf Eike Beer wrote: > Am 2012-09-12 12:36, schrieb Brett Delle Grazie: > >> Hi, >> >> I've come across some strange behaviour when using add_custom_target and >> an >> add_custom_command( PRE_BUILD or PRE_LINK ) in nested projects. >> >> We have a number of static an

Re: [CMake] add_custom_target and PRE_BUILD commands added in sub-dir not executing

Am 2012-09-12 12:36, schrieb Brett Delle Grazie: Hi, I've come across some strange behaviour when using add_custom_target and an add_custom_command( PRE_BUILD or PRE_LINK ) in nested projects. We have a number of static analysis checks that were working using cppcheck. The technique was to

Re: [CMake] add_custom_target and Code Blocks generator

On Thursday 20 January 2011, Alexander Neundorf wrote: > On Thursday 20 January 2011, Dimitri Kaparis wrote: ... > > From the documentation at > > http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:add_custom_ta > >rg et > > > > "The SOURCES option specifies additional source files to be i

Re: [CMake] add_custom_target and output file dependencies

Yep, that looks like it will work - thanks! CY On Thu, Feb 10, 2011 at 11:21 AM, David Cole wrote: > Sorry. Correction here... Make that: > >   COMMAND ${CMAKE_COMMAND} -E touch > ${CMAKE_CURRENT_BINARY_DIR}/${targetprefix}.sentinel > > (The "touch" is the rather important part of that command l

Re: [CMake] add_custom_target and output file dependencies

Sorry. Correction here... Make that: COMMAND ${CMAKE_COMMAND} -E touch ${CMAKE_CURRENT_BINARY_DIR}/${targetprefix}.sentinel (The "touch" is the rather important part of that command line) On Thu, Feb 10, 2011 at 11:19 AM, David Cole wrote: > Are you using "make -j" for parallel builds b

Re: [CMake] add_custom_target and output file dependencies

Are you using "make -j" for parallel builds by any chance? Does it still happen if you use make without any -j flags...? Rather than: ADD_CUSTOM_COMMAND( OUTPUT ${outputlist} COMMAND ${CMAKE_COMMAND} -P ${CMAKE_CURRENT_BINARY_DIR}/${targetprefix}.cmake DEPENDS ${${data

Re: [CMake] add_custom_target and output file dependencies

On Thu, Feb 10, 2011 at 10:48 AM, David Cole wrote: > Show us the surrounding code (i.e. -- the actual copy command) - sorry, should have provided more detail. This is an example file that does the copying: SET(FILES_TO_COPY /home/user/brlcad/cmake/src/tclscripts/ami.tcl;/home/user/brlca

Re: [CMake] add_custom_target and output file dependencies

Show us the surrounding code (i.e. -- the actual copy command) On Thu, Feb 10, 2011 at 10:40 AM, Clifford Yapp wrote: > I'm seeing an extremely strange behavior with > add_custom_command/add_custom_target, and I'm not sure what's causing > it. > > Background: I'm trying to copy large numbers o

Re: [CMake] add_custom_target and Code Blocks generator

On Thursday 20 January 2011, Dimitri Kaparis wrote: > On Thu, Jan 20, 2011 at 7:27 PM, Alexander Neundorf > > wrote: > > On Thursday 20 January 2011, Dimitri Kaparis wrote: > >> Greetings, > >> > >> the Code Blocks generator is not adding to the project the sources, > >> specified in the command.

Re: [CMake] add_custom_target and Code Blocks generator

On Thu, Jan 20, 2011 at 7:27 PM, Alexander Neundorf wrote: > On Thursday 20 January 2011, Dimitri Kaparis wrote: >> Greetings, >> >> the Code Blocks generator is not adding to the project the sources, >> specified in the command. >> In order to add a group of header files to my project tree, I'm t

Re: [CMake] add_custom_target and Code Blocks generator

On Thursday 20 January 2011, Dimitri Kaparis wrote: > Greetings, > > the Code Blocks generator is not adding to the project the sources, > specified in the command. > In order to add a group of header files to my project tree, I'm trying > to implement the solution posted here: > http://www.cmake.o

Re: [CMake] add_custom_target dependency list issue

Am Montag 27 September 2010, 01:48:38 schrieb Szilárd Páll: > > No black magic, just cmake's rules about variable contents. > > Basically CMake has only 1 type of variable value, thats a string. What > > you created above is a string variable "DEPS" with the value "dep1 dep2 > > dep3", i.e. a singl

Re: [CMake] add_custom_target dependency list issue

On 09/26/2010 09:09 PM, Szilárd Páll wrote: >> The DEPENDS option of ADD_CUSTOM_TARGET() is meant for file-level >> dependencies only; use ADD_DEPENDENCIES() for target-level ones. > > Silly mistake, thanks for pointing it out. However, even if I add > target dependencies using ADD_DEPENDENCIES()

Re: [CMake] add_custom_target dependency list issue

> No black magic, just cmake's rules about variable contents. > Basically CMake has only 1 type of variable value, thats a string. What > you created above is a string variable "DEPS" with the value "dep1 dep2 > dep3", i.e. a single string consisting of 3 words separated by spaces. > Some strings a

Re: [CMake] add_custom_target dependency list issue

On 26.09.10 21:31:20, Szilárd Páll wrote: > I figured out something that makes me even more puzzled. The following > does _not_ work as expected:: > > set(DEPS "dep1 dep2 dep3") > add_dependencies(foo bar > ${DEPS}) > > Target "foo" gets only dependent on bar and n

Re: [CMake] add_custom_target dependency list issue

I figured out something that makes me even more puzzled. The following does _not_ work as expected:: set(DEPS "dep1 dep2 dep3") add_dependencies(foo bar ${DEPS}) Target "foo" gets only dependent on bar and not dep1,2,3. On the other hand, manually listing the latte

Re: [CMake] add_custom_target dependency list issue

> The DEPENDS option of ADD_CUSTOM_TARGET() is meant for file-level > dependencies only; use ADD_DEPENDENCIES() for target-level ones. Silly mistake, thanks for pointing it out. However, even if I add target dependencies using ADD_DEPENDENCIES() it seems to take into account only the dependent the

Re: [CMake] add_custom_target dependency list issue

On 09/26/2010 02:34 AM, Szilárd Páll wrote: > Hi, > > I implemented a custom target which depends on several other targets, > including some that I generate beforehand as custom targets and > collect their names in a variable. However, this seems to behave in a > strange way if I list these depend

Re: [CMake] add_custom_target problem

On Wednesday 09 June 2010 09:35 PM, Michael Wild wrote: On 9. Jun, 2010, at 17:47 , Hariharan Iyer wrote: This may not be only because of using add_custom_target, but I have the following problem. I have a custom target that depends on a generated file, as: add_custom_target(foo DEPENDS bar)

Re: [CMake] add_custom_target problem

On 9. Jun, 2010, at 17:47 , Hariharan Iyer wrote: > This may not be only because of using add_custom_target, but I have the > following problem. I have a custom target that depends on a generated file, > as: > add_custom_target(foo DEPENDS bar) > > where "bar" is a generated file, generated us

Re: [CMake] add_custom_target: always built during "make" and "make install"

Hi, I have done some experiments and I have found something interesting. Let's take my old example: === root/src/CMakeLists.txt === (build a shared library) # Compilation add_library( ${CMAKE_PROJECT_NAME} SHARED ${CMAKE_BINARY_DIR}/xsd/mapping_file.cxx) # XML mapping source files are gene

Re: [CMake] add_custom_target: always built during "make" and "make install"

On Mon, Nov 02, 2009 at 11:28:08PM +0800, Romain CHANU wrote: > 1. If there is a restriction / condition regarding the "out-of-date" > behavior, it might be good to update the documentation. Agreed, but I don't understand the behavior so I can't help with that. > 3. I am not 100% sure also... Any

Re: [CMake] add_custom_target: always built during "make" and "make install"

1. If there is a restriction / condition regarding the "out-of-date" behavior, it might be good to update the documentation. 2. Yes you are right, I got confused at some point :-\ It is fixed. But still, it is compiling twice during "make" and "make install" (it should not compile during the lates

Re: [CMake] add_custom_target: always built during "make" and "make install"

On Mon, Nov 02, 2009 at 10:48:49PM +0800, Romain CHANU wrote: > # Add a custom target to manage dependencies > add_custom_target(cxx_xml_mapping DEPENDS xml_mapping) > > add_custom_command( > OUTPUT cxx_xml_mapping > COMMAND ${XSD_EXECUTABLE} ARGS ${XSD_ARGS} > ${CMAKE_CURRENT_SOURCE_DIR}/*.xs

Re: [CMake] add_custom_target / add_definitions cache issues

On Thu, May 14, 2009 at 11:59:53AM +0200, Reto Glauser wrote: > add_definitions( -DVERSION="${PROJECT_VERSION}" ) > > Now, I'd like to rerun and redefine -DVERSION each time I commit a change > to the SCM or change the branch but fail to see how to achieve that. > > I tried to add a add_custom_t

Re: [CMake] add_custom_target and eclipse

On Monday 30 March 2009, Benoit wrote: > Hello, > > There is a little bug for the generation of eclipse MinGW project in cmake. > The thing is the custom targets are not added to the list of make target in > the .cproject. Which version of cmake ? This has been changed recently, so if you are not

Re: [CMake] Add_custom_target copying files

A Dilluns 16 Febrer 2009, Michael Jackson va escriure: > Not sure, it should work. > > Try changing POST_BUILD to PRE_BUILD and see what happens. > > also try printing the variable ${${inputPo}} > > message(STATUS "${inputPo}: ${${inputPo}}") > message(STATUS "inputPo: ${inputPo}") Well, first o

Re: [CMake] Add_custom_target copying files

Not sure, it should work. Try changing POST_BUILD to PRE_BUILD and see what happens. also try printing the variable ${${inputPo}} message(STATUS "${inputPo}: ${${inputPo}}") message(STATUS "inputPo: ${inputPo}") _ Mike Jackson

Re: [CMake] Add_custom_target copying files

A Diumenge 15 Febrer 2009, Michael Jackson va escriure: > Here is a code snippet from a project that I use that copies some > files to the build directory. Thanks, but my modified version doesn't work and I don't know what's happen macro (GETTEXT_UPDATE_LANG_PO dirOUTpo inputPo ) #mess

Re: [CMake] Add_custom_target copying files

Here is a code snippet from a project that I use that copies some files to the build directory. #-- Copy all the HDF5 files from the test directory into the build directory SET (HDF5_REFERENCE_TEST_FILES tnullspace.h5 family_v1.7_3.h5 family_v1.7_1.h5 mergemsg.h5 tbogus.h5

Re: [CMake] add_custom_target always runs?

2008/12/16 Tyler Roscoe : > I am using what I think is a common pattern to create some headers. > Following the example at > http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_then_use_the_executable_to_generate_a_file.3F, > I have an add_custom_command which calls a script (gen

Re: [CMake] add_custom_target always runs?

On Wed, Dec 17, 2008 at 08:45:01AM +0100, Martin Apel wrote: > I had a similar problem some time ago. I worked around it by first > generating the header files into ${CMAKE_CURRENT_BINARY_DIR} and then > execute 'cmake -E > copy_if_different' to their target location. This way dependent files > wil

Re: [CMake] add_custom_target always runs?

Tyler Roscoe wrote: > On Tue, Dec 16, 2008 at 09:44:38PM +0100, Eric NOULARD wrote: > >>> Ok, so is it simply impossible to do delta builds if my build process >>> needs add_custom_command/add_custom_target invocations? Is there some >>> better way to have CMake create the headers for me? Does t

Re: [CMake] add_custom_target always runs?

On Tue, Dec 16, 2008 at 09:44:38PM +0100, Eric NOULARD wrote: > > Ok, so is it simply impossible to do delta builds if my build process > > needs add_custom_command/add_custom_target invocations? Is there some > > better way to have CMake create the headers for me? Does this behavior > > of add_cus

Re: [CMake] add_custom_target always runs?

On Tue, Dec 16, 2008 at 10:09:41PM +0100, Alexander Neundorf wrote: > Did you try to use full pathes, i.e. use CMAKE_CURRENT_SOURCE_DIR and > CMAKE_CURRENT_BINARY_DIR respectively ? Yes, all paths in my cmake files are based on ${CMAKE_CURRENT_SOURCE_DIR}. tyler _

Re: [CMake] add_custom_target always runs?

On Tuesday 16 December 2008, Tyler Roscoe wrote: > I am using what I think is a common pattern to create some headers. > Following the example at > http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_then >_use_the_executable_to_generate_a_file.3F, I have an add_custom_command >

Re: [CMake] add_custom_target always runs?

Le Tue, 16 Dec 2008 12:26:26 -0800, Tyler Roscoe a écrit : > I am using what I think is a common pattern to create some headers. > Following the example at > http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_then_use_the_executable_to_generate_a_file.3F, > I have an add_custo

Re: [CMake] ADD_CUSTOM_TARGET behavior 2.4 vs 2.6?

Zitat von Roland Philippsen <[EMAIL PROTECTED]>: It is quite possible that the following problem arises because I misunderstant custom targets, but it worked under cmake-2.4 (various patch levels, various UNIX-ish operating systems). Attached is a mini-project which triggers an error due to the

Re: [CMake] ADD_CUSTOM_TARGET(target ALL) and Visual Studio

You're right. I tried a simple example and it did work. Now I have to find out why mine didn't. Thanks for your help. On Jan 24, 2008 3:23 PM, Sahn Lam <[EMAIL PROTECTED]> wrote: > > > On Jan 24, 2008 2:17 PM, Hendrik Sattler <[EMAIL PROTECTED]> wrote: > > > Am Donnerstag 24 Januar 2008 schrie

Re: [CMake] ADD_CUSTOM_TARGET(target ALL) and Visual Studio

On Jan 24, 2008 2:17 PM, Hendrik Sattler <[EMAIL PROTECTED]> wrote: > Am Donnerstag 24 Januar 2008 schrieb Sahn Lam: > > I don't trust myself to be able to specify the dependencies correctly - > now > > or in the future. It is not as simple as it seems. For example, let's > say > > I have this s

Re: [CMake] ADD_CUSTOM_TARGET(target ALL) and Visual Studio

On Jan 24, 2008 2:17 PM, Hendrik Sattler <[EMAIL PROTECTED]> wrote: > Am Donnerstag 24 Januar 2008 schrieb Sahn Lam: > > I don't trust myself to be able to specify the dependencies correctly - > now > > or in the future. It is not as simple as it seems. For example, let's > say > > I have this s

Re: [CMake] ADD_CUSTOM_TARGET(target ALL) and Visual Studio

Am Donnerstag 24 Januar 2008 schrieb Sahn Lam: > I don't trust myself to be able to specify the dependencies correctly - now > or in the future. It is not as simple as it seems. For example, let's say > I have this structure: > > libA has gen.h which is generated > libB has header1.h which includ

Re: [CMake] ADD_CUSTOM_TARGET(target ALL) and Visual Studio

I don't trust myself to be able to specify the dependencies correctly - now or in the future. It is not as simple as it seems. For example, let's say I have this structure: libA has gen.h which is generated libB has header1.h which includes libA/gen.h libC has header2.h which includes libB/heade

Re: [CMake] ADD_CUSTOM_TARGET(target ALL) and Visual Studio

Am Donnerstag 24 Januar 2008 schrieb Sahn Lam: > I have a top level custom target that depends on a header file generated by > a custom command. I want this custom target to be invoked first so the > generated header is built before any other targets needing the header are > built. > > Adding the

Re: [CMake] add_custom_target dependencies error

I resolved my problem using this command add_custom_target( deb ) add_custom_command( TARGET deb COMMAND ${CMAKE_MAKE_PROGRAM} subproject1_deb COMMAND ${CMAKE_MAKE_PROGRAM} subproject2_deb ) instead of using DEPENDS, but it looks ugly ^^ On 6/27/07, David Cole <[EMAIL PROTECTED]> wrote:

Re: [CMake] add_custom_target dependencies error

What is the error output now that you have removed the comma? On 6/27/07, Mehdi Rabah <[EMAIL PROTECTED]> wrote: Quoting Mehdi Rabah >: > > >* Hello,* > > > **>* I'm seeking for help for a weird error that is happening to me.* > >* I have a cmake pr

Re:[CMake] add_custom_target dependencies error

Quoting Mehdi Rabah http://www.cmake.org/mailman/listinfo/cmake> >: >* Hello,* > **>* I'm seeking for help for a weird error that is happening to me.* >* I have a cmake project, with a lot of target, two of them are named* >* subproject1_deb, and subproject2_deb* > **>* $ make help:* >* The foll

Re: [CMake] add_custom_target dependencies error

Quoting Mehdi Rabah <[EMAIL PROTECTED]>: Hello, I'm seeking for help for a weird error that is happening to me. I have a cmake project, with a lot of target, two of them are named subproject1_deb, and subproject2_deb $ make help: The following are some of the valid targets for this Makefile: .