-Ursprüngliche Nachricht-
Von: Marcel Loose [mailto:lo...@astron.nl]
Gesendet: Donnerstag, 2. Juli 2009 12:13
An: cmake@cmake.org
Cc: Jörg Förstner
Betreff: Re: [CMake] Problem with generated source and header files
Hi Joerg,
As far as I know there's no hook in CMake to do this. Did you
try
Hi James,
On Wednesday 01 July 2009 15:58:12 James C. Sutherland wrote:
So, in general, when using globbing, YOU are responsible for rerunning
CMake whenever you've added a source file. Otherwise you run the
risk of
the new file not being compiled. Furthermore, you might accidentally
in the CMakeLists.txt
files (some kind of a hook)?
Regards,
Joerg
-Ursprüngliche Nachricht-
Von: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org]
Im Auftrag von Marcel Loose
Gesendet: Donnerstag, 2. Juli 2009 09:57
An: cmake@cmake.org
Betreff: Re: [CMake] Problem with generated source
So, in general, when using globbing, YOU are responsible for rerunning
CMake whenever you've added a source file. Otherwise you run the
risk of
the new file not being compiled. Furthermore, you might accidentally
compile sources that were just lying around in your directory as test
code.
I hope my examples convinced you enough that globbing is (in general) a
bad idea.
So is it common practice among users of CMake to manually create and
maintain a list of all files that are to be compiled, even if such a list is
very large and may involve several directories and
Hi Joerg,
Is there a fixed, predictable relation between the input file(s) to the
generator and the output file(s) that are generated; like with Bison or
Flex?
If that's the case you can construct the list of files to be generated
from the list of input files to the generator. If the list of
Hi Marcel,
Is there a fixed, predictable relation between the input
file(s) to the
generator and the output file(s) that are generated; like
with Bison or
Flex?
The output files' names and contents are derived from a MetaModel. New objects
in the MetaModel result in new files' names and
Hi Tyler,
I don't know if linking multiple shared libraries together
like that is
going to work. You might need to compile libxyz.generated as a static
lib.
You're right. Either I'll have to use a static library for libxyz.generated or
I manage to add the generated objects to libxyz (the
2009/6/30 Jörg Förstner joerg.foerst...@ubidyne.com:
Hi Tyler,
I don't know if linking multiple shared libraries together
like that is
going to work. You might need to compile libxyz.generated as a static
lib.
You're right. Either I'll have to use a static library for libxyz.generated
or
Hi,
I have a possible solution, but at the cost of a different CMake problem then.
INTERMEDIATE SOLUTION:
==
If the generator creates one file everything.cpp, which contains the source
code of all separately created *.cpp files, I could use everything.cpp as a
defined
On Tue, Jun 30, 2009 at 06:53:07PM +0200, Jörg Förstner wrote:
The generator now is called EVERY TIME I run make, because
- I need two separate CMakeLists.txt files now,
- I have to make a custom target, otherwise CMake does not know
everything.cpp and quits with an error.
- the custom
Hello everybody,
I have a problem with generated source and header files.
The main problem is, that I don't want to note each generated file's name
manually in a CMakeLists.txt file, because the output of the file generator
changes frequently.
The sequence of the build process shall be:
1. Go
On Mon, Jun 29, 2009 at 08:24:12PM +0200, Jörg Förstner wrote:
The sequence of the build process shall be:
1. Go to build directory and execute cmake source-path
2. Execute make
3. The generator shall be called (but only if the source and header files are
not yet generated).
4. The
13 matches
Mail list logo
