Brad King wrote:
- Some of the patches remove trailing whitespace from lines unrelated to
the real change. Please identify the set of files from which you've
blanket-removed whitespace, create a commit that does just that, and
then rebase the rest of the patches on it. That will
Stephen Kelly wrote:
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
This is even more interesting now.
http://www.cdash.org/CDash/testDetails.php?test=118872016build=1620094
On gentoo, the build of
Stephen Kelly wrote:
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
This is even more interesting now.
http://www.cdash.org/CDash/testDetails.php?test=118872016build=1620094
On gentoo, the build of
Stephen Kelly wrote:
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
This is even more interesting now.
http://www.cdash.org/CDash/testDetails.php?test=118872016build=1620094
On gentoo, the build of
Stephen Kelly wrote:
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
This is even more interesting now.
http://www.cdash.org/CDash/testDetails.php?test=118872016build=1620094
On gentoo, the build of
Rolf Eike Beer wrote:
Stephen Kelly wrote:
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
This is even more interesting now.
http://www.cdash.org/CDash/testDetails.php?test=118872016build=1620094
Rolf Eike Beer wrote:
Stephen Kelly wrote:
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
This is even more interesting now.
http://www.cdash.org/CDash/testDetails.php?test=118872016build=1620094
Rolf Eike Beer wrote:
I'm not certain that's correct though. Those flags don't seem to be
used
when I build. I also don't know what those flags do.
Linking CXX executable exec
/home/stephen/dev/qt48/kde/bin/cmake -E cmake_link_script
CMakeFiles/exec.dir/link.txt --verbose=1
On Thu, Oct 13, 2011 at 4:33 PM, Richard Wackerbarth rich...@nfsnet.org wrote:
Steve,
Here is the output from the version of test19 that you sent privately.
The version of cmake was built with last night's dashboard.
I don't see the failure here. Am I doing something wrong?
Hi,
it doesn't
On Thu, Oct 13, 2011 at 12:01 PM, Stephen Kelly steve...@gmail.com wrote:
On Thu, Oct 13, 2011 at 4:33 PM, Richard Wackerbarth rich...@nfsnet.org
wrote:
Steve,
Here is the output from the version of test19 that you sent privately.
The version of cmake was built with last night's dashboard.
On Thu, Oct 13, 2011 at 8:30 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Brad King wrote:
- Some of the patches remove trailing whitespace from lines unrelated to
the real change. Please identify the set of files from which you've
blanket-removed whitespace, create a commit that does
2011/10/13 Brad King brad.k...@kitware.com:
On 10/12/2011 11:10 AM, Nicolas Desprès wrote:
I have extracted some documentation patches I have made while I was
working on the ninja-generator and some enhancement for ccmake. I
would like to submit them now. They are addressing:
- usage
2011/10/13 Nicolas Desprès nicolas.desp...@gmail.com:
2011/10/13 Brad King brad.k...@kitware.com:
On 10/12/2011 11:10 AM, Nicolas Desprès wrote:
I have extracted some documentation patches I have made while I was
working on the ninja-generator and some enhancement for ccmake. I
would like
Stephen Kelly wrote:
Ok, knowing why it fails on APPLE is good enough for me for now.
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
I was given access to a freebsd box to see why the build
On 10/13/2011 2:14 PM, Nicolas Desprès wrote:
2011/10/13 Nicolas Desprèsnicolas.desp...@gmail.com:
Thanks for the review. I have fix all the remarks.
Pushed on my github:
https://github.com/polrop/CMake/commits/some-documentation-fixes
Thanks. I will fetch it from there when I get a chance
On 10/13/2011 2:14 PM, Nicolas Desprès wrote:
2011/10/13 Nicolas Desprèsnicolas.desp...@gmail.com:
Thanks for the review. I have fix all the remarks.
Pushed on my github:
https://github.com/polrop/CMake/commits/some-documentation-fixes
That looks pretty good. I have two more comments:
-
Stephen Kelly wrote:
Ok, knowing why it fails on APPLE is good enough for me for now.
The tests can be enabled on APPLE again later, I've flipped the if
condition so we can see why it fails on some non-APPLE platforms too.
I was given access to a freebsd box to see why the build
I have code like below:
IF(MSVC)
set(CMAKE_CXX_FLAGS /Ox)
set(CMAKE_C_FLAGS /Ox)
ENDIF(MSVC)
However, the flag is ignored and CMake generates projects that use /O2.
How can I fix it?
--
Twoje radio
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
Hi Alexander,
2011/10/12 Alexander Neundorf a.neundorf-w...@gmx.net:
Hi,
On Wednesday 12 October 2011, Bernhard Sputh wrote:
Cool :-)
Please create an entry in the bug tracker for that, so it doesn't get lost.
OK, will do this later today.
Since 2.8.5 the ASM language is the one to use
Hi everyone,
I'm trying to compile in Windows an app that I have been working on in
Ubuntu for a while.
My problem is that FindBoost.cmake does not find my boost libraries even
though they are in the system.
I have them compiled with the compiler vc71, vc80.and so on
I indicate in my cmake
Hi everyone,
I'm trying to compile in Windows an app that I have been working on in
Ubuntu for a while.
My problem is that FindBoost.cmake does not find my boost libraries even
though they are in the system.
I have them compiled with the compiler vc71, vc80.and so on
I indicate in
Hi,
How can I separate settings for different configurations in Xcode.
As an example...
SET_TARGET_PROPERTIES( ${APP_NAME} PROPERTIES
XCODE_ATTRIBUTE_CODE_SIGN_ENTITLEMENTS ${IOS_CODE_SIGN_ENTITLEMENTS} )
... sets the same entitlement file for all four configurations (Debug,
On 10/13/2011 02:26 PM, Daniel Dekkers wrote:
Hi,
How can I separate settings for different configurations in Xcode.
As an example...
SET_TARGET_PROPERTIES( ${APP_NAME} PROPERTIES
XCODE_ATTRIBUTE_CODE_SIGN_ENTITLEMENTS ${IOS_CODE_SIGN_ENTITLEMENTS} )
... sets the same
Thanks Michael,
Just found it out myself as well (and yes, XCODE_ATTRIBUTE was the google
entry).
SET_TARGET_PROPERTIES( ${RT_APP_NAME} PROPERTIES
XCODE_ATTRIBUTE_CODE_SIGN_ENTITLEMENTS[variant=Debug]
${RT_IOS_CODE_SIGN_ENTITLEMENTS_DEBUG} )
SET_TARGET_PROPERTIES( ${RT_APP_NAME} PROPERTIES
Hi all,
I would like to port a hardcoded build line from an old make file to my
CMakeLists.txt file for a fortran 90
project using ifort compiler.
The line is the following:
ifort *.o -o myexec -static-intel -Bstatic -lXm -Bdynamic -lXt
First, if I get it right (sorry for my ignorance but
Hi,
Comparing Xcode generator output to standard Xcode output...
If I look at a different project file (non CMake) which shows correct behavior,
a part of the project.pbxproj looks like:
...
/* Begin XCBuildConfiguration section */
1D6058940D05DD3E006BFB54 /* Debug */ = {
As this grep from a Visual Studio build tree shows, the variables
containing /O compiler flags are the configuration-specific
variables:
$ grep /O CMakeCache.txt
CMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG
Hi,
I was looking around on the internet for how to attach files, specifically
images, to CDash submissions with CTest. I saw some other mailing list posts
related to it in which people said the attached files were showing up as plain
text instead of images on the dashboard.
The solution was
For now, no. ATTACHED_FILES uses a hard-coded file type:
type=\file\
(in CMake/Source/CTest/cmCTestTestHandler.cxx, line 1293 in today's 'next')
Instead of using ATTACHED_FILES, you could alternatively emit your own
NamedMeasurement text in the stdout output stream of your test
program. (Or
First of all I'm using cmake 2.8.6 and generating Visual Studio 2003
projects with it.
There is a particular project that needs to first copy its header files to a
specific directory in a specific structure. After that, all other projects
need to reference this project's source code from the
This works:
set( project_count 0 CACHE INTERNAL )
function( define_project )
math( EXPR count ${project_count}+1 )
set( project_count ${count} CACHE INTERNAL )
endfunction()
define_project()
message(${project_count})
define_project()
message(${project_count})
define_project()
On 10/12/2011 03:40 PM, Rolf Eike Beer wrote:
On 10/03/2011 09:18 AM, Yuri Timenkov wrote:
Hi Michael,
On Sun, Oct 2, 2011 at 6:07 PM, Michael Hertling
mhertl...@online.dewrote:
On 10/01/2011 10:07 AM, Yuri Timenkov wrote:
that's the problem: you don't know neither file name nor it's
On 10/13/2011 08:26 AM, Yuri Timenkov wrote:
See my comments inline.
I could make an implementation proposal, but I don't have time till the end
of November. So this discussion is quite pointless.
On Wed, Oct 12, 2011 at 3:02 PM, Michael Hertling mhertl...@online.dewrote:
On 10/03/2011
On Thursday 13 October 2011, Bernhard Sputh wrote:
Hi Alexander,
2011/10/12 Alexander Neundorf a.neundorf-w...@gmx.net:
Hi,
On Wednesday 12 October 2011, Bernhard Sputh wrote:
Cool :-)
Please create an entry in the bug tracker for that, so it doesn't get
lost.
OK, will do
In visual studio, there is a way to exclude a source file from the build on
a per-configuration basis (debug vs release). The actual VCPROJ looks like
this when you exclude a CPP file from the build for only DEBUG
configuration:
File
On Thu, Oct 13, 2011 at 3:37 PM, Robert Dailey rcdai...@gmail.com wrote:
In visual studio, there is a way to exclude a source file from the build on
a per-configuration basis (debug vs release). The actual VCPROJ looks like
this when you exclude a CPP file from the build for only DEBUG
On Thu, Oct 13, 2011 at 3:16 PM, David Cole david.c...@kitware.com wrote:
On Thu, Oct 13, 2011 at 3:37 PM, Robert Dailey rcdai...@gmail.com wrote:
In visual studio, there is a way to exclude a source file from the build
on
a per-configuration basis (debug vs release). The actual VCPROJ
On 10/13/2011 07:09 PM, Robert Dailey wrote:
First of all I'm using cmake 2.8.6 and generating Visual Studio 2003
projects with it.
There is a particular project that needs to first copy its header files to a
specific directory in a specific structure. After that, all other projects
need to
I used
EXECUTE_PROCESS(COMMAND cmake -E copy_if_different ${SOURCE}
${CMAKE_BINARY_DIR}/${BASENAME}.cpp )
which is done when cmake is run (before vs builds)
only problem with this is that to update that souce you need to always
run cmake before build
On Thu, Oct 13, 2011 at 10:09 AM,
On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling mhertl...@online.dewrote:
You might use an installation component for the concerned headers:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(INSTCOMP C)
SET(CMAKE_VERBOSE_MAKEFILE ON)
SET(F_PREFIX /dev/shm CACHE PATH )
FILE(WRITE
On 10/13/2011 10:56 PM, Robert Dailey wrote:
On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling mhertl...@online.dewrote:
You might use an installation component for the concerned headers:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(INSTCOMP C)
SET(CMAKE_VERBOSE_MAKEFILE ON)
Hi cmake list!
I've been playing around with cmake for a couple of weeks now, and am
loving (almost) every minute of it. A thing I really like about cmake
and that I feel will add the greatest value for me, besides the
cross-platform capabilities, is the build products go outside the
source tree
Am Donnerstag, 13. Oktober 2011, 20:09:04 schrieb Michael Hertling:
On 10/12/2011 03:40 PM, Rolf Eike Beer wrote:
On 10/03/2011 09:18 AM, Yuri Timenkov wrote:
Hi Michael,
On Sun, Oct 2, 2011 at 6:07 PM, Michael Hertling
mhertl...@online.dewrote:
On 10/01/2011 10:07 AM, Yuri
43 matches
Mail list logo
