Thanks, this works. Actually
if(CMAKE_CONFIGURATION_TYPES)
set(CMAKE_CONFIGURATION_TYPES Debug Release DebugMX31 ReleaseMX31)
set(CMAKE_CONFIGURATION_TYPES ${CMAKE_CONFIGURATION_TYPES} CACHE STRING
Reset the configurations to what we need FORCE)
endif()
also works for me. I've added
Hi,
I'm currently trying to use the following line to include all source files into
my build:
file (GLOB_RECURSE Files_CPP *.cpp)
add_executable(test
${Files_CPP}
)
Everything runs fine while using an out-of-source build, but for in-source
builds these lines include .cpp files from the
On 1. Jul, 2010, at 9:45 , Diablo 666 wrote:
Hi,
I'm currently trying to use the following line to include all source files
into my build:
file (GLOB_RECURSE Files_CPP *.cpp)
add_executable(test
${Files_CPP}
)
Everything runs fine while using an out-of-source build, but for
Hi,
thanks for your reply.
1. Never use GLOB_RECURSE. It's evil. E.g. if you add or remove source files,
CMake has no way of knowing that it should be re-run.
I have tested rerunning cmake manually and it worked out well. (Testcase: I
added a new .cpp file to the build) I either have to
On 1. Jul, 2010, at 10:15 , Diablo 666 wrote:
Hi,
thanks for your reply.
1. Never use GLOB_RECURSE. It's evil. E.g. if you add or remove source
files, CMake has no way of knowing that it should be re-run.
I have tested rerunning cmake manually and it worked out well. (Testcase: I
Hi Fraser,
It doesn't. Well, partly it does, but unfortunately setting FOO to an
empty string doesn't make it undefined; i.e. if(DEFINED FOO) will be
TRUE. I've decided to use 'if(${FOO} MATCHES ^$)' instead.
Best regards,
Marcel Loose.
On Wed, 2010-06-30 at 10:57 +0100, Fraser Hutchison wrote:
Thing is: will you never forget? And it prevents stray files from being
picked up (as you experienced). Also, you get an immediate response if a file
is missing, and not just when the compiler complains about a missing header
or you get undefined references during the linking stage.
Ok,
I have been trying to upload files as notes for my builds using the
ctest_submit(PARTS Notes) command. When i run the script it shows submissions
successful but when i check the dashboard i cannot find any notes. What am i
doing wrong ?
Regards
Johny
Hi,
I need CMake to create a Visual Studio solution for a project with several
subdirectories but only one single library.
How can I achieve project files that preserve this tree structure?
Best regards,
Andreas
2010/7/1 Diablo 666 thediablo...@hotmail.de:
Hi,
I need CMake to create a Visual Studio solution for a project with several
subdirectories but only one single library.
How can I achieve project files that preserve this tree structure?
For grouping source in Visual Studio you may use
Hi good people,
When I give an argument to -C, can this be used in the INSTALL commands?
I have a generated file in buildtype/libmysqld.exp that I need in the
installer, and I'm having a lot of problems figuring out how to do this
properly.
I have this line in a subdir CMakeLists.txt:
Marcel,
Maybe I missed it earlier ITT, but I don't understand why you can't just
use if(FOO) instead?
tyler
On Thu, Jul 01, 2010 at 11:53:33AM +0200, Marcel Loose wrote:
Hi Fraser,
It doesn't. Well, partly it does, but unfortunately setting FOO to an
empty string doesn't make it undefined;
In the CMake wiki (http://www.cmake.org/Wiki/CMake_Cross_Compiling) it says
clearly that the platform module are included in the following order;
Platform/${CMAKE_SYSTEM_NAME}.cmake (mandatory)
Platform/${CMAKE_SYSTEM_NAME}-compiler.cmake (optional)
It seems that the PROJECT() command does a fair bit behind the scenes and is
not documented enough. It seems to reset several variable created before it
was _first_ called.
Since i use cmake from cross compilation, i have created Platform files for
Generic-gcc.cmake and
On Thursday 01 July 2010, Kishore wrote:
It seems that the PROJECT() command does a fair bit behind the scenes and
is not documented enough. It seems to reset several variable created
before it was _first_ called.
Since i use cmake from cross compilation, i have created Platform files for
Hello
I'm trying to generate source files .cxx and include them in ADD_LIBRARY to
build a static library, according to
http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_generate_a_source_file_during_
the_build.3F
#
# Copy template source files to *.cxx and place them in the build dir
#
I think you mean:
${CMAKE_COMMAND} -E copy src dst
You forgot the -E.
On Thu, Jul 1, 2010 at 2:38 PM, Hicham Mouline hic...@mouline.org wrote:
Hello
I'm trying to generate source files .cxx and include them in ADD_LIBRARY to
build a static library, according to
On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
On Thursday 01 July 2010, Kishore wrote:
It seems that the PROJECT() command does a fair bit behind the scenes and
is not documented enough. It seems to reset several variable created
before it was first called.
Since i use
From: David Cole [mailto:david.c...@kitware.com]
Sent: 01 July 2010 19:58
To: Hicham Mouline
Cc: cmake@cmake.org
Subject: Re: [CMake] generating source files with ADD_CUSTOM_COMMAND
I think you mean:
${CMAKE_COMMAND} -E copy src dst
You forgot the -E.
_
I'll try that.
I added the -E, no difference.
Shouldn't an error have been printed the first time round when I didn't have
the -E. There was no error.
I traced it and the ADD_CUSTOM_COMMAND was in the trace.
Is this an indication that line is not executed at all?
From: David Cole
Did you build yet?
Custom commands are executed at build time, not at cmake configure time.
On Thu, Jul 1, 2010 at 3:21 PM, Hicham Mouline hic...@mouline.org wrote:
I added the -E, no difference.
Shouldn't an error have been printed the first time round when I didn't
have the -E. There
That must be it, obvious indeed,
Thank you,
From: David Cole [mailto:david.c...@kitware.com]
Sent: 01 July 2010 20:27
To: Hicham Mouline
Cc: cmake@cmake.org
Subject: Re: [CMake] generating source files with ADD_CUSTOM_COMMAND
Did you build yet?
Custom commands are executed at
Greetings,
I have recently created a CMake project that I use to generate Visual
Studio solutions/projects and it works perfectly with one exception.
After generating a Visual Studio 9 2008 Win64 solution, the solution
contains only the x64 build specification. Is it possible to have
I have recently created a CMake project that I use to generate Visual Studio
solutions/projects and it works perfectly with one exception.
After generating a Visual Studio 9 2008 Win64 solution, the solution
contains only the x64 build specification. Is it possible to have CMake add
the
On Thu, Jul 01, 2010 at 02:18:45PM -0500, Adarr, Lee wrote:
After generating a Visual Studio 9 2008 Win64 solution, the solution
contains only the x64 build specification. Is it possible to have CMake
Yes, this is as designed.
add the win32 build specification to the same solution or must
Hi John,
Thank you for your help.
Hopefully this gets added to the thread properly.
Thanks, Lee
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Thursday, July 01, 2010 2:43 PM
To: Adarr, Lee; CMake mailing list
Subject: Re: [CMake] Generating a combined x86
Hi Tyler,
Thank you for your help on this. Sorry, I must have missed that one. I
guess I need to take a break from this research.
Thanks, Lee
-Original Message-
From: Tyler Roscoe [mailto:ty...@cryptio.net]
Sent: Thursday, July 01, 2010 2:46 PM
To: Adarr, Lee
Cc: cmake@cmake.org
I currently have a project that I configure using CMake 2.8, and because
of a problem with Xcode on the Macintosh I need to add some checks and
adjust things in the CMake scripts to change the build configuration
when Xcode is the intended build tool. I would like to restrict these
changes
On 2. Jul, 2010, at 6:02 , Tron Thomas wrote:
I currently have a project that I configure using CMake 2.8, and because of a
problem with Xcode on the Macintosh I need to add some checks and adjust
things in the CMake scripts to change the build configuration when Xcode is
the intended
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 517f4c03f0757aff3e0289bc238986da9bdf33e0 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 9f3524f4696f394e04077aed93b482ed72cda4ca (commit)
from
31 matches
Mail list logo
