[cmake-developers] [CMake 0012614]: Support for RVDS 4.1: ARM C/C++ and ASM compilers.
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12614
==
Reported By:Abdelrazak Younes
Assigned To:
==
Project:CMake
Issue ID: 12614
Category: Modules
Reproducibility:N/A
Severity: feature
Priority: normal
Status: new
==
Date Submitted: 2011-12-09 03:18 EST
Last Modified: 2011-12-09 03:18 EST
==
Summary:Support for RVDS 4.1: ARM C/C++ and ASM compilers.
Description:
What works:
* The ASM compilation works just fine, except for FLAGS, we don’t know how
to use that so we just hardcoded the flags in the CMakeASM-RVDSInformation.cmake
file.
* The C and C++ compilation and static libraries generation work with one
caveat: we hardcoded “armar” in CMAKE_C_CREATE_STATIC_LIBRARY and
CMAKE_CXX_CREATE_STATIC_LIBRARY because setting CMAKE_AR doesn’t work for us.
What doesn’t work:
* We cannot use armcc for linking because we need to use a scatter file for
memory and this requires using armlink. Unfortunately, setting
CMAKE_CXX_LINK_EXECUTABLE doesn’t work for us because:
1) we did not find how to set the arguments of armlink correctly
2) armlink requires an object file as first input, giving only static libraries
doesn’t work
So, as a workaround, we install our static libraries in a dedicated
“archive” folder and we use a build script for the final linking step thanks
to a custom target:
file(GLOB archives ${CMAKE_BINARY_DIR}/archive/*.a)
add_custom_target(fw ${CMAKE_SOURCE_DIR}/../cmake/link.sh ${CMAKE_BINARY_DIR}
${CMAKE_SOURCE_DIR}
WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/archive)
I also attach our build script for reference.
This works for us but obviously is far from optimal. So we are contributing this
in the hope that it is useful to you and also that it can be improved. If some
CMake developer can help us improve this, we would be happy to test and help of
course.
Additional Information:
Contribution of MARVELL Switzerland SARL
==
Issue History
Date ModifiedUsername FieldChange
==
2011-12-09 03:18 Abdelrazak YounesNew Issue
2011-12-09 03:18 Abdelrazak YounesFile Added: cmake-RVDS.zip
==
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012616]: ReRunCMake.make overriden by subprojects
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=12616 == Reported By:ngladitz Assigned To: == Project:CMake Issue ID: 12616 Category: CMake Reproducibility:always Severity: major Priority: normal Status: new == Date Submitted: 2011-12-09 07:12 EST Last Modified: 2011-12-09 07:12 EST == Summary:ReRunCMake.make overriden by subprojects Description: First of I'm guessing this issue is related to http://www.cmake.org/Bug/view.php?id=10151. Having a similar setup: src/ - CMakeLists.txt - A/ - CMakeLists.txt Where A/CMakeLists.txt contains a call to project() and CMakeLists.txt uses add_subdirectory(A). The generated ReRunCMake.make lists only A/CMakeLists.txt as a dependency. Without the call to project() in A/CMakeLists.txt ReRunCMake.make correctly lists dependencies for both CMakeLists.txts (plus a lot of other cmake files). == Issue History Date ModifiedUsername FieldChange == 2011-12-09 07:12 ngladitz New Issue == -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] target_include_directories branch in stage
Maybe this is a bit late, but wouldn't it be much simpler to get this feature with a namespace inspired approach: http://public.kitware.com/Bug/view.php?id=11793 All within a namespace has the same scope as an add_subdirectory added target. This way we get more than the 'target_include_directories' without adding multiple target_* functions (which maybe will come). Peter -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] Cpack Installing extra files depending on generator type
2011/12/9 vivek goel goelvivek2...@gmail.com: I want to generate two package type . So I am using following syntax in my CMakeLists.txt SET(CPACK_GENERATOR TGZ;RPM) Now problem is that I want to install some extra files in Generator RPM. And I want to set different Install RPM prefix. How can I do that ? When you want to do CPack generator specific things you'd better off using CPACK_PROJECT_CONFIG_FILE http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Overall_usage_.28common_to_all_generators.29 this file is loaded **at CPack time** before the CPack generator runs. in this file you can do something like; if(CPACK_GENERATOR MATCHES TGZ) set(CPACK_ARCHIVE_COMPONENT_INSTALL OFF) endif(CPACK_GENERATOR MATCHES ZIP) if(CPACK_GENERATOR MATCHES RPM) set(CPACK_RPM_COMPONENT_INSTALL ON) # change the default install prefix set(CPACK_PACKAGING_INSTALL_PREFIX /opt) endif(CPACK_GENERATOR MATCHES RPM) The problem with the install extra file for RPM is that install command are prepared at **CMake time** and launched at **CPack time** so may be you can use the install(SCRIPT ...) signature with a cmake script which will check (at CPack time) the value of CPACK_GENERATOR in the same way CPACK_PROJECT_CONFIG_FILE does. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Eclipse and CMake...
2011/12/9 Clifford Yapp cliffy...@gmail.com: I decided to take a stab at using the Eclipse Unix Makefile generator with my project - on import, I get the following error: Error processing changed links in project description file. No file system is defined for scheme: virtual I'm not really sure what this means or what issue it's indicating - has anyone else seen this? Which CMake version? Which version of Eclipse are you using? Helios, Indigo? Alex will answer that but I think virtual folder are used in linked resource which implies at least Helios I think. Alex also tries to detect the eclipse version in order to use ot nor use some eclipse features, this should only be in master I think. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Support for RVDS 4.1: ARM C/C++ and ASM compilers.
Hi Alex,
Thanks for the quick reply.
I am using Outlook so I cannot reply inline easily, please bear with me. I will
prefix your answer with '#'
-Original Message-
From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
Sent: Thursday, December 08, 2011 9:24 PM
To: cmake@cmake.org
Cc: Abdelrazak Younes
Subject: Re: [CMake] Support for RVDS 4.1: ARM C/C++ and ASM compilers.
On Thursday 08 December 2011, Abdelrazak Younes wrote:
Hello,
We (MARVELL Switzerland) have created some CMake support files in order to
use RVDS 4.1 ARM C/C++ and ASM compilers.
# Cool !
# I mean, this is really cool ! :-)
I am very glad that you like it :-)
# Can you please create a ticket for this on
# http://public.kitware.com/Bug/my_view_page.php
#, basically with the content of this email ?
# This way it is ensured that it won't get lost or forgotten.
Done:
http://public.kitware.com/Bug/view.php?id=12614
# Setting all the CMAKE_(C|CXX)_CREATE_* and ARCHIVE variables in the toolchain
# file should not be necessary.
#
# It should be enough to only set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER.
# Then cmake tries to compile a small executable with it, and tries to detect
# the compiler, see Modules/CMakeCCompilerID.c.in.
# Probably there is a macro builtin into this compiler to detect that it is the
# RVDS compiler ?
Yes, see here:
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0041c/Babbacdb.html
So I guess I can either use __arm or __ARMCC_VERSION
# The cmake compiler ID could then be named RVDS.
#
# Then cmake executes Modules/CMakeFindBinUtils.cmake.
# If the compiler ID has been determined successfully, you can change this file
# so that if the compiler ID is RVDS, it looks for armar instead of ar.
#
# Then, once it has detected this compiler id, it can load
# Modules/Compiler/RVDS-C.cmake and RVDS-CXX.cmake. There you can put also the
# variables for linking etc.
OK, so shall I make a local copy of Modules/CMakeCCompilerID.c.in and modify
that? I mean, would this copy take precedence if I add the local Module path
like this:
set(CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/../cmake/Modules
${CMAKE_MODULE_PATH})
# Thanks a lot :-)
And thanks to you for your support.
Cheers,
Abdel.
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Support for RVDS 4.1: ARM C/C++ and ASM compilers.
-Original Message-
From: Abdelrazak Younes
# The cmake compiler ID could then be named RVDS.
#
# Then cmake executes Modules/CMakeFindBinUtils.cmake.
# If the compiler ID has been determined successfully, you can change this
file
# so that if the compiler ID is RVDS, it looks for armar instead of ar.
#
# Then, once it has detected this compiler id, it can load
# Modules/Compiler/RVDS-C.cmake and RVDS-CXX.cmake. There you can put also
the
# variables for linking etc.
OK, so shall I make a local copy of Modules/CMakeCCompilerID.c.in and modify
that? I mean, would this copy take precedence if I add the local Module
path like this:
set(CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/../cmake/Modules
${CMAKE_MODULE_PATH})
It doesn't work with the local copy unfortunately... but it works with the
modified installed version in /usr/share/cmake-2.8/Modules:
cmake ../src -Drvds=1 -Dfirmware=$2
-DCMAKE_TOOLCHAIN_FILE=../cmake/LinuxRvdsToolchain.cmake
-- The C compiler identification is RVDS
-- The CXX compiler identification is unknown
-- Check for working C compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc
-- Check for working C compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc
-- Check for working CXX compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
Compiling for ARM platform
-- The ASM-RVDS compiler identification is unknown
-- Found assembler: /opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armasm
-- Configuring done
-- Generating done
-- Build files have been written to:
I have used the __ARMCC_VERSION macro (see patch below).
So now I will try to remove CMAKE_(C|CXX)_CREATE_* and ARCHIVE variables and
modify Modules/CMakeFindBinUtils.cmake; I hope I can use a local copy for this
file.
Cheers,
Abdel.
--- /usr/share/cmake-2.8/Modules/CMakeCCompilerId.c.in.original 2011-07-08
14:21:44.0 +0200
+++ /usr/share/cmake-2.8/Modules/CMakeCCompilerId.c.in 2011-12-09
09:57:49.565830358 +0100
@@ -85,6 +85,9 @@
#elif defined(__hpux) || defined(__hpua)
# define COMPILER_ID HP
+#elif defined(__ARMCC_VERSION)
+# define COMPILER_ID RVDS
+
#else /* unknown compiler */
# define COMPILER_ID
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Support for RVDS 4.1: ARM C/C++ and ASM compilers.
-Original Message-
From: Abdelrazak Younes
So now I will try to remove CMAKE_(C|CXX)_CREATE_* and ARCHIVE variables
and modify Modules/CMakeFindBinUtils.cmake; I hope I can use a local copy
for this file.
It seems I can use a local copy of it as I got a warning about that (see
below). So I modified my local copy with the diff below but it doesn't work,
/usr/bin/ar is still used. One additional question: armar is apparently doing
the job of ar and ranlib so I don't want ranlib to be used afterwards so please
tell me how to avoid that.
Cheers,
Abdel.
The diff:
diff -u /usr/share/cmake-2.8/Modules/CMakeFindBinUtils.cmake
../cmake/Modules/CMakeFindBinUtils.cmake
--- /usr/share/cmake-2.8/Modules/CMakeFindBinUtils.cmake2011-07-08
14:21:44.0 +0200
+++ ../cmake/Modules/CMakeFindBinUtils.cmake2011-12-09 10:32:04.049725221
+0100
@@ -38,8 +38,13 @@
MARK_AS_ADVANCED(CMAKE_LINKER)
+ELSEIF(${CMAKE_CXX_COMPILER_ID} MATCHES RVDS
+ OR ${CMAKE_C_COMPILER_ID} MATCHES RVDS)
+
+ FIND_PROGRAM(CMAKE_AR NAMES armar HINTS ${_CMAKE_TOOLCHAIN_LOCATION})
+
# in all other cases search for ar, ranlib, etc.
ELSE(${CMAKE_CXX_COMPILER_ID} MATCHES MSVC
ELSE(${CMAKE_CXX_COMPILER_ID} MATCHES MSVC
OR ${CMAKE_C_COMPILER_ID} MATCHES MSVC
OR ${CMAKE_GENERATOR} MATCHES Visual Studio)
The cmake call with the warning:
cmake ../src -Drvds=1 -Dfirmware=$2
-DCMAKE_TOOLCHAIN_FILE=../cmake/LinuxRvdsToolchain.cmake
-- The C compiler identification is RVDS
-- The CXX compiler identification is unknown
-- Check for working C compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc
-- Check for working C compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc
-- Check for working CXX compiler:
/opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armcc -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
Compiling for ARM platform
-- The ASM-RVDS compiler identification is unknown
CMake Warning (dev) at
/usr/share/cmake-2.8/Modules/CMakeDetermineASMCompiler.cmake:156 (INCLUDE):
File /usr/share/cmake-2.8/Modules/CMakeDetermineASMCompiler.cmake includes
/src/../cmake/Modules/CMakeFindBinUtils.cmake
(found via CMAKE_MODULE_PATH) which shadows
/usr/share/cmake-2.8/Modules/CMakeFindBinUtils.cmake. This may cause
errors later on .
Policy CMP0017 is not set: Prefer files from the CMake module directory
when including from there. Run cmake --help-policy CMP0017 for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.
Call Stack (most recent call first):
/cmake/Modules/CMakeDetermineASM-RVDSCompiler.cmake:3 (INCLUDE)
/CMakeLists.txt:5 (enable_language)
This warning is for project developers. Use -Wno-dev to suppress it.
-- Found assembler: /opt/ARM/RVCT/Programs/4.1/462/linux-pentium/armasm
-- Configuring done
-- Generating done
-- Build files have been written to: xxx
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Cpack Installing extra files depending on generator type
Hi, Can you please give an example for install(SCRIPT ...) So I can install a init-script with rpm ? On 12/9/11, Eric Noulard eric.noul...@gmail.com wrote: 2011/12/9 vivek goel goelvivek2...@gmail.com: I want to generate two package type . So I am using following syntax in my CMakeLists.txt SET(CPACK_GENERATOR TGZ;RPM) Now problem is that I want to install some extra files in Generator RPM. And I want to set different Install RPM prefix. How can I do that ? When you want to do CPack generator specific things you'd better off using CPACK_PROJECT_CONFIG_FILE http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#Overall_usage_.28common_to_all_generators.29 this file is loaded **at CPack time** before the CPack generator runs. in this file you can do something like; if(CPACK_GENERATOR MATCHES TGZ) set(CPACK_ARCHIVE_COMPONENT_INSTALL OFF) endif(CPACK_GENERATOR MATCHES ZIP) if(CPACK_GENERATOR MATCHES RPM) set(CPACK_RPM_COMPONENT_INSTALL ON) # change the default install prefix set(CPACK_PACKAGING_INSTALL_PREFIX /opt) endif(CPACK_GENERATOR MATCHES RPM) The problem with the install extra file for RPM is that install command are prepared at **CMake time** and launched at **CPack time** so may be you can use the install(SCRIPT ...) signature with a cmake script which will check (at CPack time) the value of CPACK_GENERATOR in the same way CPACK_PROJECT_CONFIG_FILE does. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- regards Vivek Goel -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] How to detect set dependences when build-time(not when cmake)?
On Friday 09 December 2011, 持重 金 wrote: Hello every one. Recently, I try to rewrite a large project's building system by using cmake. I meet a difficult point, how to detect set dependences when build-time. I have lot of this requirement, and currently I solve it with some terrible ways. I want some refined ways. For example: Using precompiled header file. Cmake do not support pch directly and can not detect a header's dependences as a source file. I can't set pch's dependences when cmake-time because it's changed frequently and it's dependences is tree structures. If your PCH changes frequently, then you probably aren't using it correctly. The pre-compiled headers should include only stable headers that do not change often (for instance: system and 3rd party library headers), because pre- compiling the PCH file consumes a lot of time and disk space. Regards, Pedro -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Eclipse and CMake...
On Fri, Dec 9, 2011 at 3:50 AM, Eric Noulard eric.noul...@gmail.com wrote: 2011/12/9 Clifford Yapp cliffy...@gmail.com: I decided to take a stab at using the Eclipse Unix Makefile generator with my project - on import, I get the following error: Error processing changed links in project description file. No file system is defined for scheme: virtual I'm not really sure what this means or what issue it's indicating - has anyone else seen this? Which CMake version? Which version of Eclipse are you using? Helios, Indigo? Alex will answer that but I think virtual folder are used in linked resource which implies at least Helios I think. Alex also tries to detect the eclipse version in order to use ot nor use some eclipse features, this should only be in master I think. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Please try with CMake 2.8.7-rc1, released yesterday. There have been several Eclipse related changes since 2.8.6. Then report back whether it is still a problem or not. Thx, David -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] How to preserve directory structure within Visual Studio
2011/12/9 David Cole david.c...@kitware.com:
2011/12/8 Mateusz Łoskot mate...@loskot.net:
2011/12/8 David Cole david.c...@kitware.com:
2011/12/8 Mateusz Łoskot mate...@loskot.net:
On 8 December 2011 21:45, David Cole david.c...@kitware.com wrote:
No, the FOLDER property is only a mechanism for grouping and
organizing *targets*, it is not a source file property...
Is it the source_group still the recommended way of grouping?
Yes, the source_group command should be able to handle this. Try it
with \\ and / separators, I can't remember which character is used
to split on for sub-folders within the project file. (Maybe either
works...?)
The issue I have always suffered is that search_group (or related parties)
ignores source files (any specified) if they are not used in the targets.
Here is illustration from one of my C++ headers-only pet projects:
1) I need to collect and structure all headers I want to have listed in
Solution Explorer in Visual Studio:
https://github.com/mloskot/boost-gil-workshop/blob/master/CMakeLists.txt
file(GLOB GIL_HPP ${GIL_DIR}/*.hpp)
file(GLOB GIL_EXT_IO_HPP ${GIL_EXT_IO_DIR}/*.hpp)
file(GLOB GIL_EXT_IO_DETAIL_HPP ${GIL_EXT_IO_DIR}/detail/*.hpp)
# Make single list with all headers for convenience in 2)
if(MSVC)
list(APPEND GIL_ALL_HPP ${GIL_HPP})
list(APPEND GIL_ALL_HPP ${GIL_EXT_IO_HPP})
list(APPEND GIL_ALL_HPP ${GIL_EXT_IO_DETAIL_HPP})
endif()
2) Indicate the headers are used source files:
add_executable(gil_pnm_test gil_pnm_test.cpp ${GIL_ALL_HPP})
3) Assign headers to groups:
https://github.com/mloskot/boost-gil-workshop/blob/master/test/CMakeLists.txt
source_group(Header Files\\gil FILES ${GIL_HPP})
source_group(Header Files\\gil\\extension\\io_new FILES ${GIL_EXT_IO_HPP})
source_group(Header Files\\gil\\extension\\io_new\\detail FILES
${GIL_EXT_IO_DETAIL_HPP})
Has anything changed to make the procedure easier?
Not that I'm aware of -- this looks quite reasonable to me.
I'm glad to have it confirmed. Thanks.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] New type of cache variable: lists
On Thu, Dec 8, 2011 at 7:59 PM, David Cole david.c...@kitware.com wrote:
Well, nearly
You'll have to double-quote the ${documentation} inside the function
in case it is the empty string...
Or if it has spaces in it, right? Any time I have a string with spaces in
it, or that could have spaces in it, I use quotes so the value of the
string doesn't get interpreted as multiple parameters (like a list)
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] [CTest] CTest -S script cannot be found on Windows network drive
I have two buildservers: a Linux box and a Windows box. I now have a buildscript that does a svn checkout in the homedir of the Linux build user. This directory is shared read/write using Samba. The Windows builduser (same credentials, same uid) is able to reach the files through a mingw mount. On the Windows box there is a ssh server, so I can run commands from the Linux box. When running ssh windowsbuilduser@windowsip 'ctest -S /path/to/scriptfile' I get the following error: CMake Error: Cannot find file: /path/to/scriptfile (actual pathnames are used of course) When running ssh windowsbuilduser@windowsip 'ls /path/to/scriptfile' I do see that the scriptfile is there. My guess is that ctest starts a new shell, which cannot find the script. Is that a correct assumption? Does anybody know how to resolve this? Any help or pointers would be very much appreciated. With kind regards, Micha Hergarden -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] New type of cache variable: lists
On Fri, Dec 9, 2011 at 9:59 AM, Robert Dailey rcdai...@gmail.com wrote:
On Thu, Dec 8, 2011 at 7:59 PM, David Cole david.c...@kitware.com wrote:
Well, nearly
You'll have to double-quote the ${documentation} inside the function
in case it is the empty string...
Or if it has spaces in it, right? Any time I have a string with spaces in
it, or that could have spaces in it, I use quotes so the value of the string
doesn't get interpreted as multiple parameters (like a list)
No, in this case, it's just in case it's empty because the CACHE form
of set expects to get the type and the docstring following the CACHE
keyword. If ${documentation} evaluates to the empty string, then the
set command only sees 4 arguments and yields an error.
The example CMakeLists file did have spaces in the documentation
strings, but they worked just fine.
In the case of set, the 5th argument can be ${documentation} or
${documentation} as long as it's non-empty, and the results are
equivalent. But if it's empty, the double-quoted form must be used.
CMake's parser is the thing that splits at space boundaries when
evaluating what to send into the set command. But since the actual
literal code ${documentation} does not have spaces in it, it's full
value (including any spaces in the value) get sent into the set
command internally as arg 5.
Understanding when you have to quote things is simply one of the
hardest things to grok when dealing with CMake language code. Stick
with it, though. It's easier than learning git. It only took me about
2 years of practice before I think something snapped into place in my
brain...
David
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] [CTest] CTest -S script cannot be found on Windows network drive
On Fri, Dec 9, 2011 at 9:30 AM, m.hergarden m.hergar...@euphoria-it.nl wrote: I have two buildservers: a Linux box and a Windows box. I now have a buildscript that does a svn checkout in the homedir of the Linux build user. This directory is shared read/write using Samba. The Windows builduser (same credentials, same uid) is able to reach the files through a mingw mount. On the Windows box there is a ssh server, so I can run commands from the Linux box. When running ssh windowsbuilduser@windowsip 'ctest -S /path/to/scriptfile' I get the following error: CMake Error: Cannot find file: /path/to/scriptfile (actual pathnames are used of course) When running ssh windowsbuilduser@windowsip 'ls /path/to/scriptfile' I do see that the scriptfile is there. My guess is that ctest starts a new shell, which cannot find the script. Is that a correct assumption? Does anybody know how to resolve this? Any help or pointers would be very much appreciated. With kind regards, Micha Hergarden -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake What sshd are you running on the Windows box? Can you map the network path to a Windows drive letter (say N: for network), and use the N:/path/to/script file form instead? -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Eclipse and CMake...
Let's try replying to the list this time... Eclipse 3.7.1 (Indigo) Eclipse succeeded in importing. I'm not sure how to do a C/C++ project build with Eclipse (or that my build of Indigo actually added everything it needed to) but it looks like the CMake project import part of the equation succeeded. Test done using CMake 2.8.7 release candidate. CY On Fri, Dec 9, 2011 at 10:01 AM, David Cole david.c...@kitware.com wrote: On Fri, Dec 9, 2011 at 9:39 AM, Clifford Yapp cliffy...@gmail.com wrote: On Fri, Dec 9, 2011 at 6:41 AM, David Cole david.c...@kitware.com wrote: Please try with CMake 2.8.7-rc1, released yesterday. There have been several Eclipse related changes since 2.8.6. Then report back whether it is still a problem or not. Still seeing the same error (repeated multiple times, now). Should I upgrade my Eclipse to something newer than and try again? I wasn't sure if CDT4 corresponded to some particular version of Eclipse or just identified a component - I'm not familiar with their versioning scheme. Cheers, Cliff Honestly, I'm not familiar with their versioning scheme either... I just know that Alex has been working hard at making Eclipse support work well with their current version. I don't use Eclipse much for C++ work. In fact, I haven't even installed it on the laptop that I got back in July yet... Maybe I should give it a whirl again. Sorry, David -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] iOS Archiving (again)
Hi, A small step in the iOS release archiving problem. Note, this is all Xcode 4.0.2, Xcode 4.2 (the LLVM GCC compiler) doesn't specify the error (more than 1), so is basically unworkable. At least the old GCC 4.2 compiler tells you what is going on. For archiving to work on iOS (OSX don't know) you have to set skip install to yes for all static libs you might be using, so they don't end up in the final product: http://developer.apple.com/library/ios/#technotes/tn2215/_index.html So, in the iOSNavApp example from the CMake test suite, which uses a library named Functions I set this skip install property to yes in the Functions target, and to no for the application target itself. But then, during the link phase of a release archive step, the compiler can not find the library in /path/to/build/Release-iphoneos (libFunctions.a not found). Xcode doesn't copy the lib to this destination directory, could be related to: http://www.cmake.org/Bug/bug_relationship_graph.php?bug_id=12506graph=dependency My solution now is to split the process in two phases: 1) Set skip install to no for both targets (library and application) and do a (release) archive. This will result in a corrupt ipa but at least the lib is built and copied. 2) Set skip install to yes for the lib and do an archive again. Now it will create a proper ipa. Hope this helps a bit. Mainly in battling http://developer.apple.com/library/ios/#technotes/tn2215/_index.html Thanks, Daniel -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] [CTest] CTest -S script cannot be found on Windows network drive
On 12/09/2011 04:30 PM, David Cole wrote: On Fri, Dec 9, 2011 at 9:30 AM, m.hergardenm.hergar...@euphoria-it.nl wrote: I have two buildservers: a Linux box and a Windows box. I now have a buildscript that does a svn checkout in the homedir of the Linux build user. This directory is shared read/write using Samba. The Windows builduser (same credentials, same uid) is able to reach the files through a mingw mount. On the Windows box there is a ssh server, so I can run commands from the Linux box. When running ssh windowsbuilduser@windowsip 'ctest -S /path/to/scriptfile' I get the following error: CMake Error: Cannot find file: /path/to/scriptfile (actual pathnames are used of course) When running ssh windowsbuilduser@windowsip 'ls /path/to/scriptfile' I do see that the scriptfile is there. My guess is that ctest starts a new shell, which cannot find the script. Is that a correct assumption? Does anybody know how to resolve this? Any help or pointers would be very much appreciated. With kind regards, Micha Hergarden -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake What sshd are you running on the Windows box? Can you map the network path to a Windows drive letter (say N: for network), and use the N:/path/to/script file form instead? Thank you for the quick reply. I am using FreeSSHd. Using the 'net use' command I can map the network drive to n: When calling ctest using your suggested path locally on the windows box it does seem to work OK. Running it through the ssh session still yields the same error. -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Eclipse and CMake...
On Friday 09 December 2011, David Cole wrote: On Fri, Dec 9, 2011 at 3:50 AM, Eric Noulard eric.noul...@gmail.com wrote: 2011/12/9 Clifford Yapp cliffy...@gmail.com: I decided to take a stab at using the Eclipse Unix Makefile generator with my project - on import, I get the following error: Error processing changed links in project description file. No file system is defined for scheme: virtual I'm not really sure what this means or what issue it's indicating - has anyone else seen this? Which CMake version? Which version of Eclipse are you using? Helios, Indigo? Alex will answer that but I think virtual folder are used in linked resource which implies at least Helios I think. Alex also tries to detect the eclipse version in order to use ot nor use some eclipse features, this should only be in master I think. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- Please try with CMake 2.8.7-rc1, released yesterday. There have been several Eclipse related changes since 2.8.6. Then report back whether it is still a problem or not. Thx, David Yes, please try 2.8.7rc1. If you still have this problem, cmake probably didn't find Eclipse and so could not detect the version. For this case, you can now set CMAKE_ECLIPSE_VERSION to the version you have, if you use cmake-gui to do this, you get a combobox to chose from. Alex -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] How to preserve directory structure within Visual Studio
On Thu, Dec 8, 2011 at 1:45 PM, David Cole david.c...@kitware.com wrote:
No, the FOLDER property is only a mechanism for grouping and
organizing *targets*, it is not a source file property...
uhh... FOLDER works on projects in a solution, but it also works on
source files within a project.
SET_TARGET_PROPERTIES(bag.image PROPERTIES
FOLDER Image Library
)
SET_SOURCE_FILES_PROPERTIES( ${OPTION_SOURCE} PROPERTIES
FOLDER Source Files\\Option Library )
On Thu, Dec 8, 2011 at 4:19 PM, J Decker d3c...@gmail.com wrote:
set_property(GLOBAL PROPERTY USE_FOLDERS On)
SET_SOURCE_FILES_PROPERTIES( ${YOUR_SOURCES} PROPERTIES
FOLDER project folder name here )
On Thu, Dec 8, 2011 at 12:32 PM, Stephen Torri stephen.to...@gmail.com
wrote:
CMake version: 2.8
IDE: Visual Studio 2008
For the source and header files I would like to preserve the directory
structure within the Visual Studio Header Files and Source Files
folders. Without it should there occur two files with the same name
but in different directories only one is shown. For example:
SET ( HEADERS
base_units/time.hpp
si/time.hpp )
add_custom_target ( UnitHeaders SOURCES ${HEADERS} )
If UnitHeaders is included within the parent CMakeLists.txt file a
Project called UnitHeaders is included within the Visual Studio
Solution. What you will see undert the Header Files for UnitHeaders
is only one header file. I would like to see the following within
Visual Studio under Header Files:
UnitHeaders
|
|-- Header Files - base - time.hpp
- si - time.hpp
A search on Google has shown two similar questions asked in the past
but no answer was posted in reply to them.
Stephen
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] How to preserve directory structure within Visual Studio
On Fri, Dec 9, 2011 at 11:41 AM, J Decker d3c...@gmail.com wrote:
On Thu, Dec 8, 2011 at 1:45 PM, David Cole david.c...@kitware.com wrote:
No, the FOLDER property is only a mechanism for grouping and
organizing *targets*, it is not a source file property...
uhh... FOLDER works on projects in a solution, but it also works on
source files within a project.
SET_TARGET_PROPERTIES(bag.image PROPERTIES
FOLDER Image Library
)
SET_SOURCE_FILES_PROPERTIES( ${OPTION_SOURCE} PROPERTIES
FOLDER Source Files\\Option Library )
On Thu, Dec 8, 2011 at 4:19 PM, J Decker d3c...@gmail.com wrote:
set_property(GLOBAL PROPERTY USE_FOLDERS On)
SET_SOURCE_FILES_PROPERTIES( ${YOUR_SOURCES} PROPERTIES
FOLDER project folder name here )
On Thu, Dec 8, 2011 at 12:32 PM, Stephen Torri stephen.to...@gmail.com
wrote:
CMake version: 2.8
IDE: Visual Studio 2008
For the source and header files I would like to preserve the directory
structure within the Visual Studio Header Files and Source Files
folders. Without it should there occur two files with the same name
but in different directories only one is shown. For example:
SET ( HEADERS
base_units/time.hpp
si/time.hpp )
add_custom_target ( UnitHeaders SOURCES ${HEADERS} )
If UnitHeaders is included within the parent CMakeLists.txt file a
Project called UnitHeaders is included within the Visual Studio
Solution. What you will see undert the Header Files for UnitHeaders
is only one header file. I would like to see the following within
Visual Studio under Header Files:
UnitHeaders
|
|-- Header Files - base - time.hpp
- si - time.hpp
A search on Google has shown two similar questions asked in the past
but no answer was posted in reply to them.
Stephen
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Well, you can set any properties you want on any entity you want. They
are just key/value pairs that are stored with the entity.
But, what I'm saying is: CMake does not pay attention to any FOLDER
property you put on your source files. If I grep the CMake source tree
for FOLDER the only uses I see of it are related to targets, not to
source files.
So. If you're saying that this has some sort of organizational effect
all by itself on your source files in your generated Visual Studio
projects, then I'd like to know what version of CMake you're using.
Sounds like 2.8.magic to me. :-)
Are you sure you don't also have proper source_group calls in your
CMakeLists.txt files?
David
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Visual Studio links again even if no changes were made
Hello,
I am using CMake to build a shared lib on Visual Studio 2008. The problem
here is that every time I try to debug the executable that uses that
library, the visual studio links its objects again, even if no changes were
made.
Do someone know what could be going on?
The CMakeLists for this lib is:
cmake_minimum_required(VERSION 2.8)
project(apwinnt)
set(APWINNT_SOURCES
${TOTVS_INTERFACETST_PATH}/apwinnt.cpp
except.cpp
${TOTVS_INTERFACETST_PATH}/interfacetst.cpp
${TOTVS_INTERFACETST_PATH}/serverunittest.cpp
)
set(APWINNT_HEADERS
except.hpp
${TOTVS_INTERFACETST_PATH}/serverunittest.h
)
set(APWINNT_LIBS
wsock32.lib
odbc32.lib
odbccp32.lib
Version.lib
psapi.lib
Dbghelp.lib
tmq
lib_jpeg
advpl
web
lib
)
set(TOTVS_INCLUDES_PATHS
${TOTVS_LIB_COMM_PATH}
${TOTVS_LIB_BASE_PATH}
${TOTVS_OPENSSL_PATH}/inc32
${TOTVS_LIB_GZIP_PATH}
${TOTVS_WEB_PATH}
${TOTVS_INTERFACE_PATH}
${TOTVS_ADVPL_PATH}
${TOTVS_ADS_INCLUDE_PATH}
${TOTVS_LIB_GETSYS_PATH}
)
set(DEFINITIONS /DAPWINNT_EXPORTS /DBUILD_MAKEDLL)
set(DEFINITIONS_RELEASE /D_USRDLL /DCLICONN_EXPORTS)
set(DEFINITIONS_DEBUG )
#os ignore são pra ignorar warnings específicos que são gerados pelo
libXML.
set(LINKER_FLAGS /ignore:4217 /ignore:4049)
set(LINKER_FLAGS_DEBUG /LIBPATH:${TOTVS_OPENSSL_PATH}/debug
/LIBPATH:${TOTVS_LIB_ICONV_PATH}/debug /LIBPATH:${TOTVS_XML_PATH}/debug
/LIBPATH:${TOTVS_XMLSEC_PATH}/debug Dbghelp.lib)
set(LINKER_FLAGS_RELEASE /INCREMENTAL /INCLUDE:_SmartHeap_malloc
/LIBPATH:${TOTVS_OPENSSL_PATH}/release
/LIBPATH:${TOTVS_LIB_ICONV_PATH}/release /LIBPATH:${TOTVS_XML_PATH}/release
/LIBPATH:${TOTVS_XMLSEC_PATH}/release
${TOTVS_SMARTHEAP_PATH}/msvc/shdsmpmt.lib)
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} ${DEFINITIONS})
set(CMAKE_CXX_FLAGS_DEBUG ${CMAKE_CXX_FLAGS_DEBUG} ${DEFINITIONS_DEBUG})
set(CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_RELEASE}
${DEFINITIONS_RELEASE})
set(CMAKE_SHARED_LINKER_FLAGS ${CMAKE_SHARED_LINKER_FLAGS}
${LINKER_FLAGS})
set(CMAKE_SHARED_LINKER_FLAGS_DEBUG ${CMAKE_SHARED_LINKER_FLAGS_DEBUG}
${LINKER_FLAGS_DEBUG} ${LIBRARIES_DEBUG})
set(CMAKE_SHARED_LINKER_FLAGS_RELEASE ${CMAKE_SHARED_LINKER_FLAGS_RELEASE}
${LINKER_FLAGS_RELEASE})
include_directories(
${TOTVS_INCLUDES_PATHS}
)
add_library(apwinnt SHARED ${APWINNT_SOURCES} ${APWINNT_HEADERS})
target_link_libraries(apwinnt ${APWINNT_LIBS})
The Visual Studios output is:
1-- Build started: Project: apwinnt, Configuration: Debug Win32 --
1Linking...
1LINK : C:\advtec9\trunk\bin_sem_unittest\apwinnt\Debug\apwinnt.dll not
found or not built by the last incremental link; performing full link
1 Creating library
C:\advtec9\trunk\bin_sem_unittest\apwinnt\Debug\apwinnt.lib and object
C:\advtec9\trunk\bin_sem_unittest\apwinnt\Debug\apwinnt.exp
1Embedding manifest...
1Build log was saved at
file://c:\advtec9\trunk\bin_sem_unittest\apwinnt\apwinnt.dir\Debug\BuildLog
.htm
1apwinnt - 0 error(s), 0 warning(s)
== Build: 1 succeeded, 0 failed, 21 up-to-date, 0 skipped ==
Thanks!
Renan Greinert
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] New type of cache variable: lists
BTW thank you for the choice() function. I have looked it over and it looks
perfect. I'm going to actively use this in our project. It would be a
perfect addition to the language as well.
As far as knowing when to use quotations is concerned, according to the
logic you have described, is that consistent behavior? In other words,
across all CMake commands, regardless of what the contents of a string is
(whitespace and whatnot), it is safe to pass it in without quotes unless it
may possibly be empty, in which case I'd use ${var}.
I agree that knowing when to use quotes can be confusing, but once you
understand a couple of rules it is pretty easy. Maybe you can give an
example of a more ambiguous case :)
Thanks again David.
-
Robert Dailey
On Fri, Dec 9, 2011 at 9:27 AM, David Cole david.c...@kitware.com wrote:
On Fri, Dec 9, 2011 at 9:59 AM, Robert Dailey rcdai...@gmail.com wrote:
On Thu, Dec 8, 2011 at 7:59 PM, David Cole david.c...@kitware.com
wrote:
Well, nearly
You'll have to double-quote the ${documentation} inside the function
in case it is the empty string...
Or if it has spaces in it, right? Any time I have a string with spaces in
it, or that could have spaces in it, I use quotes so the value of the
string
doesn't get interpreted as multiple parameters (like a list)
No, in this case, it's just in case it's empty because the CACHE form
of set expects to get the type and the docstring following the CACHE
keyword. If ${documentation} evaluates to the empty string, then the
set command only sees 4 arguments and yields an error.
The example CMakeLists file did have spaces in the documentation
strings, but they worked just fine.
In the case of set, the 5th argument can be ${documentation} or
${documentation} as long as it's non-empty, and the results are
equivalent. But if it's empty, the double-quoted form must be used.
CMake's parser is the thing that splits at space boundaries when
evaluating what to send into the set command. But since the actual
literal code ${documentation} does not have spaces in it, it's full
value (including any spaces in the value) get sent into the set
command internally as arg 5.
Understanding when you have to quote things is simply one of the
hardest things to grok when dealing with CMake language code. Stick
with it, though. It's easier than learning git. It only took me about
2 years of practice before I think something snapped into place in my
brain...
David
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] custom target output in Visual Studio
I run a couple of commands in a custom target in Visual Studio 2008. However, most of the output for these commands is not presented in the Output Window in Visual Studio when I execute a build on the custom target. How can I setup my custom target and/or commands inside the target to make sure that all output from the commands is presented in the Visual Studio Output Window? Thanks in advance. - Robert Dailey -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Problem Compiling on Solaris 10 x86
Hey guys, I'm trying to build cmake on Solaris 10 x86 and am getting the following error: [ 94%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesMainForm.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesPathWidget.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesStringWidget.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o [ 96%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o Linking CXX executable ../bin/ccmake Undefined first referenced symbol in file wattr_on CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o wattr_off CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o ld: fatal: Symbol referencing errors. No output written to ../bin/ccmake collect2: ld returned 1 exit status make[2]: *** [bin/ccmake] Error 1 make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2 make: *** [all] Error 2 Below is with VERBOSE=1 [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o cd /build/packages/cmake/cmake-2.8.6/Source /build/system/bin/g++ -DCURL_STATICLIB -DLIBARCHIVE_STATIC -DCMAKE_BUILD_WITH_CMAKE -I/build/packages/cmake/cmake-2.8.6/Utilities -I/build/packages/cmake/cmake-2.8.6/Source -I/build/packages/cmake/cmake-2.8.6/Utilities/cmcompress -I/build/packages/cmake/cmake-2.8.6/Source/CTest -I/build/packages/cmake/cmake-2.8.6/Source/CursesDialog/form-o CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o -c /build/packages/cmake/cmake-2.8.6/Source/CursesDialog/cmCursesWidget.cxx /build/packages/cmake/cmake-2.8.6/Bootstrap.cmk/cmake -E cmake_progress_report /build/packages/cmake/cmake-2.8.6/CMakeFiles 41 [ 96%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o cd /build/packages/cmake/cmake-2.8.6/Source /build/system/bin/g++ -DCURL_STATICLIB -DLIBARCHIVE_STATIC -DCMAKE_BUILD_WITH_CMAKE -I/build/packages/cmake/cmake-2.8.6/Utilities -I/build/packages/cmake/cmake-2.8.6/Source -I/build/packages/cmake/cmake-2.8.6/Utilities/cmcompress -I/build/packages/cmake/cmake-2.8.6/Source/CTest -I/build/packages/cmake/cmake-2.8.6/Source/CursesDialog/form-o CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o -c /build/packages/cmake/cmake-2.8.6/Source/CursesDialog/ccmake.cxx Linking CXX executable ../bin/ccmake cd /build/packages/cmake/cmake-2.8.6/Source /build/packages/cmake/cmake-2.8.6/Bootstrap.cmk/cmake -E cmake_link_script CMakeFiles/ccmake.dir/link.txt --verbose=1 /build/system/bin/g++ CMakeFiles/ccmake.dir/CursesDialog/cmCursesBoolWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesCacheEntryComposite.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesDummyWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesFilePathWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesForm.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesLabelWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesMainForm.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesPathWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesStringWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o -o ../bin/ccmake libCMakeLib.a CursesDialog/form/libcmForm.a kwsys/libcmsys.a ../Utilities/cmexpat/libcmexpat.a ../Utilities/cmlibarchive/libarchive/libcmlibarchive.a -lmd ../Utilities/cmbzip2/libcmbzip2.a ../Utilities/cmcompress/libcmcompress.a ../Utilities/cmcurl/libcmcurl.a ../Utilities/cmzlib/libcmzlib.a -ldl -lsocket -lnsl -lcurses Undefined first referenced symbol in file wattr_on CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o wattr_off CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o ld: fatal: Symbol referencing errors. No output written to ../bin/ccmake collect2: ld returned 1 exit status make[2]: *** [bin/ccmake] Error 1 make[2]: Leaving directory `/build/packages/cmake/cmake-2.8.6' make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2 make[1]: Leaving directory `/build/packages/cmake/cmake-2.8.6' make: *** [all] Error 2 -- Chris -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problem Compiling on Solaris 10 x86
On 12/9/2011 3:43 PM, Christopher Hylarides wrote: Hey guys, I'm trying to build cmake on Solaris 10 x86 and am getting the following error: [ 94%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesMainForm.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesPathWidget.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesStringWidget.cxx.o [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o [ 96%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o Linking CXX executable ../bin/ccmake Undefined first referenced symbol in file wattr_on CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o wattr_off CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o ld: fatal: Symbol referencing errors. No output written to ../bin/ccmake collect2: ld returned 1 exit status make[2]: *** [bin/ccmake] Error 1 make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2 make: *** [all] Error 2 Below is with VERBOSE=1 [ 95%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o cd /build/packages/cmake/cmake-2.8.6/Source /build/system/bin/g++ -DCURL_STATICLIB -DLIBARCHIVE_STATIC -DCMAKE_BUILD_WITH_CMAKE -I/build/packages/cmake/cmake-2.8.6/Utilities -I/build/packages/cmake/cmake-2.8.6/Source -I/build/packages/cmake/cmake-2.8.6/Utilities/cmcompress -I/build/packages/cmake/cmake-2.8.6/Source/CTest -I/build/packages/cmake/cmake-2.8.6/Source/CursesDialog/form -o CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o -c /build/packages/cmake/cmake-2.8.6/Source/CursesDialog/cmCursesWidget.cxx /build/packages/cmake/cmake-2.8.6/Bootstrap.cmk/cmake -E cmake_progress_report /build/packages/cmake/cmake-2.8.6/CMakeFiles 41 [ 96%] Building CXX object Source/CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o cd /build/packages/cmake/cmake-2.8.6/Source /build/system/bin/g++ -DCURL_STATICLIB -DLIBARCHIVE_STATIC -DCMAKE_BUILD_WITH_CMAKE -I/build/packages/cmake/cmake-2.8.6/Utilities -I/build/packages/cmake/cmake-2.8.6/Source -I/build/packages/cmake/cmake-2.8.6/Utilities/cmcompress -I/build/packages/cmake/cmake-2.8.6/Source/CTest -I/build/packages/cmake/cmake-2.8.6/Source/CursesDialog/form -o CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o -c /build/packages/cmake/cmake-2.8.6/Source/CursesDialog/ccmake.cxx Linking CXX executable ../bin/ccmake cd /build/packages/cmake/cmake-2.8.6/Source /build/packages/cmake/cmake-2.8.6/Bootstrap.cmk/cmake -E cmake_link_script CMakeFiles/ccmake.dir/link.txt --verbose=1 /build/system/bin/g++ CMakeFiles/ccmake.dir/CursesDialog/cmCursesBoolWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesCacheEntryComposite.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesDummyWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesFilePathWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesForm.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesLabelWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesMainForm.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesPathWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesStringWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/cmCursesWidget.cxx.o CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o -o ../bin/ccmake libCMakeLib.a CursesDialog/form/libcmForm.a kwsys/libcmsys.a ../Utilities/cmexpat/libcmexpat.a ../Utilities/cmlibarchive/libarchive/libcmlibarchive.a -lmd ../Utilities/cmbzip2/libcmbzip2.a ../Utilities/cmcompress/libcmcompress.a ../Utilities/cmcurl/libcmcurl.a ../Utilities/cmzlib/libcmzlib.a -ldl -lsocket -lnsl -lcurses Undefined first referenced symbol in file wattr_on CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o wattr_off CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o ld: fatal: Symbol referencing errors. No output written to ../bin/ccmake collect2: ld returned 1 exit status make[2]: *** [bin/ccmake] Error 1 make[2]: Leaving directory `/build/packages/cmake/cmake-2.8.6' make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2 make[1]: Leaving directory `/build/packages/cmake/cmake-2.8.6' make: *** [all] Error 2 Looks like an issue with the curses library. Can you do a make VERBOSE=1? Also look in the CMakeCache.txt and see what curses library it has found. Looks like the headers might not match your library... -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe:
[Cmake-commits] CMake branch, next, updated. v2.8.6-2172-g61e773a
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 61e773ab20e417b5a1a7e30ac1c9143efa5269c4 (commit) via 61a7da279a71f251aa9ff9d5713838f0a20cbead (commit) via 33c24b210099c6cc9fc8f7b50621014ab6b3 (commit) via e61d2ded80e98c96911eaf9545f720c29de72dc3 (commit) from 87a1ebc9c7a9d3ed0723405c90f1e48aeaaf4562 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=61e773ab20e417b5a1a7e30ac1c9143efa5269c4 commit 61e773ab20e417b5a1a7e30ac1c9143efa5269c4 Merge: 87a1ebc 61a7da2 Author: David Cole david.c...@kitware.com AuthorDate: Fri Dec 9 09:00:36 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Fri Dec 9 09:00:36 2011 -0500 Merge topic 'update-cygwin-release-script' into next 61a7da2 Release: Increase timeout for slow-testing cygwin build 33c24b2 KWSys Nightly Date Stamp e61d2de KWSys Nightly Date Stamp http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=61a7da279a71f251aa9ff9d5713838f0a20cbead commit 61a7da279a71f251aa9ff9d5713838f0a20cbead Author: David Cole david.c...@kitware.com AuthorDate: Fri Dec 9 08:58:25 2011 -0500 Commit: David Cole david.c...@kitware.com CommitDate: Fri Dec 9 08:58:25 2011 -0500 Release: Increase timeout for slow-testing cygwin build Previously, the ExternalProject test was timing out at the default timeout value of 1500 seconds. Give it time, little one, it will finish if you learn patience. diff --git a/Utilities/Release/dash2win64_cygwin.cmake b/Utilities/Release/dash2win64_cygwin.cmake index da66002..74d5012 100644 --- a/Utilities/Release/dash2win64_cygwin.cmake +++ b/Utilities/Release/dash2win64_cygwin.cmake @@ -8,6 +8,7 @@ set(CPACK_SOURCE_GENERATORS CygwinSource) set(MAKE_PROGRAM make) set(INITIAL_CACHE CMAKE_BUILD_TYPE:STRING=Release CMAKE_Fortran_COMPILER_FULLPATH:FILEPATH=FALSE +DART_TESTING_TIMEOUT:STRING=7200 ) set(CXX g++) set(CC gcc) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- Utilities/Release/dash2win64_cygwin.cmake |1 + 2 files changed, 2 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v2.8.6-2174-gde2bbba
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 de2bbba316ad3b207d906a670ce8ce8d4e0b9c14 (commit)
via 4cb73c43ac13a4b796c61da137a1576c8c6a4d23 (commit)
from 61e773ab20e417b5a1a7e30ac1c9143efa5269c4 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=de2bbba316ad3b207d906a670ce8ce8d4e0b9c14
commit de2bbba316ad3b207d906a670ce8ce8d4e0b9c14
Merge: 61e773a 4cb73c4
Author: Brad King brad.k...@kitware.com
AuthorDate: Fri Dec 9 09:59:35 2011 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Dec 9 09:59:35 2011 -0500
Merge topic 'FortranCInterface-MinGW' into next
4cb73c4 FortranCInterface: Work around mingw32-make trouble with parens
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4cb73c43ac13a4b796c61da137a1576c8c6a4d23
commit 4cb73c43ac13a4b796c61da137a1576c8c6a4d23
Author: Brad King brad.k...@kitware.com
AuthorDate: Fri Dec 9 09:37:46 2011 -0500
Commit: Brad King brad.k...@kitware.com
CommitDate: Fri Dec 9 09:40:14 2011 -0500
FortranCInterface: Work around mingw32-make trouble with parens
The mingw32-make tool does not handle parenthesis in the path to a
source file consistently. When CMake is installed in a typical location
like c:\Program Files (x86)\CMake 2.8\ the mingw32-make tool fails on
the FortranCInterface detection project sometimes with errors like
mingw32-make -f CMakeFiles\myfort.dir\build.make
CMakeFiles/myfort.dir/my_module.f90.obj
mingw32-make: *** No rule to make target `x86)/CMake
2.8/share/cmake-2.8/Modules/FortranCInterface/my_module.f90)',
needed by `CMakeFiles/myfort.dir/my_module.f90.obj'. Stop.
due to parens in the path to the FortranCInterface source directory.
However, the behavior varies with the file name of build.make:
copy CMakeFiles\myfort.dir\build.make CMakeFiles\myfort.dir\build2.make
mingw32-make -f CMakeFiles\myfort.dir\build2.make
CMakeFiles/myfort.dir/my_module.f90.obj
[ 3%] Building Fortran object CMakeFiles/myfort.dir/my_module.f90.obj
Tested with
mingw32-make -v
GNU Make 3.82
Built for i386-pc-mingw32
Work around the problem by copying the whole FortranCInterface source
directory in to the project build tree.
diff --git a/Modules/FortranCInterface.cmake b/Modules/FortranCInterface.cmake
index 90ef59b..2455c5f 100644
--- a/Modules/FortranCInterface.cmake
+++ b/Modules/FortranCInterface.cmake
@@ -116,6 +116,14 @@ endforeach()
#-
set(FortranCInterface_SOURCE_DIR ${CMAKE_ROOT}/Modules/FortranCInterface)
+# MinGW's make tool does not always like () in the path
+if(${CMAKE_GENERATOR} MATCHES MinGW AND
+${FortranCInterface_SOURCE_DIR} MATCHES [()])
+ file(COPY ${FortranCInterface_SOURCE_DIR}/
+DESTINATION ${CMAKE_BINARY_DIR}/CMakeFiles/FortranCInterfaceMinGW)
+ set(FortranCInterface_SOURCE_DIR
${CMAKE_BINARY_DIR}/CMakeFiles/FortranCInterfaceMinGW)
+endif()
+
# Create the interface detection project if it does not exist.
if(NOT FortranCInterface_BINARY_DIR)
set(FortranCInterface_BINARY_DIR
${CMAKE_BINARY_DIR}/CMakeFiles/FortranCInterface)
---
Summary of changes:
Modules/FortranCInterface.cmake |8
1 files changed, 8 insertions(+), 0 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v2.8.6-2176-ga5b213a
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 a5b213a704b73e776b0f5a17d00e01cec1ebd224 (commit) via e8b8f0eda8f5d757582310a9f5d58c90d7074e3f (commit) from de2bbba316ad3b207d906a670ce8ce8d4e0b9c14 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a5b213a704b73e776b0f5a17d00e01cec1ebd224 commit a5b213a704b73e776b0f5a17d00e01cec1ebd224 Merge: de2bbba e8b8f0e Author: Brad King brad.k...@kitware.com AuthorDate: Fri Dec 9 13:02:04 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Fri Dec 9 13:02:04 2011 -0500 Merge topic 'xcode-rerun-issue-12616' into next e8b8f0e Xcode: Create separate rerun dependencies for subprojects (#12616) http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e8b8f0eda8f5d757582310a9f5d58c90d7074e3f commit e8b8f0eda8f5d757582310a9f5d58c90d7074e3f Author: Brad King brad.k...@kitware.com AuthorDate: Fri Dec 9 12:43:06 2011 -0500 Commit: Brad King brad.k...@kitware.com CommitDate: Fri Dec 9 13:00:22 2011 -0500 Xcode: Create separate rerun dependencies for subprojects (#12616) Generate the rerun dependency file for the top-level project() and each subdirectory project() into the corresponding build directory. Do not clobber them all with the one for the last subproject. This mistake was left from when the Xcode generator did not produce subprojects. diff --git a/Source/cmGlobalXCodeGenerator.cxx b/Source/cmGlobalXCodeGenerator.cxx index 32eaef8..859503f 100644 --- a/Source/cmGlobalXCodeGenerator.cxx +++ b/Source/cmGlobalXCodeGenerator.cxx @@ -458,8 +458,7 @@ void cmGlobalXCodeGenerator::CreateReRunCMakeFile( std::vectorstd::string::iterator new_end = std::unique(lfiles.begin(), lfiles.end()); lfiles.erase(new_end, lfiles.end()); - std::string dir = mf-GetHomeOutputDirectory(); - this-CurrentReRunCMakeMakefile = dir; + this-CurrentReRunCMakeMakefile = mf-GetStartOutputDirectory(); this-CurrentReRunCMakeMakefile += /CMakeScripts; cmSystemTools::MakeDirectory(this-CurrentReRunCMakeMakefile.c_str()); this-CurrentReRunCMakeMakefile += /ReRunCMake.make; --- Summary of changes: Source/cmGlobalXCodeGenerator.cxx |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v2.8.6-369-g85344d7
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 85344d767bc8430ad4e844331461e66791477133 (commit) from 33c24b210099c6cc9fc8f7b50621014ab6b3 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=85344d767bc8430ad4e844331461e66791477133 commit 85344d767bc8430ad4e844331461e66791477133 Author: KWSys Robot kwro...@kitware.com AuthorDate: Sat Dec 10 00:05:04 2011 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Sat Dec 10 00:05:04 2011 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 331c360..cdd8e3d 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2011) SET(KWSYS_DATE_STAMP_MONTH 12) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 09) +SET(KWSYS_DATE_STAMP_DAY 10) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
