ExternalProject does its work at build time, so too late for find_package which
is executed at config time.
Have a look at module FetchContent which does its work before config time.
Le 19 nov. 2019 à 16:13 +0100, hex , a écrit :
> I have an external CMake project that gets exported on install. Th
I have an external CMake project that gets exported on install. The root
project uses it as a package. The external project must be installed
prior being used as a package.
I can solve this problem by using `ExternalProject` for both projects
and declare their dependency. My setup is different
On 17/12/2018 15:37, David Blaikie wrote:
On Sun, Dec 16, 2018, 4:24 PM Kris Thielemans
mailto:kris.f.thielem...@gmail.com> wrote:
I’ve just had a problem caused by an upgrade of my system files (in
this particular case: boost). Rebuilding our software didn’t
correctly rebuild those
Thanks David
It seems that a rebuild is the only way. We’ll add that to our instructions
then!
Kris
From: David Blaikie
Sent: 17 December 2018 15:37
To: Kris Thielemans
Cc: CMake Mail List
Subject: Re: [CMake] dependencies on system include files
If you're willing to
If you're willing to run a different command or flag when rebuilding after
upgrading system libraries, I would guess the thing to do would be to do a
clean and rebuild, perhaps?
On Sun, Dec 16, 2018, 4:24 PM Kris Thielemans Hi all
>
>
>
> I’ve just had a problem caused by an upgrade of my system
Hi Kris,
On 17.12.18 01:24, Kris Thielemans wrote:
> Checking a bit more carefully it appears that the system .h files are
> not included in depend.make. I guess this is done to save some time
> checking all those dependencies as system files are supposed to be
> relatively stable, but if they’re
Hi all
I've just had a problem caused by an upgrade of my system files (in this
particular case: boost). Rebuilding our software didn't correctly rebuild
those files that depend on the updated boost files. (I'm using CMake 3.9
with make on Ubuntu 16.04)
Checking a bit more carefully it appe
On Mon, Dec 10, 2018 at 7:57 PM Eric Noulard wrote:
>
> Le dim. 9 déc. 2018 à 12:24, Craig Scott a
> écrit :
>
>> On Tue, Dec 4, 2018 at 6:56 PM Torsten Robitzki
>> wrote:
>>
>>> > Am 27.11.2018 um 19:55 schrieb Eric Noulard :
>>> >
>>> > My assumption are:
>>> > a) when you cross-compile your
Le dim. 9 déc. 2018 à 12:24, Craig Scott a écrit :
> On Tue, Dec 4, 2018 at 6:56 PM Torsten Robitzki
> wrote:
>
>> > Am 27.11.2018 um 19:55 schrieb Eric Noulard :
>> >
>> > My assumption are:
>> > a) when you cross-compile your build is a "whole" and you shouldn't
>> have to setup some superbui
On Tue, Dec 4, 2018 at 6:56 PM Torsten Robitzki wrote:
> > Am 27.11.2018 um 19:55 schrieb Eric Noulard :
> >
> > However from my point of view and my cross-compiling experience when you
> cross-compile you have:
> >
> > 1) the host compiler which is used to compile "host tools"
> > 2) the target
> Am 27.11.2018 um 19:55 schrieb Eric Noulard :
>
> However from my point of view and my cross-compiling experience when you
> cross-compile you have:
>
> 1) the host compiler which is used to compile "host tools"
> 2) the target compiler (may be several of them) to "cross-compile"
>
> My assum
Le mar. 27 nov. 2018 à 11:28, Rolf Eike Beer a écrit :
> Am 2018-11-09 10:04, schrieb Torsten Robitzki:
> > Hi,
> > I hope this question was not asked before. I work in the embedded
> > field and there it is usually to have at least two different build
> > platforms. The Host platform, where unit
Since I'm not doing the work I don't get to tell you how to
do it.
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Rolf Eike Beer
Sent: Tuesday, November 27, 2018 4:28 AM
To: cmake@cmake.org
Cc: cmake-develop...@cmake.org
Subject: Re: [CMake] d
> which I bet all of us would love to see.
This is not correct. I would strongly prefer they continue with QBS
instead. Cmake is defacto, but very suboptional.
On Tue, Nov 27, 2018, 10:28 AM Rolf Eike Beer Am 2018-11-09 10:04, schrieb Torsten Robitzki:
> > Hi,
> > I hope this question was not as
Am 2018-11-09 10:04, schrieb Torsten Robitzki:
Hi,
I hope this question was not asked before. I work in the embedded
field and there it is usually to have at least two different build
platforms. The Host platform, where unit tests are build (and where
CMake is running) and an embedded Target plat
> Am 09.11.2018 um 15:55 schrieb Miller Henry :
>
> There are two options. Each with pros and cons.
>
> The first what you are doing now, except you use external project
> https://cmake.org/cmake/help/v3.12/module/ExternalProject.html to build the
> host tools instead of add_custom_command. I
g.
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Torsten Robitzki
Sent: Friday, November 9, 2018 3:04 AM
To: cmake@cmake.org
Subject: [CMake] dependencies of cross compiliations
Hi,
I hope this question was not asked before. I work in the embedded field and
t
Hi,
I hope this question was not asked before. I work in the embedded field and
there it is usually to have at least two different build platforms. The Host
platform, where unit tests are build (and where CMake is running) and an
embedded Target platform, where targets are build with a cross com
On Sat, Oct 6, 2018 at 10:58 AM Stephan Menzel
wrote:
>
> protobuf_generate(TARGET my_protobuf_lib)
>
>
Well, it seems like this was the culprit all along. There is a bug in
protobuf's usage of the add_custom_command. Appears this is known and fixed
by:
https://github.com/protocolbuffers/protobuf
Hello all,
I am a long term user of CMake, protobuf and grpc on Windows (MSVC15) and
Linux.
Roughly in the beginning of this year I started to notice that dependencies
of targets using generated sources to their appropriate protobuf files
didn't work anymore. Basically, when I change a grpc source
On Thu, Jun 28, 2018 at 4:07 PM Stephan Menzel
wrote:
> I am observing a strange problem regarding dependencies to static libs in
> executables. I am not entirely sure but it seems this started since I
> upgraded to the 3.11 line. I am using Windows and MSVC14.
>
> Basically, my code base contain
Are you sure you hit the right build menu item? Maybe you are just building the
current target. At least that would explain it. In MSVC you must either build
the solution or the ALL_BUILD target for this to work.
Am 28. Juni 2018 16:07:33 MESZ schrieb Stephan Menzel
:
>Hello CMake community,
>
Hello Innokentiy,
On Thu, Jun 28, 2018 at 4:17 PM, Innokentiy Alaytsev
wrote:
> Hello!
>
> I hope you will forgive me a silly question: did you consider checking last
> change date of the executable? And is there any way you can ensure that the
> changes to the library a present in the executabl
Hello!
I hope you will forgive me a silly question: did you consider checking last
change date of the executable? And is there any way you can ensure that the
changes to the library a present in the executable?
Best regards,
Innokentiy Alaytsev
--
Sent from: http://cmake.3232098.n2.nabble.com/
Hello CMake community,
I am observing a strange problem regarding dependencies to static libs in
executables. I am not entirely sure but it seems this started since I
upgraded to the 3.11 line. I am using Windows and MSVC14.
Basically, my code base contains a number of static libraries that are
l
Hi,
I ran into a CMake problem and I found a very informative answer at
https://cmake.org/pipermail/cmake/2011-April/043758.html. Still, 7 years has
passed. Is any easier solution for dependency scanning for an proprietary
language?
BR,
SoMux
--
Powered by www.kitware.com
Please keep messag
Usually there would be variables like A_ROOT which allow the
FindA.cmake module being used by B to correctly find everything. If
there isn't, you'd have to write your own FindA.cmake module in either
case. If you can't modify B, you could use the patch step of the
external project to replace the br
I'm struggling with how to handle dependencies between external projects in
a
superbuild. The issue is different than simply ensuring that one gets
built before
another using the DEPENDS keyword -- that's trivial.
Suppose I have two external libraries A and B, where B depends on A. It is
not
alw
On Thu, Sep 11, 2014 at 9:51 AM, Vojtech Mašek wrote:
> Hi, I am working at team developing RPM pacage generator.
> Now I am solving a problem how can i get dependencies using cmake.
> Basically we need to get paths to libs like they are cached in
> CmakeCache.txt, is it somehow possible before c
Hi, I am working at team developing RPM pacage generator.
Now I am solving a problem how can i get dependencies using cmake.
Basically we need to get paths to libs like they are cached in
CmakeCache.txt, is it somehow possible before calling cmake and then
parsing the file ?
--
Powered by www.kit
Jörg Kreuzberger wrote:
Hi!
i had a problem between depencendies of static libraris. Due to the
used tools (qt, moc, uic) a library depends on another library,
especially on header files generated by uic.
This is a litte bit a broken design, but cannot fix it currently.
On massive parallel bui
Hi!
i had a problem between depencendies of static libraris. Due to the used tools
(qt, moc, uic) a library depends on another library, especially on header files
generated by uic.
This is a litte bit a broken design, but cannot fix it currently.
On massive parallel builds ( 8 cores on ssd ) i
: [CMake] Dependencies
Quoting the documentation of OBJECT_DEPENDS:
Specifies a semicolon-separated list of full-paths to files on which any
object files compiled from this source file depend.
Notice the "full-paths" bit. You're not providing a full path. You must make
the pat
t, and another
> CMake. Nothing gets built. VSHVOLT.asm should get reassembled.
>
>
>
> This is driving me crazy...
>
>
>
> *From:* Petr Kmoch [mailto:petr.km...@gmail.com]
> *Sent:* Wednesday, February 05, 2014 12:08 AM
>
> *To:* Phil Smith
> *Cc:* cmake@c
doing the set_property as expected
(i.e., that code didn't somehow get bypassed).
From: Petr Kmoch [mailto:petr.km...@gmail.com]
Sent: Wednesday, February 05, 2014 3:08 AM
To: Phil Smith
Cc: cmake@cmake.org
Subject: Re: [CMake] Dependencies
Hi Phil.
If your FOO.asm is used as a sourc
I might also add that the set_property() approach has an additional
advantage over the set_source_files_properties(): The APPEND and
APPEND_STRING options allow you to add properties like dependencies without
overwriting the values which already exist.
> Hi Phil.
>
>
>> If your FOO.asm is used as
Hi Phil.
If your FOO.asm is used as a source file (i.e. it's listed in an
add_executable() or add_library() command), then you can use the source
file property OBJECT_DEPENDS for that:
add_executable(myexe FOO.asm other.file one.more)
set_property(SOURCE FOO.asm PROPERTY OBJECT_DEPENDS BAR.m
This is surely something basic, but I'm far from a CMake guru and would rather
not spend weeks digging to solve something that *seems* like it'll be simple.
We have assembler modules in a project. These use macros, as assembler modules
are wont to do.
So if module FOO.asm uses macro BAR.mac, an
Hi Olaf.
You're missing a DEPENDS argument in your custom command to make
${foo_STATIC_LEXER_HPP} depend on ${foo_LEXER_HPP}. (Or, in your case,
MAIN_DEPENDENCY would probably be more appropriate).
Next, the custom target driving the lexer generation should depend on
its output, not its input - i
Hello,
obviously I have a problem with the understanding of generating
dependencies of generated files.
generate_foo_static_lexer is using ${foo_LEXER_HPP} to generate a header
file ${foo_STATIC_LEXER_HPP}. Each time ${foo_STATIC_LEXER_HPP} is
changed the header shall be regenerated. Later,
Hi,
Apologies for not replying properly to this thread. I just joined the list.
By coincidence I just wrote up a blog post on this topic, which I just wanted
to share with you. We've faced the same problem and came up with a solution for
our projects:
http://pogl.wordpress.com/2012/06/01/build
Hi André,
2012/5/2 André Caron
>
> I've come up with a simple workflow where each library project exports a
> "library-config.cmake" file and any project that includes it defines the
> "library_DIR" variable to the folder containing this "library-config.cmake"
> file so that it can be resolved fr
I've run into this issue before and posted a question about this on
Programmers.StackExchange[1]. While the exact workflow I present is for
Git & CMake, the question is really similar. The idea is to have a certain
library B that depends on library A, as well as a program C that depends on
B and
Hi,
I'm very interested in this solution and the results if it is finished.
Could you keep me up to date if you have something working?
Thx!
2012/4/30 Arnault Christian
> Hi
>
> We have been using a configuration system named CMT which exactly cope
> with this issue
> It used to be directly b
Hi Peter,
Thanks for your reply,
2012/4/30 Petr Kmoch
> Hi Alexander,
>
> I had to create a very similar setup at work. My solution was to
> define a global property for the list of projects to generate. There
> is a top level CMakeLists.txt file which doesn't define any targets,
> but just inc
Hi
We have been using a configuration system named CMT which exactly cope
with this issue
It used to be directly based on pure Make files for the build aspect.
Nowadays, we are converting the build part to using CMake, while
preserving te general configuration properties.
In fact, we do mana
Hi Alexander,
I had to create a very similar setup at work. My solution was to
define a global property for the list of projects to generate. There
is a top level CMakeLists.txt file which doesn't define any targets,
but just includes all subdirectories as necessary. In pseudo-code, my
solution is
Hi all,
I am looking for a way to have dependencies between independent projects.
For example
ProjectA
ProjectB depends on A
ProjectC depends on B and A
What I like to do is that when project B or C is build, the dependencies
are also build. But I also want the project to be independent, to be m
My project involves a set of plugin libraries. Those libraries get loaded
dynamically at runtime, e.g. by calling dlopen(). The user can install them to
any location they want, so the directory won't necessarily be in the library
path. I can safely assume, though, that they'll all be in the s
On 09/16/2011 01:29 PM, Max Vasin wrote:
> Hello,
> I have a number of headers (say A.h, B.h, C.h) that define some kind
> of hardware abstraction layer, which header to use is determined
> by the CMakeLists.txt and specified by the macro in config.h:
>
> config.h:
> #cmakedefine HAL_H ${HAL_H}
>
Hello,
I have a number of headers (say A.h, B.h, C.h) that define some kind
of hardware abstraction layer, which header to use is determined
by the CMakeLists.txt and specified by the macro in config.h:
config.h:
#cmakedefine HAL_H ${HAL_H}
The config.h and the HAL_H are included by the header (s
On Friday 17 June 2011, Glenn Coombs wrote:
> If the library you are trying to build is one that is totally under your
> control then really it should be a subdirectory of your MY_APP source tree
> so that you can call add_subdirectory() on it. If MY_LIB is shared across
> multiple projects then y
If the library you are trying to build is one that is totally under your
control then really it should be a subdirectory of your MY_APP source tree
so that you can call add_subdirectory() on it. If MY_LIB is shared across
multiple projects then you can always arrange for it to appear as a
subdirec
On 16/06/2011 23:54, David Springate wrote:
I have the following:
A library called MY_LIB that builds with a cmake command (I have created
a nice CMakeLists.txt file)
What do you mean a cmake command? add_custom_target?
If that's how you generate your library then you need CMake 2.8.4 or
lat
Thanks for that helpful summary Jacob - and indeed you are correct I was
getting very confused (overtime is getting to me!) and forgetting of course
cmake doesn't actually *build* the product - but I do want it to generate
the makefiles that the project is dependant on, as you outlined.
Now, my se
Hej David,
You're either very confusing in explaining your needs or you just don't
understand what CMake does. CMake knows that it needs to build MY_LIB
before MY_APP, because supposedly you have written code in the
lists-file that tells CMake so.
I can't be sure, but I feel you really need
Hello,
Am Freitag, 17. Juni 2011, 11:40:15 schrieb David Springate:
> Hi Andreas,
>
> Thanks for another reply!
>
> My question therefore is:
> How can the cmake for MY_APP start the cmake for MY_LIB?
>
> I know how to get my app to link a library, and how to add the include
> directories for t
I don't see any good reason, why should cmake call itself in another
build directory?
If the library is part of the project, than it is added with
add_subdirectory in the main CMakeLists.txt file.
If the library is not part of the project, it has to be maintained from
outside.
Am I missing so
Hi Andreas,
Thanks for another reply!
My question therefore is:
How can the cmake for MY_APP start the cmake for MY_LIB?
I know how to get my app to link a library, and how to add the include
directories for the lib - so that the app can compile - but how can it
kick-start the build for MY_LIB s
Hi,
how should cmake find your MY_LIB-directory?
The simplest way, is to add the directory using
"add_subdirectory(MY_LIB_DIR ...)"
If the MY_LIB-build directory is somewhere else, in a completely
different directory, you should think about your project structure.
Andreas
Am 17.06.2011 11:0
Hi,
Thanks for the reply - but I think you might have misunderstood my question.
I want to setup CMake so that when I call Cmake like so (for MY_APP):
mkdir build && cd build
cmake .. -G Xcode
that the cmake call will be able to 'know' that it needs MY_LIB, find where
the MY_LIB CMakeLists.txt f
Hej David,
From your description I think all your build script needs to do is:
mkdir build && cd build
cmake ..
make MY_APP
Further, assuming your library also gets build with CMake, you probably
have an add_directory(../MY_LIB ../MY_LIB) in your main lists-file
(otherwise you should) and the
Hi,
I am new to CMake - and whilst I am immediately impressed with it's relative
ease of use - I have a 'noob' question, I'm sure!
I have the following:
A library called MY_LIB that builds with a cmake command (I have created a
nice CMakeLists.txt file)
An application called MY_APP that builds a
Ah, I see this is an issue already discussed in length. Well hopefully
something comes of these discussions.
Thanks for the links.
---
Aaron Wright
From: Michael Hertling
To: cmake@cmake.org
Date: 04/06/2011 05:03 AM
Subject:Re: [CMake] Dependencies scanning for non-c/c
On 04/05/2011 06:26 PM, aaron_wri...@selinc.com wrote:
> There's a base class for the dependency scanners and several derived
> classes for C, java, fortan, etc. Would it not be easy to just derive
> another class for each file type I need? These dependency scanner classes
> seemed to just rege
;m4_include".
In the mean time however, I think I could slip in one of your solutions.
Thanks again.
---
Aaron Wright
From: Michael Hertling
To: cmake@cmake.org
Date: 04/05/2011 08:36 AM
Subject:Re: [CMake] Dependencies scanning for non-c/c++ files
Sent by:cmak
On 04/03/2011 02:25 AM, aaron_wri...@selinc.com wrote:
> I have some m4 files in my build that include other m4 files, so there's a
> dependency between m4 files that can change at any time. I can calculate
> the dependency at configure time, but what can I do when the files change
> and I need
I have some m4 files in my build that include other m4 files, so there's a
dependency between m4 files that can change at any time. I can calculate
the dependency at configure time, but what can I do when the files change
and I need to recalculate the dependencies? This is obviously handled for
Dear All,
here I am again. I still have a problem with cmake dependencies which is a
bit complicated (for me at least). I really apologise in advance if what
follows is not clear, but I do need your help here. I have a coding convention
checker tool that runs on all the source files to check
On Sunday 01 August 2010 20:50:05 Dennis Schridde wrote:
> I just notice that
this command does not do what I expected it to do:
>
> set_property(TARGET
MyLib PROPERTY IMPORTED_LOCATION
> "${MYLIB_DIR}/build")
>
> Apparently it
sets the path to the *file* that is
> MyLib, not to the directory it
On Sunday 01 August 2010, Dennis Schridde wrote:
> Hello!
>
> The binary I am building has a dependency on an external
> library.
> This library may be present system-wide, otherwise I am building it
> in a subdirectory.
> Therefore I am calling these
> commands:
>
> add_custom_target(BuildMyLib ..
I just notice that this command does not do what I expected it to do:
>
set_property(TARGET MyLib PROPERTY IMPORTED_LOCATION
"${MYLIB_DIR}/build")
Apparently it sets the path to the *file* that is
MyLib, not to the directory it is in. Is there a property to set the path to
the *directory*?
With CM
Hello!
The binary I am building has a dependency on an external
library.
This library may be present system-wide, otherwise I am building it
in a subdirectory.
Therefore I am calling these
commands:
add_custom_target(BuildMyLib ...)
add_library(MyLib SHARED
IMPORTED)
add_dependencies(MyLib BuildM
On Monday 25 January 2010, Jens Auer wrote:
> Hi,
>
> I am trying to port a project from VC++ to a cmake build-system.
> Unfortunately, the project has a little problem: There are several
> libraries and some of them generate files using uic (Qt3). Cmake can
> handle this pretty well, but in one ca
Hi,
I am trying to port a project from VC++ to a cmake build-system.
Unfortunately, the project has a little problem: There are several
libraries and some of them generate files using uic (Qt3). Cmake can
handle this pretty well, but in one case, there are two libraries which
include generated hea
Jeroen Dierckx wrote:
I noticed that libraries are put into the link flags. They don't show up
in the "Linked Libraries" list of the target's info. Could it be that
everything works correctly if we could libraries there? I think XCode
does some extra logic in that case, as opposed to librari
Hi,
On Sun, Nov 8, 2009 at 5:04 AM, Bill Hoffman wrote:
> Daniel Dunbar wrote:
>
>> Hi Bill,
>>
>> Thanks for the reply.
>>
>> The uses I'm seeing aren't on external targets, they are for internal
>> libraries which are built during the build. Is this the same problem?
>>
>> Pretty much the same
Daniel Dunbar wrote:
Hi Bill,
Thanks for the reply.
The uses I'm seeing aren't on external targets, they are for internal
libraries which are built during the build. Is this the same problem?
Pretty much the same problem. A lot of it has to do with static
libraries, if you link a target to a
Hi Bill,
Thanks for the reply.
The uses I'm seeing aren't on external targets, they are for internal
libraries which are built during the build. Is this the same problem?
Also, do you know if anyone has filed a bug with Apple tracking this issue?
- Daniel
On Sat, Nov 7, 2009 at 6:10 PM, Bill
Daniel Dunbar wrote:
Hi,
I've been looking at the CMake generated Xcode project files and I'm
wondering if the dependency hacks (XCODE_DEPEND_HELPER.make) are
absolutely necessary in newer versions of Xcode. That file has some
comment about avoiding a bug in Xcode 1.5 -- is it possible to
genera
Hi,
I've been looking at the CMake generated Xcode project files and I'm
wondering if the dependency hacks (XCODE_DEPEND_HELPER.make) are
absolutely necessary in newer versions of Xcode. That file has some
comment about avoiding a bug in Xcode 1.5 -- is it possible to
generate Xcode 2.0+ specific
On Sunday 27 September 2009, Wojciech Migda wrote:
> Hi,
>
> projects created using Texas Instruments DSP tools involve compilation
> of assembler source (*.s62) and header (*.h62) files generated using a
> dedicated tool (tconf). Those source files include headers using a
> directive of a form:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
projects created using Texas Instruments DSP tools involve compilation
of assembler source (*.s62) and header (*.h62) files generated using a
dedicated tool (tconf). Those source files include headers using a
directive of a form:
.include file_na
Gerhard Gappmeier wrote:
Hi
When generating Makefiles, VS projects or Eclipse CDT projects
CMake creates artificial dependencies to CMakeLists.txt to be able to
recreate the projects
when something changes.
This is good for developers, but not so good for the users (also
developers).
We are
Hi
When generating Makefiles, VS projects or Eclipse CDT projects
CMake creates artificial dependencies to CMakeLists.txt to be able to
recreate the projects
when something changes.
This is good for developers, but not so good for the users (also
developers).
We are making portable SDKs and libra
On Thu, Mar 5, 2009 at 7:10 PM, Bill O'Hara wrote:
> Hi
>
> I'm writing a grand top-level CMakeLists.txt that delegates to a number of
> CMakeLists.txt in various subdirectories:
>
> add_subdirectories(foo)
> add_subdirectories(bar)
>
> Is there a straightforward to get cmake to do a make install
Hi
I'm writing a grand top-level CMakeLists.txt that delegates to a number of
CMakeLists.txt in various subdirectories:
add_subdirectories(foo)
add_subdirectories(bar)
Is there a straightforward to get cmake to do a make install for foo before
continuing on to do bar? And to prevent a parallel b
On Tuesday 23 September 2008 22:29:38 Phil Smith wrote:
> How does CMAKE decide on its own that A.c is dependent on B.c, and that
> compiling A.c thus requires compiling B.c?
I'm somewhat confused by what you mean. In basic terms CMake is about creating
libraries or executables. A library/executab
On 2008-09-24 11:47-0700 Phil Smith wrote:
Well, I now know why the first question got no responses: it made no sense to
those who understand things. Turns out there was another CMakeLists.txt in the
tree that was busted -- someone else checked in a bad copy. And not even
realizing that there
compared it to the
working tree!
So...any takers on the ADDITIONAL_MAKE_CLEAN_FILES question?
...phsiii
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Smith
Sent: Tuesday, September 23, 2008 5:30 PM
To: cmake@cmake.org
Subject: [CMake] Dependencies and
I suspect these questions will mostly give y'all your entertainment for the
day, but I freely admit my ignorance of things, so here goes.
Dependencies:
I'm working on porting existing code, so CMakeLists.txt already exists, and
I've made changes to it that allow me to compile. But I don't unders
Hi,
does cmake support handling of a situation when the timestamp of the
file upon which trigger for a given action is dependent (compilation,
build system regeneration) moves to past?
-Wojciech
--
Sprawdz, czy jestes leps
Bill Hoffman wrote:
Daniel wrote:
One thing I have noticed while trying to improve the speed of my builds is
that the depends.make file for a project is fairly large (15MB) and that
most of that size is dependencies against libraries I am using, mostly
Boost and Qt.
It is fairly safe to assume
Daniel wrote:
One thing I have noticed while trying to improve the speed of my builds
is that the depends.make file for a project is fairly large (15MB) and
that most of that size is dependencies against libraries I am using,
mostly Boost and Qt.
It is fairly safe to assume that I won't be mo
One thing I have noticed while trying to improve the speed of my builds is that
the depends.make file for a project is fairly large (15MB) and that most of that
size is dependencies against libraries I am using, mostly Boost and Qt.
It is fairly safe to assume that I won't be modifying these li
The CustomCommand works properly with the dependencies. This issue I
was having was that I needed the output of a EXECUTE_PROCESS command
for the outputs of the CustomCommand. Here is what I ended up
doing...
# Check to see if there are file already in the directory
# Copy the .xml file that gen
On 2007-10-01 14:15-0700 Neal Meyer wrote:
I've got a static library that contains generated code, today this is
done in a make file so I can check the dependencies before the PERL
script is called again during the build process. I'm adding a
CustomBuildCommand to the project, so the dependecie
I've got a static library that contains generated code, today this is
done in a make file so I can check the dependencies before the PERL
script is called again during the build process. I'm adding a
CustomBuildCommand to the project, so the dependecies are properly
checked in my vcproj files.
I'
Original-Nachricht
Datum: Thu, 21 Sep 2006 14:39:27 +0200
Von: "Ebersold André" <[EMAIL PROTECTED]>
An: Alexander Neundorf <[EMAIL PROTECTED]>
Betreff: Re: [CMake] Dependencies check failure
> Thanks a lot it works fine.
> So is it necessary to have
Original-Nachricht
Datum: Thu, 21 Sep 2006 12:34:46 +0200
Von: "Ebersold André" <[EMAIL PROTECTED]>
An: cmake@cmake.org
Betreff: [CMake] Dependencies check failure
> Hello,
>
> I am working with cmake 2.4.2 and have the macro bellow in a projet.
>
1 - 100 of 107 matches
Mail list logo
