On Thu, Mar 21, 2013 at 11:06 AM, Vittorio Giovara
vittorio.giov...@gmail.com wrote:
On Wed, Mar 20, 2013 at 2:05 PM, Brad King brad.k...@kitware.com wrote:
On 3/20/2013 4:52 AM, Vittorio Giovara wrote:
is it possible to use the TARGET variable during the COMPILE_OBJECT
phase?
I see it
On Thu, Mar 21, 2013 at 1:11 PM, Vittorio Giovara
vittorio.giov...@gmail.com wrote:
On Thu, Mar 21, 2013 at 11:06 AM, Vittorio Giovara
vittorio.giov...@gmail.com wrote:
On Wed, Mar 20, 2013 at 2:05 PM, Brad King brad.k...@kitware.com wrote:
On 3/20/2013 4:52 AM, Vittorio Giovara wrote:
Hi,
When the try_compile source-file signature is used, it generates a
cmake_minimum_required line with the version of cmake run by the user (not
the minimum used by the project being built).
This affects policies, and could have an effect on the generated
CMakeLists.txt file. Anyone using
On 03/21/2013 08:29 AM, Stephen Kelly wrote:
When the try_compile source-file signature is used, it generates a
cmake_minimum_required line with the version of cmake run by the user (not
the minimum used by the project being built).
This affects policies, and could have an effect on the
On 03/20/2013 04:31 PM, Alexander Neundorf wrote:
The keywords won't interact well with PUBLIC/PRIVATE/INTERFACE keywords.
Let's assume there would be only PRIVATE, INTERFACE_BUILD and
INTERFACE_INSTALL.
I'll use PRIVATE for building the target.
I'll add INTERFACE_BUILD if I want to make
On Thursday 21 March 2013, Matthew Woehlke wrote:
On 2013-03-20 17:42, Alexander Neundorf wrote:
On Wednesday 20 March 2013, Matthew Woehlke wrote:
On 2013-03-20 17:10, David Cole wrote:
Are you proposing that == behaves as STREQUAL, or as EQUAL?
What's the difference?
Okay, for ,
On Thursday 21 March 2013, Brad King wrote:
On 03/20/2013 04:31 PM, Alexander Neundorf wrote:
...
So e.g. I could do
tid(hello
PRIVATE ${Foo_INCLUDE_DIRS} ${Bar_INCLUDE_DIRS}
${CMAKE_SOURCE_DIR}/blub INTERFACE_BUILD ${CMAKE_SOURCE_DIR}/blub
${Bar_INCLUDE_DIRS}
On 03/21/2013 02:47 PM, Alexander Neundorf wrote:
Still, is the PUBLIC part necessary ?
IMO PRIVATE and INTERFACE suffice, and for me it seems more straighforward to
separate only between these two.
PRIVATE and INTERFACE are sufficient but need to be duplicated
to produce the equivalent of
Unfortunately, this entire discussion nicely demonstrates and
reinforces my belief that we ought not to do this == thing...
If Alex, Brad, Matthew and I can't understand each other's meanings
within the context of this discussion, what chance does a poor user
reading through the CMake IF
On 2013-03-21 14:56, David Cole wrote:
Unfortunately, this entire discussion nicely demonstrates and reinforces
my belief that we ought not to do this == thing...
If Alex, Brad, Matthew and I can't understand each other's meanings
within the context of this discussion, what chance does a poor
Is there a best practices using existing functionality to always avoid
automatic dereference when comparing strings?
Clint
On Thursday, March 21, 2013 02:56:51 PM David Cole wrote:
Unfortunately, this entire discussion nicely demonstrates and
reinforces my belief that we ought not to do this
I almost always do one of these for string compare to a CMake variable
value:
if(${var} STREQUAL some string constant)
if(${var} STREQUAL ${some_other_variable})
However, this is only because I am almost always certain that ${var}
does not evaluate to the name of yet another CMake
On 03/21/2013 03:40 PM, Clinton Stimpson wrote:
Is there a best practices using existing functionality to always avoid
automatic dereference when comparing strings?
if(x${LHS} STREQUAL x${RHS})
One can construct pathological cases that will break it but it works
well.
-Brad
--
Powered by
On 2013-03-21 16:55, David Cole wrote:
I almost always do one of these for string compare to a CMake variable
value:
if(${var} STREQUAL some string constant)
if(${var} STREQUAL ${some_other_variable})
However, this is only because I am almost always certain that ${var}
does not
Hi,
I have a suggestion for the PythonInterp. On a system I am compiling my
code on, I need to find the python binary which is newer than 2.5.
However, the default /usr/bin/python is 2.4.
If I then set the variable (which is not documented in the header by the
way) PythonInterp_FIND_VERSION to
I am trying out CMake 2.8.11rc1 on windows and linux continuous build
clients.
During clean full rebuilds everything seems to work fine.
During incremental Continuous builds with reused build directories
however CMAKE_OBJCOPY (on linux gcc; used by me manually) and
CMAKE_LINKER (on windows
Am 21.03.2013 11:03, schrieb Yngve Inntjore Levinsen:
Hi,
I have a suggestion for the PythonInterp. On a system I am compiling
my
code on, I need to find the python binary which is newer than 2.5.
However, the default /usr/bin/python is 2.4.
If I then set the variable (which is not
Hi,
I am trying out CMake 2.8.11rc1 on OS X Lion with XCode 4.4.1
When I use the Xcode generator, I get the following messages
=
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
--
2013/3/20 Theodore Papadopoulo theodore.papadopo...@inria.fr:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/20/2013 05:01 PM, Eric Noulard wrote:
2013/3/20 Theodore Papadopoulo theodore.papadopo...@inria.fr:
And do you observe differences when you do that?
As I said above, no there
2013/3/20 Theodore Papadopoulo theodore.papadopo...@inria.fr:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, this patch works better... and is much simpler.
Yes right.
Some other modifications of yours in
Source/cmFindBase.cxx
Source/cmFindLibraryCommand.cxx
Do not belong to that
In my win project, when I use the visual studio generator (64bit), I always get
the /D _MBCS flag in the compiler options
(started with msbuild).
When I generate Makefiles with the same project (JOM NMakefiles), _MBCS is not
defined.
I do not want to have it defined. How can I avoid it and still
On Thu, Mar 21, 2013 at 10:20 AM, Martin Koller martin.kol...@etm.at wrote:
In my win project, when I use the visual studio generator (64bit), I always
get the /D _MBCS flag in the compiler options
(started with msbuild).
When I generate Makefiles with the same project (JOM NMakefiles), _MBCS
On Thursday 21 March 2013 15:29:18 John Drescher wrote:
On Thu, Mar 21, 2013 at 10:20 AM, Martin Koller martin.kol...@etm.at wrote:
In my win project, when I use the visual studio generator (64bit), I always
get the /D _MBCS flag in the compiler options
(started with msbuild).
When I
On Thu, 21 Mar 2013 22:27:41 +1100, Nicholas Yue said:
I am trying out CMake 2.8.11rc1 on OS X Lion with XCode 4.4.1
My dashboard here:
http://open.cdash.org/buildSummary.php?buildid=2851443
Is running OS X 10.7.5, CMake 2.8.11rc1, and Xcode 4.4.1. It's able to build
(nightly) CMake
On 21. mars 2013 12:00, Rolf Eike Beer wrote:
Am 21.03.2013 11:03, schrieb Yngve Inntjore Levinsen:
Hi,
I have a suggestion for the PythonInterp. On a system I am compiling my
code on, I need to find the python binary which is newer than 2.5.
However, the default /usr/bin/python is 2.4.
If
Eric Noulard said:
Instead of copying you could use
cmake -E create_symlink
but this won't work on Windows.
If building on Windows is required, you could make a symlink, hardlink, or
junction point. If on Vista or later, look at the command mklink. Symlinks
require admin privileges, but
Yngve Inntjore Levinsen wrote:
On 21. mars 2013 12:00, Rolf Eike Beer wrote:
Am 21.03.2013 11:03, schrieb Yngve Inntjore Levinsen:
Hi,
I have a suggestion for the PythonInterp. On a system I am compiling my
code on, I need to find the python binary which is newer than 2.5.
However,
Our build it taking a long time, (15+ minutes even when with a massive build
farm to distribute compiles across), and the question keeps coming up: what is
actually taking so long. Is there an easy way to measure?
If there are some top 10 files we might be able to split them (reducing some
Hello,
I'm having a hard time figuring out which solution to choose to build a library
(FFmpeg) based on autotools from CMake, and I have the impression I'm going the
tricky way.
I know how to run the FFmpeg's configure and make scripts with the right
options from a bash script. I made a
Hi,
Is there a way to get a coredumps from failures that happen durink 'make
test'?
Thanks,
Martin
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
On 22/03/13 2:19 AM, Sean McBride wrote:
On Thu, 21 Mar 2013 22:27:41 +1100, Nicholas Yue said:
I am trying out CMake 2.8.11rc1 on OS X Lion with XCode 4.4.1
My dashboard here:
http://open.cdash.org/buildSummary.php?buildid=2851443
Is running OS X 10.7.5, CMake 2.8.11rc1, and Xcode
2013/3/21 Miller Henry millerhe...@johndeere.com:
Our build it taking a long time, (15+ minutes even when with a massive build
farm to distribute compiles across), and the question keeps coming up: what
is actually taking so long. Is there an easy way to measure?
Your build certainly have a
2013/3/21 Martin Sustrik sust...@250bpm.com
Hi,
Is there a way to get a coredumps from failures that happen durink 'make
test'?
Thanks,
Martin
--
What do you mean by get coredump?
Any crash should produce core if ulimit -c unlimited set.
--
Best Regards,
Sergei Nikulov
--
Powered by
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index bd315c0..d3bbf1e 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 20130321
34 matches
Mail list logo
