I've been using CMAKE recently on Linux and Windows and I really like it.
Its a great way of spinning up a project and organizing your builds. There
are just a few things that are bugging me and I'm hoping to get help here.
Visual Studio Settings
Every time CMAKE generates a project it will be a
On 07/21/2014 08:05 AM, Joseph Rosensweig wrote:
Visual Studio Settings
Every time CMAKE generates a project it will be a fresh solution and
will not maintain any of the settings you applied to the Visual Studio
project. I know that many things such as CMAKE_CXX_FLAGS, etc can change
the
Hi Glenn,
Adding linker flags exactly in target_link_libraries is not a very good
practice in my opinion. To add specific linker flags to an executable, you
can use the variable CMAKE_EXE_LINKER_FLAGS, which you can edit before
calling add_executable. You could set this variable accordingly in
Hi!
if i want to add sources to list of compilation i can rely on CMAKE_BUILD_TYPE.
E.g if i want to add a source file only for release, i append it to list of
source files only then.
BUT: how can i do this for multi configuration like vs?
So i want to add it to the sources, so that it appears
On 07/21/2014 11:46 AM, Jörg Kreuzberger wrote:
Hi!
if i want to add sources to list of compilation i can rely on CMAKE_BUILD_TYPE.
E.g if i want to add a source file only for release, i append it to list of
source files only then.
BUT: how can i do this for multi configuration like vs?
So i
Jörg Kreuzberger wrote:
Is there an easy way to handle this?
Try a nightly build:
http://www.cmake.org/files/dev/?C=M;O=D
And a generator expression:
http://www.cmake.org/cmake/help/v3.0/manual/cmake-generator-expressions.7.html
add_library(mylib bar.cpp
$$CONFIG:Debug:foo.cpp
)
Hm, following your suggestion i replace lines
if( ${CMAKE_BUILD_TYPE} STREQUAL Release)
add_definitions( -DNDEBUG )
endif()
with
set_directory_properties( PROPERTIES COMPILE_DEFINITIONS_RELEASE
${COMPILE_DEFINITIONS_RELEASE};NDEBUG )
it didnt worked. ( inspecting e.q. flags.make and
On 07/21/2014 02:29 PM, Jörg Kreuzberger wrote:
Hm, following your suggestion i replace lines
if( ${CMAKE_BUILD_TYPE} STREQUAL Release)
add_definitions( -DNDEBUG )
endif()
with
set_directory_properties( PROPERTIES COMPILE_DEFINITIONS_RELEASE
${COMPILE_DEFINITIONS_RELEASE};NDEBUG )
1) i reset it with
set( CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS_INIT} )
set( CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_RELEASE_INIT} )
set( CMAKE_CXX_FLAGS_DEBUG ${CMAKE_CXX_FLAGS_DEBUG_INIT} )
and then append my own custom compiler definitions. -DNDEBUG appears in
flags.make, only in CXX_FLAGS,
On 07/21/2014 03:19 PM, Jörg Kreuzberger wrote:
1) i reset it with
set( CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS_INIT} )
set( CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_RELEASE_INIT} )
set( CMAKE_CXX_FLAGS_DEBUG ${CMAKE_CXX_FLAGS_DEBUG_INIT} )
and then append my own custom compiler definitions.
ok, then it worked.
i got no warning on the policies, maybe i would have then detected it further.
Can i enable them globally?
-Ursprüngliche Nachricht-
Von:Nils Gladitz nilsglad...@gmail.com
Gesendet: Mo 21.07.2014 15:36
Betreff:Re: AW: [CMake] Source List Compilation
On 07/21/2014 04:01 PM, Jörg Kreuzberger wrote:
ok, then it worked.
i got no warning on the policies, maybe i would have then detected it further. Can i
enable them globally?
With cmake_minimum_required(VERSION 3.0) the new behaviour is used for
the policy which is to ignore the property
Hi!
After much help from Nils from the list i am able to use GENERATOR expressions
in my compile definitions.
But i end up in the moc'ing step for my qt4 files.
The cmake macros QT4_WRAP_CPP generates a moc command file called
moc_...cxx_parameters, that contains the generator expression
The problem is that I need to add both -whole-archive and -no-whole-archive
options. And I need to control exactly where they occur so that only my
libraries occur inside the whole archive section. I'd be happy to be
proven wrong but I don't think setting CMAKE_EXE_LINKER_FLAGS will give me
that
Hendrick! That's exactly what I'm trying to do. Do you have an example
of the declaration of the dll import target setup you could share? That
would be immensely helpful.
Thanks
Walter
On 7/19/2014 4:01 AM, Hendrik Sattler wrote:
Hi,
for DLLs, the .lib part has it's own property
Well try it and see if it works. If you set this variable in a specific
CMakeLists file, it will affect the specific add_library (or
add_executable) that is in that CMakeLists file. With this way you can
control which libraries/executables will be linked with these flags, and
this is the level of
Hi,
Is it possible to (easily) install a file, say Readme.txt, into a users My
Documents folder, using CMake/CPack?
I can't find information about such.. :(
-tk
--
View this message in context:
http://cmake.3232098.n2.nabble.com/My-Documents-folder-tp7587946.html
Sent from the CMake
On Monday, July 21, 2014 08:40:11 Payal Prajapati wrote:
hello All,
Two things to say:
1)I read all conversion regarding this topic..but can any one explain me
the whole procedure?
2)I am working on orfeo toolbox which i imported in eclipse.It works fine
upto make target-build step. but
Scott Kitterman wrote:
Given the above, I thought it would make sense to provide a new
FindPyQt.cmake that would replace (and be backward compatible with)
FindPyQt4.cmake that would work for both the new and old PyQt4 configure
and with PyQt5 and have it be actually in CMake so that there
On Sun, Jul 20, 2014 at 11:49 PM, Nils Gladitz nilsglad...@gmail.com
wrote:
On 07/21/2014 08:05 AM, Joseph Rosensweig wrote:
Visual Studio Settings
Every time CMAKE generates a project it will be a fresh solution and
will not maintain any of the settings you applied to the Visual Studio
So CMAKE can't control the options int he *.user files I guess :-\? Would a
potential workaround be to find a command line tool that can edit these and
run it as a post-build script?
CMake gives you the functionality needed to edit these via your own
script. I mean reading and writing files
On 07/21/2014 09:07 PM, Totte Karlsson wrote:
Hi,
Is it possible to (easily) install a file, say Readme.txt, into a users My
Documents folder, using CMake/CPack?
I can't find information about such.. :(
I'd consider having the installed application set these up when run
since specifically
Hi Nils,
Thanks for your reply.
The installed application is a python module and it should not ever
perform any file install/copy operations.
It is an absolute requirement that the installer are able to install files
into the users MyDoc folder (or even other common system folders, sucha as
I am attempting to build an easy-to-use build system for an embedded
system. This chip uses .dat, .spin, .cogc, and .ecogc files along with
.S, .c, and .cpp. I've added the necessary language files to my project
path which will enable cogc (I'll get to the other file types
eventually) and they
On Monday, July 21, 2014 22:41:32 Stephen Kelly wrote:
Scott Kitterman wrote:
Given the above, I thought it would make sense to provide a new
FindPyQt.cmake that would replace (and be backward compatible with)
FindPyQt4.cmake that would work for both the new and old PyQt4 configure
and
On 17/07/14 16:33, Brad King wrote:
+# .. command:: configure_package_config_file
+#
+# Create a config file for a project::
The definition of the command should be in an indented block so
that reST knows it is part of the explicit markup block.
I indented the whole command block, can you
Daniele E. Domenichelli wrote:
You can generate valid config files, but in the build tree the relative
paths will always be calculated compared to CMAKE_INSTALL_PREFIX, and
this does not make sense, and also generates config files with very long
lists of ../../../ and difficult to read.
Can
On 07/21/2014 04:54 AM, Daniele E. Domenichelli wrote:
I indented the whole command block, can you please have a look if that's
what you meant? Or is it just the brief description of the command
that should be indented?
I think just the signature summary is enough. Section headers
can be used
With CMP0043 the COMPILE_DEFINITIONS_Config properties are ignored.
This currently doesn't seem to be reflected in the documentation of the
properties themselves.
Should the documentation for those properties be deleted (I think I
would personally prefer that) or extended to show that they
On 07/21/2014 10:38 AM, Nils Gladitz wrote:
Should the documentation for those properties be deleted (I think I
would personally prefer that) or extended to show that they may not have
any effect when requiring 3.0 (the policy is set to NEW)?
The latter, please.
See the intro paragraph in
On 21/07/14 14:23, Stephen Kelly wrote:
Can you give a more-concrete example of what the problem is?
I have a project that is similar to this small example:
--- CMakeLists.txt
cmake_minimum_required(VERSION 2.8.12)
project(FOO NONE)
set(FOO_VERSION 0.0.1)
On 21/07/14 16:17, Brad King wrote:
On 07/21/2014 04:54 AM, Daniele E. Domenichelli wrote:
I indented the whole command block, can you please have a look if that's
what you meant? Or is it just the brief description of the command
that should be indented?
I think just the signature summary
On 07/21/2014 11:38 AM, Daniele E. Domenichelli wrote:
Done.
Thanks. Please squash in something like the patch below.
-Brad
diff --git a/Modules/CMakePackageConfigHelpers.cmake
b/Modules/CMakePackageConfigHelpers.cmake
index 24b5b74..54ceb54 100644
---
Daniele E. Domenichelli wrote:
On 21/07/14 14:23, Stephen Kelly wrote:
Can you give a more-concrete example of what the problem is?
The project is supposed to work both from build tree (using
export(TARGETS)) and from the install tree (using install(EXPORT)).
Your example is too abstract.
On 07/20/2014 05:22 AM, Daniel Pfeifer wrote:
* add the liblzma source from XZ Utils
* make it compile with CMake (by adding CMakeLists.txt etc.)
* make it compile in VC6 (by porting the source from C99 to C90)
* make cmlibarchive use cmliblzma (using cm_lzma.h)
* add cpack generators for .7z
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 b86f0e445b1d7f9e58c8d2d9f14c7501e734057d (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 c86b99c351d313f3e45ee895a6166d55e86b245c (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, next has been updated
via 154cfe3c03b0c52bdc5ca15054b78567e1d98152 (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, next has been updated
via 4ceee50e1d51f8bea1a6f76ec267712457a39b02 (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 23ec3738a0bafd23a9d37fc72e7183e8dc84a4ac (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, next has been updated
via 8187de1946953a26308be5b3054fb0ec5ca59766 (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, next has been updated
via fe74f3b9dc321a3340b9e96646a193469d0be653 (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, next has been updated
via 5032630277c8d8097404fe5cef6772d93793f06e (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, next has been updated
via 26f4d69d567e6ae3b88821a4f25817c5876f6a1c (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, next has been updated
via c7be55d48bcf49ef83945b9fd530923ca648edc4 (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, next has been updated
via 143931d04181a6b192da26c3e3996d9cba0eb04d (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, next has been updated
via 64d13c146c0470cf46798d10146cadedf9a25445 (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, next has been updated
via 2031072957ad0de5f4e447f34075d1f95bd609eb (commit)
via
20140721)
+set(CMake_VERSION_PATCH 20140722)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
49 matches
Mail list logo
