Brad King wrote:
I think what we need is for the cmTarget::LinkInterface structure
to have a new TargetNames member populated by ComputeLinkInterface
from a new INTERFACE_TARGET_DEPENDS property (better names?).
On export of the link interfaces the net collection of target names
that refer
Brad King wrote:
The new infrastructure will have to somehow treat non-imported
target names as plain library names for its purposes, at least when
invoked through one of the existing check module interfaces.
Thanks for the hint. That was not very difficult.
Now though I have another few
Steve,
Please take a look at this example:
$ touch foo.h bar.cpp
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8.6)
project(FOO)
find_package(Qt4 REQUIRED)
add_library(bar STATIC bar.cpp)
set_target_properties(bar PROPERTIES AUTOMOC TRUE)
target_link_libraries(bar foo)
add_library(foo
Brad King wrote:
Please fix and add this case to the tests.
I've added fix-automoc-linker-language to stage. Alex, could you review
please?
Thanks,
Steve.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
Hi,
I just pushed generate-export-header-warnings to the stage, this
removes the warnings emitted when the compiler is old. When making
extensive use of generate export headers these warnings only serve to
obscure real warnings, when in my opinion generate export header is
doing precisely what it
Brad King wrote:
On 02/20/2013 06:51 AM, Stephen Kelly wrote:
Now though I have another few errors I can't reproduce:
All of the Mac 10.8 machines seem to fail like this:
http://open.cdash.org/viewConfigure.php?buildid=2819601
Any idea what's going on?
Thanks,
Steve.
--
Powered by
ctest version 2.8.10.20121106-g262ff
I blew away the CMake-build tree.
New revision of repository is: aaa9ccf325b386d8b500c0b95a2cac1409375d51
It failed again.
Richard
On Feb 20, 2013, at 12:19 PM, Brad King brad.k...@kitware.com wrote:
On 02/20/2013 01:06 PM, Richard Wackerbarth wrote:
On Friday 15 February 2013, Alexander Neundorf wrote:
On Friday 15 February 2013, Stephen Kelly wrote:
Hi,
FindPackageHandleStandardArgs sets an uppercase found variable, but not
an ExactCase_FOUND variable. This is inconsistent with how config files
work. It also imposes on users the
Hi,
I have a small patch in the cmLocalGenerator_RemoveVirtuals branch, which
makes a bunch of functions non-virtual.
Ok to merge into next or do you want to keep them virtual ?
Alex
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
On 02/20/2013 01:50 PM, Alexander Neundorf wrote:
I have a small patch in the cmLocalGenerator_RemoveVirtuals branch, which
makes a bunch of functions non-virtual.
Ok to merge into next or do you want to keep them virtual ?
Fine with me. I think some of them used to be overridden
but do not
On 02/20/2013 11:53 AM, Marcus D. Hanwell wrote:
I just pushed generate-export-header-warnings to the stage, this
removes the warnings emitted when the compiler is old. When making
extensive use of generate export headers these warnings only serve to
obscure real warnings, when in my opinion
On 02/20/2013 01:27 PM, Richard Wackerbarth wrote:
ctest version 2.8.10.20121106-g262ff
I blew away the CMake-build tree.
New revision of repository is: aaa9ccf325b386d8b500c0b95a2cac1409375d51
It failed again.
Richard sent me his CMakeError.log and it shows that the try compiles
now
On Wednesday 20 February 2013, Stephen Kelly wrote:
Brad King wrote:
Please fix and add this case to the tests.
I've added fix-automoc-linker-language to stage. Alex, could you review
please?
If I see it correctly, actually nothing is done to each target between the
calls to
On Wednesday 20 February 2013, Brad King wrote:
On 02/20/2013 03:44 AM, Stephen Kelly wrote:
Brad King wrote:
I think what we need is for the cmTarget::LinkInterface structure
to have a new TargetNames member populated by ComputeLinkInterface
from a new INTERFACE_TARGET_DEPENDS property
Alexander Neundorf wrote:
On Wednesday 20 February 2013, Stephen Kelly wrote:
Brad King wrote:
Please fix and add this case to the tests.
I've added fix-automoc-linker-language to stage. Alex, could you review
please?
If I see it correctly, actually nothing is done to each target
Brad King wrote:
On 02/20/2013 11:53 AM, Marcus D. Hanwell wrote:
I just pushed generate-export-header-warnings to the stage, this
removes the warnings emitted when the compiler is old. When making
extensive use of generate export headers these warnings only serve to
obscure real warnings,
Hello Brad,
Am Mittwoch, 20. Februar 2013, 00:36:18 schrieb Brad Bell:
My goal is to use some new c++11 features if they are available,
otherwise to stick to the c++03 features. I need to build test programs
that check for correctness as well as distribute an include file library.
Is there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nowadays, asking for c++-11 is probably too coarse as implementations
are usually uncomplete. So you have a stdc++-11 switch and still
missing some features on which you rely.
Another technique is to test features instead of the whole standard,
that
Hmm. I've just tried this but it didn't work for me. The Runpath Search
Path field is still blank.
Do I have to do things in a particular order to get it to work? Though I
have tried moving it around and still couldn't get it to work.
Darrell
On 20 February 2013 00:17, Alexey Petruchik
Hello Darrell,
you can also set it as a property per target
set_target_properties(MyExecutable
PROPERTIES
XCODE_ATTRIBUTE_LD_RUNPATH_SEARCH_PATHS @loader_path;@loader_path/../lib
)
This should work, but I think CMake could use some facilities to handle the
executables runpath search
I think I've just answered my own question. It looks like it has to be in
the root CMakeLists.txt. If I put it in one included from
add_subdirectory() it doesn't work but in the root CMakeLists.txt it does.
On 20 February 2013 10:39, Darrell Blake darrell.bl...@gmail.com wrote:
Hmm. I've just
Ah, cool. That's much better. Cheers.
On 20 February 2013 10:54, Andreas Stahl andreas.st...@tu-dresden.dewrote:
Hello Darrell,
you can also set it as a property per target
set_target_properties(MyExecutable
PROPERTIES
XCODE_ATTRIBUTE_LD_RUNPATH_SEARCH_PATHS
I am developing an application on windows with VS2012 and CMake
(2.8.10.2). I want to use unicode in my program, so I add UNICODE and
_UNICODE with ADD_DEFINITIONS. However, there is always a _MBCS marco in
the generated project file. The project can be compiled, but I am not happy
with that.
On 2013-02-18 10:00, YanmingZou wrote:
I am developing an application on windows with VS2012 and CMake
(2.8.10.2). I want to use unicode in my program, so I add UNICODE and
_UNICODE with ADD_DEFINITIONS. However, there is always a _MBCS marco in
the generated project file. The project can be
Hi Niels, Thanks for your example. It works well on my PC. So there should be
something wrong in my files. I will check and let you know the reason when I
find it. Best regards and thanks again.Yanming
Date: Wed, 20 Feb 2013 15:36:21 +0100
From: niels_dekker_address_until_2...@xs4all.nl
To:
On 2013-02-18 04:00, YanmingZou wrote:
I want to use unicode in my program, so I add UNICODE and
_UNICODE with ADD_DEFINITIONS. However, there is always a _MBCS marco
in the generated project file.
Depending on where it is coming from...
add_definitions(-DUNICODE -D_UNICODE -U_MBCS)
Hi,
I've noticed a problem in running CMake concurrently, targeting Visual
Studio 11 solution files (also reproduced with Visual Studio 10). The
use case is a Jenkins job building LLVM, and this kicks off child jobs
to build in Debug and Release mode, at the same time but in different paths.
I am using cmake-2.8.10.2-win32-x86 and vtk-5.10.1.
I am trying to configure VTK, I have installed Visual Studio 10 (not the
express version, the full one along with SP1), with x64 support. However,
when selecting Visual Studio 10 (for 32 bit)or Visual Studio 10 x64 and
choosing the default
On Wed, Feb 20, 2013 at 2:07 PM, amitsuveer amitsuv...@gmail.com wrote:
I am using cmake-2.8.10.2-win32-x86 and vtk-5.10.1.
I am trying to configure VTK, I have installed Visual Studio 10 (not the
express version, the full one along with SP1), with x64 support. However,
when selecting Visual
Hi, I have Ubuntu 12.04, and I have already cmake
installed (2.8.7)
To compile the
last version of Sigil, I need 2.8.9 or
higher, so I tried to install it.
Unfortunately, the sh file just allows to install directly under Downloads
Hi Alain,
Instead, in a terminal you could simply do the following:
cd mkdir Support cd Support \
wget http://www.cmake.org/files/v2.8/cmake-2.8.10.2-Linux-i386.tar.gz \
tar -xzvf cmake-2.8.10.2-Linux-i386.tar.gz \
./cmake-2.8.10.2-Linux-i386/bin/cmake -version
This will create a
Le 20/02/2013 21:35, Jean-Christophe
Fillion-Robin a crit:
Hi Alain,
Instead, in a terminal you could simply do the
following:
cd
mkdir Support cd Support \
Hi,
/usr/local/bin being before /usr/bin in the path, the cmake located locate
there will be used.
See also:
http://unix.stackexchange.com/questions/8656/usr-bin-vs-usr-local-bin-on-linux
The use of which can also be helpful. See
http://unixhelp.ed.ac.uk/CGI/man-cgi?which
Hth
Jc
On Wed,
2013/2/20 Alain Aupeix alain.aup...@wanadoo.fr:
Le 20/02/2013 21:35, Jean-Christophe Fillion-Robin a écrit :
Hi Alain,
Instead, in a terminal you could simply do the following:
cd mkdir Support cd Support \
wget http://www.cmake.org/files/v2.8/cmake-2.8.10.2-Linux-i386.tar.gz \
tar
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 05f3537f1b4ae9c1f2008c6e9d412990f2b48ae0 (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 a901685e9e6ef6db8ba6a60b0e6faba98282f92b (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 414658f0572497fffcb865485f08cd2d26ce040f (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 54d77467e6e1e631c49e5dcb9518f7459a0b9aea (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 f1cd42f8182946109f71fdd37956245c0d8cfb4f (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 fc7b4d5cf320ca0c3b81be4e7163215d870342c4 (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 f7029572ca5948ff87ba0c6e8aaff35f6fdab4f1 (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 3129fe173ed5c15465a8f5e7ff989500a4c5caee (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 aaa9ccf325b386d8b500c0b95a2cac1409375d51 (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 c46387bcc87cf55718e30f2013b5164cb8858fe2 (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 26d2380d3a1090170b4607217db7558576983e5d (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 f6180d8aee61e7f170caadcce23eda6623665eba (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 7487a8f9b09bd683c34da4db1c969b6cff45e9e9 (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 2bb5dd19d2d2134efd6b0396daee5c462d7a9bed (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index a03488f..3a3b8b9 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 10)
-set(CMake_VERSION_TWEAK 20130220
49 matches
Mail list logo
