[CMake] commands

Learning and understanding cmake would be a lot easier if the cmake-commands page would have two columns. On the left, the alphabetic listing, available now. On the right, commands grouped by category. Here’s a category: if

Re: [CMake] Running custom executable

Looking at the way these things work, it seems to me that the ideal solution to my situation, if it is possible, is to do a add_custom_command() for each source file, and then do a add_custom_target() that has all of the custom commands as PRE_BUILD events. Is there a way to pass the list of files

Re: [CMake] Running custom executable

On Tuesday, April 07, 2015 13:22:30 you 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 directo

Re: [CMake] Running custom executable

> > > > 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 definitions from the build system. >> > > >> > >

Re: [CMake] External Packages?

(Apologies for the self-reply) s/CMAKE_CURRENT_BUILD_DIR/CMAKE_CURRENT_BINARY_DIR/ On Tue, Apr 7, 2015 at 12:59 PM, Steven Stallion wrote: > All, > > I'm currently working on a fairly large project that requires a number of > external tools be installed. I've been playing with the idea of havin

[CMake] External Packages?

All, I'm currently working on a fairly large project that requires a number of external tools be installed. I've been playing with the idea of having CMake download and install these packages prior to building the project. I have something that works using a combination of custom modules and exter

Re: [CMake] Enable C++11 for a Target with Intel

Robert Maynard wrote: > Currently the only compilers that support compiler features are: > > Apple Clang versions 4.4 though 6.1. > GNU compiler versions 4.4 through 5.0 on UNIX and Apple. > Microsoft Visual Studio versions 2010 through 2015. > Oracle SolarisStudio version 12.4. > > If you are i

Re: [CMake] Running custom executable

On Tue, Apr 7, 2015 at 12:46 PM, Alexander Neundorf wrote: > On Monday, April 06, 2015 21:19:57 Klaim - Joël Lamotte wrote: > > On Mon, Apr 6, 2015 at 8:47 PM, Daniel Dilts wrote: > > > I have a custom executable that does some codegen to produce an > > > enumeration and a couple of tables. I n

Re: [CMake] Running custom executable

On Monday, April 06, 2015 21:19:57 Klaim - Joël Lamotte wrote: > On Mon, Apr 6, 2015 at 8:47 PM, Daniel Dilts 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 compila

Re: [CMake] Custom target not triggered to build

I actually have these in the original script ADD_CUSTOM_TARGET( generate_resources DEPENDS ${CMAKE_BINARY_DIR}/ resources.kw ) ADD_CUSTOM_TARGET( generate_application DEPENDS ${CMAKE_BINARY_DIR}/application.dat ) which gives me a target that builds in visual studio; and a target thaat can be

Re: [CMake] Custom target not triggered to build

Add custom command doesn't generate a target. You need to use add_custom_target to create an actual target. I believe what you are missing is a custom target that consume the output of the add custom command, than the install should work. A fully contained example that I could run would make solvi

Re: [CMake] CTest for multiple parallel jobs

On Tue, Apr 7, 2015 at 1:11 PM, Christon, Mark wrote: > Hi Robert, et al., > > Thanks for the information. I believe that ctest –j <#-of-cores> is > equivalent to specifying the processor count with ctest_test that you > pointed me to. > The PROCESSORS property states how many of #-of-cores

Re: [CMake] CTest for multiple parallel jobs

Hi Robert, et al., Thanks for the information. I believe that ctest –j <#-of-cores> is equivalent to specifying the processor count with ctest_test that you pointed me to. This does not correct the issue of distributing multiple jobs across multiple nodes on a cluster via ctest. Again, cons

Re: [CMake] Custom target not triggered to build

Am I incorrect in assuming that this should work? I added dependancies to them and that helped... until I leared I had the dependants wrong order, and it wouldn't let me depend the common on both of these... so when I reversed them, then neither built before install I recall a similar message