Hi Paul.
Look up "generator expressions" in the CMake docs (for example in
"add_custom_command"), particularly $. It might help in
solving your issue.
Petr
On Wed, May 29, 2013 at 10:52 PM, Paul Smith wrote:
> No love for this question apparently :-/
>
> I tried to implement the suggestion in
- Reply message -
From: "j s"
To: "Michael Wild"
Cc: "CMake mailing list"
Subject: [CMake] write file if different?
Date: Wed, May 29, 2013 20:44
On Wed, May 29, 2013 at 2:32 AM, Michael Wild wrote:
>
> On 28.05.2013 22:07, Matthew Woehlke wrote:
> > Is there a built-in way to write
- Original Message -
> Hello,
>
> I'm using cmake to generate an Xcode project which is supposed to build a
> bundle. Thus, I use the source file property MACOSX_PACKAGE_LOCATION to
> place my data (database, GUI, localization files, …) in the correct
> directory in my bundle.
>
> I use
Hello,
I'm using cmake to generate an Xcode project which is supposed to build a
bundle. Thus, I use the source file property MACOSX_PACKAGE_LOCATION to place
my data (database, GUI, localization files, …) in the correct directory in my
bundle.
I used to have a general CMakeLists.txt with seve
No love for this question apparently :-/
I tried to implement the suggestion in the mailing list post below, and
it works fine with UNIX makefiles.
But, on other generators such as Xcode and MSVC there's a major problem
that I don't know how to solve. The post suggests forcing a new target
like
On Wed, May 29, 2013 at 2:32 AM, Michael Wild wrote:
>
> On 28.05.2013 22:07, Matthew Woehlke wrote:
> > Is there a built-in way to write a string to a file (a la FILE(WRITE))
> > that will only write the file if the content would be different? (Or
> > does FILE(WRITE) already work this way despit
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
I haven't looked into CMake code deep enough, so I don't really know how it
works either. Maybe project() stores something into the cache which causes
it to not trample over the configuration list in the next run. Just
guessing.
Petr
On Wed, May 29, 2013 at 4:40 PM, gaga bla wrote:
> Hello Pet
Hello Petr,
i don't understand how this solves the problem, but indeed it does!
Still i have one small problem. To make regeneration of a clean project as
easy as possible, i have a batch file, which first clears all generated
data (including cmake cache), an then runs cmake. Since this fails now
Hello, I'm trying to generate a Visual Studio 11 solution using v100
toolset and it is failing to compile a test program:
I run cmake -G "Visual Studio 11 Win64" -T "v100"
-- The C compiler identification is MSVC 16.0.40219.1
-- The CXX compiler identification is MSVC 16.0.40219.1
-- Check for w
Hi Janosch.
A solution to this problem which works for me is: if the configurations are
not those I want, set them correctly and abort the generation (with a help
message).
I put the following code into the CMakeList after the call to project():
if(CMAKE_CONFIGURATION_TYPES AND NOT CMAKE_CONFIGU
Hello Eric,
thanks for your reply, i tried this, but in my case it doesn't work. I made
a function that first sets the configuration types (using your line of
code) and then calls the project function. Using this function instead of
the project function itself, still all configurations are beeing g
On 28.05.2013 22:07, Matthew Woehlke wrote:
> Is there a built-in way to write a string to a file (a la FILE(WRITE))
> that will only write the file if the content would be different? (Or
> does FILE(WRITE) already work this way despite no obvious hint in the
> documentation that it does?)
>
> Rig
13 matches
Mail list logo
