Hi,
just saw that the main cmake_install.cmake contains (at the end):
FILE(WRITE
[${CMAKE_BINARY_DIR}]/${CMAKE_INSTALL_MANIFEST}
)
FOREACH(file ${CMAKE_INSTALL_MANIFEST_FILES})
FILE(APPEND
[${CMAKE_BINARY_DIR}]/${CMAKE_INSTALL_MANIFEST}
${file}\n)
ENDFOREACH(file)
as generated by CMake git
Is there a way to indirectly call a function which name is a variable?
I want to do something like that:
function(avr_compiler_gcc_cflags CFLAGS) ...
function(avr_compiler_iar_cflags CGLAGS) ...
set(COMPILER gcc)
call(avr_compiler_${COMPILER}_cflags CFLAGS)
Is there exists
2011/9/7 Firegurafiku fireguraf...@gmail.com:
Is there a way to indirectly call a function which name is a variable?
I want to do something like that:
function(avr_compiler_gcc_cflags CFLAGS) ...
function(avr_compiler_iar_cflags CGLAGS) ...
set(COMPILER gcc)
What you can do however is set the variable which uses the FLAGS
definition, i.e. CMAKE_C_COMPILE_OBJECT in your example. I have a
CMakeLists.txt file where I override the default assembler flags:
set(CMAKE_ASM-ATT_COMPILE_OBJECT CMAKE_ASM-ATT_COMPILER ${ASM_SYS_FLAGS}
-o OBJECT SOURCE)
to use
Could you not create a file in each subdirectory called something like
header-deps.cmake ? This file would contain the include_directory()
commands necessary for using this module, plus include() commands of other
modules that it depends on. So for your example:
# utils/b/header-deps.cmake
Hi,
I'm targeting iOS and wondering how to add a Settings.bundle directory to the
project via CMake.
The Settings.bundle contains preferences for the app that can be set by the
user in the settings pane of the iPhone/iPad device.
If i manually add it (right click, add files to [appname]...) in
On Mon, 5 Sep 2011 06:49:45 +0200, Michael Wild said:
Shouldn't dynamic libraries on Mac have dylib as their extension?
Why does MyLib have an extension so when I use add_library(MyLib MODULE)?
Thanks
Yifei
Because a MODULE is normally a plugin library, and these
traditionally have the
On 9/7/2011 11:43 AM, Sean McBride wrote:
Because a MODULE is normally a plugin library, and these
traditionally have the extension .so on Mac.
Do they?
I just searched all of /System and the only .so I find are in
Python.framework. I've been using Macs since the early 90s, I don't
recall
Because of CDash/CTest's strange Append/Accumulation behaviour with
consecutive report submits it would be convenient to provide multiple
targets within a single call to CTEST_BUILD(). How to do this correctly?
___
Powered by www.kitware.com
Visit other
2011/9/7 Firegurafiku fireguraf...@gmail.com:
Do not forget to CC the ML (or reply to ML).
With CMake:
1) you can ask CMake for double evaluation
using nested dollar ($) var value:
Try:
set(COMP1_CFLAGS Whatever)
set(COMP2_CFLAGS OrElse)
set(COMPILER COMP1)
There are already these feature requests that seem to cover the exact
same topic:
http://public.kitware.com/Bug/view.php?id=11845
http://public.kitware.com/Bug/view.php?id=4034
I personally do not think that EVAL adds significant value to the
CMake language. And I think it would introduce
-- Forwarded message --
From: Peter Collingbourne pe...@pcc.me.uk
Date: Wed, Sep 7, 2011 at 9:17 PM
Subject: Proposal: restat rules
To: ninja-bu...@googlegroups.com
Hi,
In this email I'll try to explain one of the oddities of make (which
some CMake-based build systems rely on),
Thanks, Glenn. That almost works. However, the values of FLAGS is hard to
construct in this case. It looks something like this:
add_library(mylib, STATIC, ${files})
set_target_properties(mylib
PROPERTIES PREFIX
Hi Glenn,
On Wed, Sep 7, 2011 at 20:36, Glenn Coombs glenn.coo...@gmail.com wrote:
Could you not create a file in each subdirectory called something like
header-deps.cmake ? This file would contain the include_directory()
commands necessary for using this module, plus include() commands of
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 accdb855c293d081580f17ed8521ca20b0dcce0e (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 56ce5dec8b9973528ae8b41a77e757c11eff81b1 (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 a239fb6c16ab075fdbd2f306b3f34369f9087d43 (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 103ab60dd7314f6a75b02dc65d40a99efedc5391 (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 f62540adcc1dd53b66534f6ed7c03b5e5daf1d26 (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 db4154661cfa1baf2596ce4c68ac8a328690245d (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 de62fd1b6d268702473b3307f48eb4cefb8c2c5d (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 05bc6bfb87a9afe9c85bd90406fce348a92b7807 (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 c80cbad15226844c2c518e49656fe19fc52d8d33 (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 07eb08439ddeaaab1115acaf717b52319efdfb13 (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 fde0a4ddd104be279600f3a80521169708a84875 (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 4e3d428cc30a6a45477720c8153b4f32952ae949 (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 abf88b50008f60c76aeaa751f2ee20ceab2114c3 (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 ec8434567837e8305a2d67734d49f0b70ad7fe3b (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 3246dc26651c50cebd99b64ca8fb1a05873f192f (commit)
from
29 matches
Mail list logo
