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
Thanks for your answer.
I thought CPACK_PACKAGE_EXECUTABLES was for NSIS installer for adding
start menu entry:
http://www.vtk.org/Wiki/CMake:CPackConfiguration
Is it used for something else?
After reading the source code, I think you are right. It not used by the rpm
generator.
-
2009/6/30 Knox, Kent kent.k...@amd.com:
I'm integrating CPack into my build system, and can't quite get
CPACK_SOURCE_IGNORE_FILES to work right.
I want to cull individual files from the source package, like .ncb files
and .pdb files and such. It seems as though CPACK_SOURCE_IGNORE_FILES
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
James Bigler wrote:
I have a project that generates object files as part of the
compilation. I add the object names to the project with
${CMAKE_CFG_INTDIR} in the file name and they show up in the solution
explorer (which is what I would expect).
VS seems to do the right thing most of the
Knox, Kent wrote:
I've just stumbled across some surprising cl.exe behavior, and I
would like to see if the collective minds of this dist list has come
across this before.
In my c++ project, I override CMAKE_CXX_FLAGS with my own flags,
including /TP. Using an nmake based build, this causes
On Tue, Jun 30, 2009 at 03:10:41PM +0200, Benjamin Schindler wrote:
Visual Studio users, this is not yet good enough: The files which are
not included in an add_executable are not visible in the Visual Studio
solution/project which is quite a pain. For header files this is no
problem
Yes, thank you for the response; I am in the process of moving my project from
MSVC solution to out-of-source cmake builds.
Please ignore the fact that I used a generated file in my previous example,
that's tangential to the problem I'm reporting. Pretend that the set statement
is:
set(
It's the leading / in the txt portion of the expression. get rid of
it.
(Eric already pointed this out in his reply to this email...)
With the expression the way it is, you're trying to exclude things that have
literal /.txt in them. What you want is .txt right?
On Tue, Jun 30, 2009 at
Yes, I did try to escape the $; no joy.
No, I'm not against leaving the $ out, but I can't get it to work
anyway.
Kent
-Original Message-
From: Tyler Roscoe [mailto:ty...@cryptio.net]
Sent: Monday, June 29, 2009 10:10 PM
To: Knox, Kent
Cc: cmake@cmake.org
Subject: Re: [CMake]
Yes, this was the trick. Thank you to Eric Noulard and David Cole
With the expression the way it is, you're trying to exclude things that
have literal /.txt in them. What you want is .txt right?
I suppose that I'm a little confused by the RegEx. So with the '/'
characters, was I literally
On Tue, Jun 30, 2009 at 11:43 AM, Knox, Kent kent.k...@amd.com wrote:
Yes, this was the trick. Thank you to Eric Noulard and David Cole
With the expression the way it is, you're trying to exclude things that
have literal /.txt in them. What you want is .txt right?
I suppose that I'm a
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
16 matches
Mail list logo