On Sat, 2019-10-12 at 19:25 -0700, Alan W. Irwin wrote:
> > Virtually all my properties are set on a per-target basis, so I assumed
> > they wouldn't be an issue here.
> >
> > Am I misunderstanding that?
>
> I think the current documentation is ambiguous about this. But
> certain target and dire
On Fri, 2019-10-11 at 10:17 -0400, Kyle Edwards wrote:
> On Fri, Oct 11, 2019 at 1:36 AM Alan W. Irwin
> <
> alan.w.irwin1...@gmail.com
> > wrote:
> > The source files that have COMPILE_OPTIONS, COMPILE_DEFINITIONS,
> > COMPILE_FLAGS, or INCLUDE_DIRECTORIES will also be skipped."
>
> This is by fa
On Thu, 2019-10-10 at 14:57 -0400, Robert Maynard via CMake wrote:
> * The "UNITY_BUILD" target property was added to tell generators to
> batch include source files for faster compilation times.
For some reason this didn't work with my actual cmake environment, but
I could enable it on a simple
On Thu, 2019-10-10 at 14:57 -0400, Robert Maynard via CMake wrote:
> * The "UNITY_BUILD" target property was added to tell generators to
> batch include source files for faster compilation times.
Are there any instructions on how to make this work? I tried this:
cmake -G 'Unix Makefiles' -DC
On Mon, 2019-06-17 at 11:43 +0200, Eric Noulard wrote:
> Yes you are right and I know that, but AFAIK when (with CMake) you
> TLL a shared lib to a static lib. You do not end up with any of the
> static lib symbol in the shared lib.
That can't be true, unless cmake is adding fancy linker options t
On Sun, 2019-06-16 at 21:42 +0200, Eric Noulard wrote:
> Le dim. 16 juin 2019 à 18:26, Paul Smith a
> écrit :
> > But, that's not the only way to use shared libraries. I'm trying
> > to collect a number of static libraries with different interfaces
> > into a
Let me just mention up-front that I spent about 2 weeks earlier this
year completely converting our circa-2011 cmake environment to ultra-
modern cmake: switching completely to TLL, interfaces, removing
virtually all if-statements and converting them into generator
expressions, etc. So I'm very fa
I have a situation where I create a number of static libraries, then I
create a shared library from them, then I create an executable from the
shared library.
This seems straightforward, but I can't get it do work as I want. The
behavior of STATIC -> SHARED for target property inheritance seems
i
On Sat, 2019-04-27 at 13:49 -0400, Paul Smith wrote:
> On Fri, 2019-04-26 at 17:26 -0400, Paul Smith wrote:
> > We're trying to implement precompiled headers (yes, I've seen all the
> > various github projects around this). As part of this we need to make
> >
On Fri, 2019-04-26 at 17:26 -0400, Paul Smith wrote:
> We're trying to implement precompiled headers (yes, I've seen all the
> various github projects around this). As part of this we need to make
> sure the precompiled header is rebuilt whenever any of the headers that
&g
We're trying to implement precompiled headers (yes, I've seen all the
various github projects around this). As part of this we need to make
sure the precompiled header is rebuilt whenever any of the headers that
it includes changes: this seems like exactly the job for
add_custom_command's IMPLICIT
On Thu, 2019-04-04 at 06:56 +0100, Stephan Menzel wrote:
> add_library(mylib STATIC mysources)
> add_excecutable(mytest mytest.cpp)
> target_link_libraries(mytest mylib)
>
> Now although I don't understand the exact reasons behind that, over
> the years came to accept that depedencies between the
On Thu, 2019-03-14 at 13:30 -0400, frodak17 wrote:
> On Thu, Mar 14, 2019 at 12:53 PM frodak17 wrote:
> > On Thu, Mar 14, 2019 at 1:13 AM Paul Smith
> > wrote:
> > > I have a situation where I've created a custom command to
> > > generate .cpp
> &g
I have a situation where I've created a custom command to generate .cpp
files to be compiled (in my case running bison/flex).
I'm using CMake 3.13.4
However, I have to compile this code in two different ways for two
different targets. I am seeing the Visual Studio generator re-running
bison/flex
On Wed, 2019-02-27 at 08:39 -0500, Robert Maynard wrote:
> CMake only provides an official way to get the location of the object
> files for OBJECT targets ( $ ). For other
> target types the location is an implementation detail.
Yes, but sometimes (as in my case) I need to know it :). I need to
Hi all. I'm using CMake 3.13.4 across Linux, MacOS, and Windows, with
various generators.
I need to write a script (this only runs on Linux actually) that will
do some processing on all the object files in a shared library and
generate a linker version file. I'm trying to write a custom command
think I'll submit this as an enhancement request and see what the
CMake devs think of it. It could be there are issues that I haven't
thought of.
On Sat, 2019-02-16 at 17:46 -0500, Paul Smith wrote:
> I wrote this function. At first attempt it seems to do what I want but
>
gt; I don't know if this doubled structure using pure interfaces libraries
> and the actual libraries is maintainable.
>
> Hope that helps a bit,
> Andreas
>
> Am 16.02.19 um 20:20 schrieb Paul Smith:
> > Hi all;
> >
> > I'm working on modernizing our l
Hi all;
I'm working on modernizing our large complex CMake environment. It
builds a number of different binaries from an even larger number of
static libraries, and these libraries depend on each other as well, in
that they need to include headers and, sometimes, -D options etc.
I've used straig
On Tue, 2019-02-12 at 16:19 -0800, Michael Ellery wrote:
> https://cmake.org/cmake/help/latest/release/3.12.html
> says that target_link_libraries got OBJECT in 3.12 - is that what
> you had in mind?
Aha! Of course, we're using the most recent 3.11 version. Isn't it
always the way it goes?
OK
Don't want to be a noodge but wondering if anyone has any thoughts
about this question or ideas on how to solve my problem?
On Sat, 2019-02-09 at 12:29 -0500, Paul Smith wrote:
> Hi all;
>
> I saw an email to the list from Chuck Atkins in the summer of 2017
> suggesting that
Hi all;
I saw an email to the list from Chuck Atkins in the summer of 2017
suggesting that OBJECT libraries were being enhanced and could become
fully-functional libraries hopefully sometime that year. I'm wondering
if that ever actally happened and if so what release of cmake it was
in, and if n
On Tue, 2018-12-18 at 08:22 +1100, Craig Scott wrote:
> If you are setting your own sysroot, are you using a toolchain file?
> You could put your set_property() command in your toolchain file if
> you're using one.
> Those techniques aside, it's interesting that you need to add this
> manual workar
Hi all.
I'm using cmake with a cross-compiler environment, but building third
party packages that are configured with CMake. So when I invoke cmake
for those packages I add this options to the command line:
-DCMAKE_FIND_ROOT_PATH=/my/sysroot
However, this is not working because it's finding 3
On Mon, 2018-01-01 at 18:12 -0500, Paul Smith wrote:
> What I hoped is for the default build with no targets specified to
> build everything ("all"), but if I invoke the build with the
> "install" target it builds only the things that are to be installed,
> not my t
On Thu, 2018-06-14 at 11:41 +0200, Deniz Bahadir wrote:
> > But all the other bintools variable overrides do the wrong thing:
> >
> >* -DCMAKE_AR=my-ar --> CMAKE_AR=/tmp/obj/my-ar
> >* -DCMAKE_LINKER=my-ld --> CMAKE_LINKER=/tmp/obj/my-ld
> >* -DCMAKE_RANLIB=my-ranlib
I've discovered that CMake is not correctly locating ar/strip/etc. if I
override the names of these tools on the command line. I've tried this
with 3.5.2 as well and I get the same incorrect behavior.
Here's an example (this is on a GNU/Linux system):
$ type -a my-ar
/work/bin/my-ar
$ my-ar --v
On Sun, 2018-01-14 at 01:08 +0100, Jean-Michaël Celerier wrote:
> https://cmake.org/cmake/help/latest/module/ExternalProject.html
>
> since CMake can download stuff, it needs to support https, hence SSL,
> hence OpenSSL
OK, thanks.
Does anyone know if there is way to convince CMake to use a dece
Hi all.
I build CMake myself. I've noticed that on GNU/Linux by default cmake
will be linked with openssl and require these shared libraries to be
available at runtime.
Why does cmake link with these libraries? I can't think of a reason it
might need them. What do I lose in functionality if I
I have (what I thought was) a common environment where my build creates
both programs to be installed and also test programs etc. that aren't
installed.
What I hoped is for the default build with no targets specified to
build everything ("all"), but if I invoke the build with the "install"
target
On Wednesday, November 8, 2017, Shoaib Meenai wrote:
> Running cmake from an x64 developer command prompt and passing
> -Thost=x64 to cmake should do the trick.
Thanks for the response!
I'm not sure what you mean by "an x64 developer command": my builds are
invoked in an automated way from a CI
Hi all. I wonder if someone can help me get CMake to force Visual
Studio to run the 64bit linker instead of the 32bit linker. By that I
mean, the link.exe binary built for 64bit, not a linker that produces a
64bit executable.
Sometimes (but not always) when I link my code I get an error from the
Hi all.
I'm trying to build LLVM/Clang locally on my Linux system, but I'm using
a separate set of system headers and libraries. These appear in a
separate sysroot directory, like this:
/sysroot/tools/usr/lib64/...
/sysroot/tools/usr/lib/...
/sysroot/tools/usr/include/...
This is basicall
On Fri, 2017-01-27 at 15:45 -0400, Dave Flogeras wrote:
> I've recently upgraded to CMake 3.7.2 (and gnu make-4.2.1). Now, when
> I execute 'make -j5 NightlyBuild', I get the following new (to me)
> warning:
>
> "gmake[4]: warning: jobserver unavailable: using -j1. Add '+' to parent make
> rule.
On Tue, 2017-01-17 at 13:20 -0500, Paul Smith wrote:
> I wonder whether _fini and _init need to be exported in order to
> properly handle global ctor/dtor when the library is loaded/unloaded?
> Hm. I may need to do some experimentation here.
FWIW I tried some experimentation with bot
On Mon, 2017-01-16 at 09:07 -0700, clin...@elemtech.com wrote:
> > Yes, thanks for that info. My situation is that I need to force ALL
> > symbols to be private, even those from external static shared libraries
> > that I'm linking in (whose symbols have global visibility by default).
>
> Have
On Sun, 2017-01-15 at 12:08 +1100, Craig Scott wrote:
> While not directly answering your question, it seems you may be trying
> to deal with symbol visibility. Are you aware of CMake's symbol
> visibility features? A good place to start would be the
> GenerateExportHeader module, the documentation
I'm really stuck: maybe someone can provide a hint.
I'm trying to create a shared library from a bunch of object files, and
use a linker script to mark almost all the symbols as local. The tricky
thing is I'm auto-generating the linker script via a shell script that
examines the object files for
If I create an OBJECT library:
add_library(libIface OBJECT iface.cpp)
Then I create a custom command that depends on this:
add_custom_command(OUTPUT out.map
COMMAND touch out.map
DEPENDS libIface
VERBATIM)
It doesn't work: the dependency is missing so when I edit the iface
I have a CMake-based build that creates about 170 binaries (most of them
are individual unit test programs).
I have set the CMAKE_EXE_LINKER_FLAGS to a set of flags I wanted on all
the binaries.
Now it turns out that I need to remove, or not set, one specific flag on
a small number (like 5) of th
On Fri, 2016-05-20 at 14:34 -0400, Paul Smith wrote:
> Just discovered a bug in the Xcode generator; this works fine with
> Makefile generator (on OSX or Linux) and Visual Studio, but fails on
> Xcode:
Meh. Looks like this is documented in add_library():
> Some native build systems
Just discovered a bug in the Xcode generator; this works fine with
Makefile generator (on OSX or Linux) and Visual Studio, but fails on
Xcode:
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 3.5)
project(BadXcode)
add_library(obj OBJECT foo.cpp)
add_library(shared SHARED $)
$ touc
On Fri, 2016-05-20 at 11:58 -0400, Paul Smith wrote:
> This is not nice but it does work...
Gah! The last of my problems can be solved with add_dependencies().
Somehow I didn't see this and was looking through all the target
properties with set_properties() to find a way to add a de
I'm using CMake 3.5.2 generating for Linux / OSX / Visual Studio.
I'm creating a shared library. This shared library is constructed
mostly from other libraries (which are also built in other directories
by this cmake setup).
I have been doing this for a long time and it worked fine:
add_libra
On Wed, 2016-05-11 at 09:06 -0500, Steve Lorimer wrote:
> I am aware of being able to do in-source builds, but would like to
> continue to reap the benefits of out-of-source builds whilst being
> able to build from in-source
Make a shell function or shell script to run your build, that does the
cd
If my compiler changes between the last invocation of cmake and this
one, then cmake will restart itself; this part works fine. The problem
is that if I've invoked cmake with some command line overrides, they are
lost when I restart. For example if I have in my makefile:
set(BUILDNUM "0" CACHE
On Mon, 2015-12-14 at 09:34 +0300, Igor Sobinov wrote:
> So, If I write in makefile
>
>
> build_release: $(RELEASE_DIR)
> @cd $(RELEASE_DIR); $(MAKE) release
>
> I got an error
>
> Also if I write
> build_release: $(RELEASE_DIR)
> $(MAKE) release -C $(RELEASE_DIR)
>
> I got an error t
Is this a known thing, or a bug (I'm using cmake 3.1.0):
I create this CMakeLists.txt:
cmake_minimum_required(VERSION 3.1.0)
project(ArgTest)
function(FOO one two)
message(STATUS "extra args are ${ARGN}")
message(STATUS "third arg is ${ARGV2}")
endfunction()
function(BAR one)
We have a situation where people are sometimes wanting to switch between
different generators: from Xcode to Unix Makefiles, or from Visual
Studio 2010 to Visual Studio 2012, etc.
If they have an already-configured workspace then run "cmake -G" with a
different generator, it appears to be a no-op:
On Mon, 2015-06-29 at 13:08 +0200, SF Markus Elfring wrote:
> > unfortunately i dont quite understand what you mean with "your
> tool".
>
> How many efforts would you like to invest so that limitations
> around software like a fortran preprocessor can be circumvented?
>
> http://www.cmake.org/Wik
On Mon, 2015-05-18 at 12:32 +0200, Ruslan Baratov via CMake wrote:
> This table tells you what attribute you need to set to disable/enable
> specific warning.
I see, so these are CMake attributes? That wasn't clear to me. I
thought they were attributes of Xcode.
I guess my basic question is, wh
On Sun, 2015-05-17 at 14:43 +0200, Ruslan Baratov via CMake wrote:
> As far as I know extra flags set by Xcode itself. You can use
> XCODE_ATTRIBUTE_* target properties to enable/disable warnings. This
> table can be helpful:
> https://github.com/ruslo/leathers/wiki/List#xcodeclang-table
Thanks
I was comparing the command line used when we choose an Xcode generator
on our OSX systems, vs. the command line used when we choose a Makefile
generator. We certainly have nothing in our CMakeLists.txt which sets
compiler flags based on the type of generator, only based on the type of
compiler (G
Has anyone else run into errors rebuilding objects using the Xcode
generator? I imagine it would be a bug in xcodebuild, not cmake. We've
been using incremental builds, rather than clean builds, for years with
cmake on GNU/Linux (make), OSX (Xcode), and Windows (MSVC) and this is
the first time I
On Mon, 2015-02-16 at 09:55 -0500, David Cole wrote:
> Ah ha! Back to the simpler approach with install(CODE!
>
> Good idea, Nils.
>
> Then you just need a stamp/sentinel file associated with running the
> operation, and you can check it against your input.
Aha, that works well. I don't nee
ot during the normal build
(because it's slow), but only if the binary that was installed has
changed.
copy_if_different won't help here.
> On Sun, Feb 15, 2015 at 1:59 PM, Paul Smith wrote:
> > install(CODE "message(STATUS \"Creating dSYM for ${target} in ${dir}\&q
On Sun, 2015-02-15 at 12:16 -0500, David Cole wrote:
> The easiest thing is probably to use the install(SCRIPT or
> install(CODE signature of the install command rather than having a
> "build time" custom command.
Hm. That has the disadvantage that it runs every time, even if the
binary hasn't be
In my Mac OSX builds I want to run dsymutil to create .dSYM debug
contents. However, this is very slow so I don't want to do it during
normal builds (where it's not needed because I have all the object
files), I only want it to be done during the install step.
I can create an add_custom_command()
lent flag to CMAKE_EXE_LINKER_FLAGS that always applies only to
compile lines, in all generators? Do we just have to continue to
bastardize add_definitions() for this, maybe?
On Thu, 2015-01-08 at 18:52 -0500, Paul Smith wrote:
> If I'm on OSX, then when I set CMAKE_CXX_FLAGS and do
On Wed, 2015-01-21 at 11:12 -0500, Brad King wrote:
> Rather than requiring users to run
>
> cmake --build . -- $tool_specific_parallel_option
>
> to get a parallel build we could instead extend the "cmake --build"
> command to support an option mapping to the right parallel option
> underneath:
On Tue, 2015-01-20 at 16:02 -0500, Paul Smith wrote:
> > I think devenv is used instead of msbuild when the solution has
> > fortran projects.
>
> I certainly don't have any Fortran projects--!!
I think I figured it out: on our build servers we don't delete
ev
On Tue, 2015-01-20 at 21:57 +0100, Nils Gladitz wrote:
> On 20.01.2015 21:40, Paul Smith wrote:
> >> Where can I go to find out more about how cmake --build chooses whether
> >> to use msbuild vs. devenv? It has to be something more complicated than
> >> just the ge
> Am 20. Januar 2015 14:54:26 MEZ, schrieb David Cole via CMake
> :
> >If you open the "Tools > Options" dialog in Visual Studio, and
> >navigate to the "Projects and Solutions > Build and Run" tab, what is
> >your "maximum number of parallel project builds" value?
> >
> >For maximum parallel build
It seems different generators are handling this differently, which is
frustrating (I've tried with both CMake 3.1.0 and 2.8.12.2)... or else
there's something very bizarre about my cmake files.
The new doc layout looks nice, but it really needs an infusion of
detail. Here's the doc for CMAKE_CXX_
Hi all. I'm testing an upgrade to CMake 3.1.0 (from 2.8.12.2) and
seeing a weird warning, but ONLY on Windows; it works fine on GNU/Linux
and OSX:
-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10 2010 Win64
-- Check for working C
On Mon, 2014-12-29 at 02:03 +, Fraser Hutchison wrote:
> I'd have thought the following replacement would work the same:
>
> function(stageobj target dir)
> add_custom_target(stage_${target} ALL
> COMMAND "${CMAKE_COMMAND}" -E make_directory "${DESTDIR}/${dir}"
> CO
On Tue, 2014-12-23 at 21:32 +, Parag Chandra wrote:
> Have you tried the CMake variables LIBRARY_OUTPUT_PATH and
> EXECUTABLE_OUTPUT_PATH? I¹ve been using them to accomplish much the
> same thing.
Well, I don't want ALL my executables and libraries to go into these
locations. Only specific on
On Tue, 2014-12-23 at 16:59 -0500, David Cole wrote:
> Are you sure there's a problem using TARGET_FILE in your original
> context?
> You should be able to use that in a custom command in your custom
> stage_tgt target...
>
> You have to give the name of the target for the TARGET_FILE generator
>
Hi all. I need a pointer or two.
In my environment I need to have my executables and binaries copied to
another location; this has to happen as part of the default "all"
target: it can't be required to run "install" for example (we use the
"install" rule for a "real" install step, for one thing).
On Wed, 2013-05-01 at 10:18 -0400, Paul Smith wrote:
> I'm wondering if there's any way to force the output from cmake (using a
> unix makefile generator for example) to be colorized, even if stdout
> doesn't appear to be a TTY.
>
> Is that possible? Some extra
On Wed, 2014-08-13 at 21:40 +0200, Nagger wrote:
> Does anyone already came up with a good solution? Isn't this a common
> problem?
I'm not sure about the other generators, but the makefile generator has
this built-in; that is, if the makefiles detect that a cmake file has
changed it will re-run
I've built CMake 3.0.0-rc1 and tested it, and I still see this same bug
with that version of CMake.
Anyone have any ideas? Not having reliable builds is wreaking total
havoc on the Xcode users on our development team.
On Wed, 2014-02-19 at 15:17 -0500, Paul Smith wrote:
> Hi all. I
Hi all. I'm using CMake 2.8.12.1 on Linux, MacOSX, and Windows.
On my system I need to build libraries in a large number of
subdirectories and link them (statically) with various executables
(different executables use different libraries). Then I also need to
take the content of all those librar
On Mon, 2014-02-17 at 08:34 -0500, Paul Smith wrote:
> On Mon, 2014-02-17 at 10:20 +0100, Hendrk Sattler wrote:
> > Visual Studio 10 totally relies on the custom build tool to protect
> > itself when run in parallel. It will run the generator as many times
> > as the ba
On Mon, 2014-02-17 at 10:20 +0100, Hendrk Sattler wrote:
> Visual Studio 10 totally relies on the custom build tool to protect
> itself when run in parallel. It will run the generator as many times
> as the bar.cpp is mentioned in different targets, even in parallel if
> that is enabled.
Yes, th
Thanks Hendrk. It's good to know I'm not crazy or overlooking something
simple, even if the answer is not what I wanted.
I did some other experimentation last night and I'll followup with some
results, which may be interesting.
Can anyone tell me how to get the Visual Studio output to show compl
On Mon, 2014-02-17 at 00:20 -0500, Paul Smith wrote:
> On Sun, 2014-02-16 at 22:38 -0500, David Cole wrote:
> > > How can I structure my cmake file to avoid
> > > this double build?
> >
> > Put the custom command in a custom target, and make the libraries using
On Sun, 2014-02-16 at 22:38 -0500, David Cole wrote:
> > How can I structure my cmake file to avoid
> > this double build?
>
>
> Put the custom command in a custom target, and make the libraries using
> the generated file depend on the custom target.
>
> That works, even for parallel builds.
>
On Sun, 2014-02-16 at 21:35 -0500, Paul Smith wrote:
> I'm using CMake 2.8.12.1 on Linux, MacOS, and Windows. On Windows I'm
> using MSVC 2010 and the Visual Studio generator, but I have only
> remote access so I'm invoking my builds using devenv (not running
>
I'm using CMake 2.8.12.1 on Linux, MacOS, and Windows. On Windows I'm
using MSVC 2010 and the Visual Studio generator, but I have only remote
access so I'm invoking my builds using devenv (not running Visual
Studio).
I'm deeply involved in some messy hackery related to building the same
code as a
On Fri, 2014-01-31 at 14:24 +0100, Eric Noulard wrote:
> > We didn't try to integrate it with the build system. We just checked in
> > the configuration file and a script people could use if they wanted to
> > re-beautify their code.
>
> Would you mind sharing the script you used with us?
Sure,
On Fri, 2014-01-31 at 02:26 -0800, Alan W. Irwin wrote:
> And to answer the OP's question, I can highly recommend uncrustify for
> code styling
I agree with Alan. We did a huge reformatting effort last year to
change a very large C++ codebase from a style based loosely on
Whitesmith to a more com
On Thu, 2014-01-23 at 11:40 -0500, Brad King wrote:
> On 01/23/2014 11:36 AM, Paul Smith wrote:
> > I see. That's a shame :-(.
>
> Unfortunately it is an Xcode limitation that CMake cannot work around.
>
> > Kind of unpleasant. Anyone have any ideas?
>
> A
On Thu, 2014-01-23 at 10:22 -0500, Brad King wrote:
> On Thu, Jan 23, 2014 at 8:03 AM, Paul Smith wrote:
> > add_library(mylib STATIC $)
> [snip]
> > The Makefile generators work fine
> >
> > For Xcode, though, the link fails:
>
> This is a known limitation.
Hi all. I'm using CMake 2.8.12.1 on Linux, MacOS, and Windows. I've
discovered a bug in the Xcode generator when dealing with OBJECT and
STATIC libraries. This example works fine on Linux, and on MacOS with
the Makefile generator. I also haven't noticed a problem on Windows
(MSVC).
What I'm do
On Sun, 2013-11-17 at 18:19 -0500, Paul Smith wrote:
> On Mon, 2013-11-18 at 00:18 +0200, Raphael Kubo da Costa wrote:
> > I'm not sure if this is what Roy originally had in mind; it would be
> > good if you could file a bug in CMake's bug tracker for this in any
> >
On Mon, 2013-11-18 at 00:18 +0200, Raphael Kubo da Costa wrote:
> I'm not sure if this is what Roy originally had in mind; it would be
> good if you could file a bug in CMake's bug tracker for this in any
> case.
I'm sure this isn't what Roy was talking about, I just happened to think
of it when I
On Sun, 2013-11-17 at 20:03 +0200, Raphael Kubo da Costa wrote:
> Roy Crihfield writes:
>
> > I have a patch the the CMake emacs mode I'd like to have reviewed and
> > push. What is the preferred way to do this - should I just send the
> > patch, or fork and push to the repository?
>
> Both send
On Thu, 2013-11-14 at 12:41 +0100, Micha Hergarden wrote:
> For the modules you can use cmake_module_path from within your
> scripts.
Unfortunately this doesn't work. I should have mentioned that I'd
already tried this. CMake looks for its installation directory as the
very first thing and error
I need to maintain my own copy of the latest cmake, and for multiple
different target systems (GNU/Linux, MacOS, Windows, Solaris...)
I have a shared location where all tools like this go, so that
regardless of the system architecture you can access this one location.
Obviously inside that locatio
I need to be able to run a command after a target is created, every time
the target is created. I need this to happen regardless of the command
line.
For example, for Makefile generators if someone runs "make myTarget"
directly (if myTarget is a program for example) I still need this
command to b
On Tue, 2013-08-13 at 00:24 +0200, Eric Noulard wrote:
> > OK, maybe I'm misunderstanding but if the SerializeTarget is considered
> > "always out of date" because it was defined with add_custom_target()
> > then won't that cause the two libraries to always rebuild, since
> > something they depend
On Mon, 2013-08-12 at 22:35 +0200, Eric Noulard wrote:
> 2013/8/12 Paul Smith :
> >
> > So I have tried using add_custom_command() with OUTPUT, but the
> > documentation says:
> >
> > "Do not list the output in more than one independent target that may build
&
Hi all.
I've got a situation where I'm creating generated source files (from
bison/flex, actually, but I'm writing my own rules for it since I need
specialized support for C++ output, etc.)
However I need to compile the generated output into two different
libraries, building two different ways (w
On Sun, 2013-07-14 at 19:35 +, David Cole wrote:
> > DEPENDS ${targetname}
>
> Instead of using a targetname here in the add_custom_command call, use
> a file name. That’s known to work with the Xcode generator. (I
> think... it’s been a while since I did it personally using Xcode, but
>
On Thu, 2013-05-30 at 08:10 +0200, Petr Kmoch wrote:
> Look up "generator expressions" in the CMake docs (for example in
> "add_custom_command"), particularly $. It might help in
> solving your issue.
Perfect! Thanks.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
E_BUILD_TYPE= flag :-/.
On Fri, 2013-05-24 at 11:41 -0400, Paul Smith wrote:
> Hi all;
>
> We have a large-ish set of cmake files building our project which
> results in various executables, libraries, scripts, etc. Currently
> these are just left lying where they were created, a
This is probably not related, but your comment about deleting the cmake
cache made me think of it: one thing to be sure of is that if you delete
CMakeCache.txt you ALSO delete the CMakeFiles/ directory.
Deleting CMakeCache.txt but not CMakeFiles yields corrupted results
after you run "cmake" the n
Hi all;
We have a large-ish set of cmake files building our project which
results in various executables, libraries, scripts, etc. Currently
these are just left lying where they were created, and all our tests
etc. expect to find them there.
Then we then have a subsequent script that we run to c
On Tue, 2013-05-14 at 09:51 -0400, Brad King wrote:
> On 05/10/2013 11:14 AM, Brad King wrote:
> > OTOH the Xcode generator just initializes all four configurations
> > in EnableLanguage up front:
> >
> >
> > http://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/cmGlobalXCodeGenerator.cxx;hb=v2.8.
1 - 100 of 118 matches
Mail list logo
