Re: [CMake] Trying to setup make folder configuration on linux
Indeed, it works with
INSTALL(PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/massmailer DESTINATION bin)
PS.: This is only a development computer, you do not want to know how
ofter I accidently entered rm -f somewhere, and since I want to install
into the global bin path, I need root access.
Thank you and greetings, Louis
Tyler Roscoe ty...@cryptio.net
at Fri, 10 Dec 2010 12:56:35 -0800
On Fri, Dec 10, 2010 at 08:11:45PM +0100, Louis Hoefler wrote:
-- Build files have been written to: /root/massmailer/Debug
Probably not a good idea to be doing this kind of thing as root.
[100%] Built target massmailer
-- Configuring done
-- Generating done
-- Build files have been written to: /root/massmailer/Release
[100%] Built target massmailer
Install the massmailer release now [Yes/n]? Yes
[100%] Built target massmailer
Install the project...
-- Install configuration: Release
CMake Error at massmailer/cmake_install.cmake:36 (FILE):
file INSTALL cannot find /root/massmailer/massmailer/massmailer.
Call Stack (most recent call first):
cmake_install.cmake:37 (INCLUDE)
We'll need to see your CMakeLists.txt to help further, but it's likely
that you got a path wrong in your install() command.
hth,
tyler
___
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] cmake qt4 Lplates
On Friday 10 December 2010 21:17:21 Andreas Pakulat wrote:
On 10.12.10 22:09:29, luxInteg wrote:
Greetings,
I have my cmake L-plates firmly on ( with a Qt4 project I am stumbling
on )
I have these in CMakeLists.txt file:-
FIND_PACKAGE( Qt4 REQUIRED )
INCLUDE( ${QT_USE_FILE} )
set(QT_USE_OPENGL TRUE)
set(QT_USE_QTSVG TRUE )
SET( QT_USE_QTXML TRUE )
SET( QT_USE_QT3SUPPORT TRUE )
SET( QT_USE_QTNETWORK TRUE )
SET( QT_USE_QTASSISTANT TRUE )
SET(QT_USE_QTSCRIPT TRUE)
This is wrong, you should set the use-variables _before_ including
the use-file. Otherwise the qt-include-dir-variable as well as libraries
variable won't contain these modules. Thats the whole point of the
use-module.
thanks for the advice, I had initially tried a tiny project without these
settings. Yes moving INCLUDE( ${QT_USE_FILE} now has ${QT_INCLUDE_DIR}
recognised.
___
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] cmake qt4 Lplates again
Greetings,
Still withcmake L-plates firmly on ( with a Qt4 project ) I have now
stumbled into this:-
I have a series of header files to compile into .cpp files via the
QT4_WRAP_CPP() utility. Just one of the file needs to 'compiled'
beforehandthen compiled to object code with other normal .cpp source-
files beforehand. I thus want to set the directory for the generated
'transitory' file. (for obvious reasons such asto know where it is!)
I checked the cmake doc and wikis, mailing list etc and the best I came across
was this:-
http://www.mail-archive.com/cmake@cmake.org/msg24990.html
sugggesting the following:-
-
FILE(GLOB MOC_HEADERSmoc/*.h )
QT4_WRAP_CPP(out_moc_files ${MOC_HEADERS})
And the generated files are going in my CMAKE_BINARY_DIR.
Has there been any changes that allow the generated file to be placed
in say $(CMAKE_BINARY_DIRECTORY}/somedirectory?
and if so how is this achieved.
thanks n advance
sincerely
luxIngeg
___
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] Concise Example of BundleUtilities for Windows
Is there a concise example for BundleUtilites aimed at Windows? I _think_ I get how to use it on OS X but I am failing miserably on Windows side of things. My installation code is turning into a mess currently due to using BundleUtilities on the OS X side and manually writing CMake code to move stuff around on the Windows side. Any help is appreciated. I tried walking through the ParaView CMake code but that proved almost impossible. Thanks _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Software www.bluequartz.net Principal Software Engineer Dayton, Ohio ___ 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] Concise Example of BundleUtilities for Windows
I did find that section. what I am a bit confused about is this:
ParaView includes its own version of BundleUtilities.cmake? Why?
ParaView includes its own version of GetPrerequisites.cmake? Why?
Is BundleUtilities aim at _just_ installing? Or will the same code run
for CPack? I am trying to generate a zip archive but the normal MSVC
runtime libs are missing but yet they are in my installed location
on the machine? Can you rectify this difference for me?
Thanks for the feedback.
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Sat, Dec 11, 2010 at 12:43 PM, Dave Partyka dave.part...@kitware.com wrote:
Whats wrong with ParaView's CMake code? ;-)
The relevant section to doing bundle utilities on non Mac Platforms is this
blob from ParaView\Applications\ParaView\CMakeLists.txt
set(DIRS) # directories to search for prerequisites
IF(PARAVIEW_BUILD_QT_GUI)
list(APPEND DIRS ${QT_BINARY_DIR} ${QT_LIBRARY_DIR})
ENDIF(PARAVIEW_BUILD_QT_GUI)
IF(VTK_USE_FFMPEG_ENCODER)
get_filename_component(FFMPEG_DIR ${FFMPEG_avcodec_LIBRARY} PATH)
list(APPEND DIRS ${FFMPEG_DIR})
ENDIF(VTK_USE_FFMPEG_ENCODER)
IF(PARAVIEW_ENABLE_PYTHON)
get_filename_component(PYTHON_BIN_DIR ${PYTHON_EXECUTABLE} PATH)
get_filename_component(PYTHON_LIB_DIR ${PYTHON_LIBRARY} PATH)
list(APPEND DIRS ${PYTHON_BIN_DIR} ${PYTHON_LIB_DIR})
ENDIF(PARAVIEW_ENABLE_PYTHON)
IF(PARAVIEW_USE_MPI)
get_filename_component(MPI_LIB_DIR ${MPI_LIBRARY} PATH)
get_filename_component(MPI_BIN_DIR ${MPIEXEC} PATH)
list(APPEND DIRS ${MPI_LIB_DIR} ${MPI_BIN_DIR})
ENDIF(PARAVIEW_USE_MPI)
set(_extension)
set(_dir ${PV_INSTALL_LIB_DIR})
IF(WIN32)
set(_extension .exe)
set(_dir bin)
ENDIF(WIN32)
set(APPS \${CMAKE_INSTALL_PREFIX}/${_dir}/paraview${_extension}) # paths
to executables
# run Bundle utilities
INSTALL(CODE
include(\${ParaView_CMAKE_DIR}/BundleUtilities.cmake\)
fixup_bundle(\${APPS}\ \\ \${DIRS}\)
COMPONENT BrandedRuntime)
On Sat, Dec 11, 2010 at 12:31 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
Is there a concise example for BundleUtilites aimed at Windows? I
_think_ I get how to use it on OS X but I am failing miserably on
Windows side of things. My installation code is turning into a mess
currently due to using BundleUtilities on the OS X side and manually
writing CMake code to move stuff around on the Windows side.
Any help is appreciated. I tried walking through the ParaView CMake
code but that proved almost impossible.
Thanks
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
___
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
[CMake] Weird behaviour of functions with list arguments
Hello,
I noticed that when defining a function, one can access lists as
arguments using named arguments or ARGV0..ARGVn, but not using ARGV and
ARGN.
To elaborate, assuming the function list_as_args defined as follows:
function(list_as_arg)
message(STATUS ${ARGC} arguments, ARGV: ${ARGV})
message(STATUS First argument: ${ARGV0})
foreach(_arg ${ARGN})
message(STATUS Parsing argument ${_arg})
endforeach(_arg)
endfunction(list_as_arg)
... and called with 2 arguments:
list_as_arg(list1a;list1b list2a;list2b)
...prints the following:
-- 2 arguments, ARGV: list1a;list1b;list2a;list2b
-- First argument: list1a;list1b
-- Parsing argument list1a
-- Parsing argument list1b
-- Parsing argument list2a
-- Parsing argument list2b
So ARGV0 is not the same as the first argument of ARGV. Why? Is it that
the ARGV and ARGN lists get flattened, but the ARGVx are assigned before
that?
How can I safely access the values of ARGN, if they might contain lists?
Thanks,
Johannes
___
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] Trying to setup make folder configuration on linux
2010/12/11 Louis Hoefler louis.hoef...@gmx.de:
Indeed, it works with
INSTALL(PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/massmailer DESTINATION bin)
This is not the appropriate way to install a target build with cmake
(even if it works).
Like Tyler said you should be doing something wrong in your CMakeLists.txt.
PS.: This is only a development computer, you do not want to know how ofter
I accidently entered rm -f somewhere, and since I want to install into the
global bin path, I need root access.
On Linux (and may be on other platforms too) you'd better be building
a package (DEB, RPM)
using CPack as normal user and
install the generated package as root.
This will even be easier to remove your installation without messing
up with rm -rf.
The package manager (rpm, dpkg) may safely uninstall the package you
did install before.
--
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] cmake qt4 Lplates again
On Saturday 11 December 2010 17:46:37 luxInteg wrote:
Greetings,
Still withcmake L-plates firmly on ( with a Qt4 project ) I have now
stumbled into this:-
I have a series of header files to compile into .cpp files via the
QT4_WRAP_CPP() utility. Just one of the file needs to 'compiled'
beforehandthen compiled to object code with other normal .cpp
source- files beforehand. I thus want to set the directory for the
generated 'transitory' file. (for obvious reasons such asto know
where it is!)
As an update, it turns out the the odd file (call this this fileZ in question
is compiled into a'moc' file by the qt moc compiler and has the extension
.moc.The starting file is a .cpp file which does not seem to need to use
of QT4_WRAP_CPP()? (though I am not expert enough to be sure).
I thus tried an add_custom_command() (gleaned from moc --help)) that looks
like the following:-
configure_file(PATH/to/fileZ.cpp PATH/to/fileZ2.h @COPYONLY)
set(MOC_cmd /opt/qt4/bin/moc)
set(PRePRCESSOR_STIRNG yyy zzz)
ADD_CUSTOM_COMMAND(
OUTPUT -o ${CMAKE_BINARY_DIR}/path/to/fileZ.moc
COMMAND ${MOC_cmd}
-I${QT_INCLUDES}
-I${CMAKE_SOURCE_DIR}/path/to
-E${PRePRCESSOR_STIRNG}
${CMAKE_BINARY_DIR}/path/to/fileZ2.h
DEPENDS ${CMAKE_SOURCE_DIR}/path/to/fileZ.cpp )
but (apart from the first line) it did not work.
advice would be appreiated.
___
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-commits] CMake branch, next, updated. v2.8.3-803-g9323fed
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 9323fedf89a7bac078c684220e47c237fba360cd (commit)
via 6d64a7e3512ba1f6e52b18d65fd8bd8b137de876 (commit)
via f20e727e74227c4a506c13c8903e258e749ca8fe (commit)
from b7ea1c5879ce1025828f7b4ecc153a4aed67604d (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=9323fedf89a7bac078c684220e47c237fba360cd
commit 9323fedf89a7bac078c684220e47c237fba360cd
Merge: b7ea1c5 6d64a7e
Author: Eric Noulard eric.noul...@gmail.com
AuthorDate: Sat Dec 11 06:05:18 2010 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sat Dec 11 06:05:18 2010 -0500
Merge topic 'CPack-AddMoreTests' into next
6d64a7e CPack Default component test for ZIP should be OK
f20e727 CPack new tests for component install
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6d64a7e3512ba1f6e52b18d65fd8bd8b137de876
commit 6d64a7e3512ba1f6e52b18d65fd8bd8b137de876
Author: Eric NOULARD eric.noul...@gmail.com
AuthorDate: Sat Dec 11 11:59:02 2010 +0100
Commit: Eric NOULARD eric.noul...@gmail.com
CommitDate: Sat Dec 11 11:59:02 2010 +0100
CPack Default component test for ZIP should be OK
diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index 3538e44..2e88bcf 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -540,8 +540,9 @@ ${CMake_BINARY_DIR}/bin/cmake -DVERSION=master -P
${CMake_SOURCE_DIR}/Utilities/
set(CPackRun_CPackGen -DCPackGen=ZIP)
set(CPackRun_CPackCommand -DCPackCommand=${CMAKE_CPACK_COMMAND})
+set(CPackRun_CPackComponentWay -DCPackComponentWay=default)
-ADD_TEST(CPackComponentsForAll-ZIP-NoComponent ${CMAKE_CTEST_COMMAND}
+ADD_TEST(CPackComponentsForAll-ZIP-default ${CMAKE_CTEST_COMMAND}
--build-and-test
${CMake_SOURCE_DIR}/Tests/CPackComponentsForAll
${CMake_BINARY_DIR}/Tests/CPackComponentsForAll/buildZIP-NoComponent
@@ -556,6 +557,7 @@ ${CMake_BINARY_DIR}/bin/cmake -DVERSION=master -P
${CMake_SOURCE_DIR}/Utilities/
-DCPackComponentsForAll_BINARY_DIR:PATH=${CMake_BINARY_DIR}/Tests/CPackComponentsForAll/buildZIP-NoComponent
${CPackRun_CPackCommand}
${CPackRun_CPackGen}
+${CPackRun_CPackComponentWay}
-P
${CMake_SOURCE_DIR}/Tests/CPackComponentsForAll/RunCPackVerifyResult.cmake)
LIST(APPEND TEST_BUILD_DIRS
${CMake_BINARY_DIR}/Tests/CPackComponentsForAll)
diff --git a/Tests/CPackComponentsForAll/CMakeLists.txt
b/Tests/CPackComponentsForAll/CMakeLists.txt
index 4153ac9..971b2dc 100644
--- a/Tests/CPackComponentsForAll/CMakeLists.txt
+++ b/Tests/CPackComponentsForAll/CMakeLists.txt
@@ -7,7 +7,7 @@
# Depending on the CPack generator and on some CPACK_xxx var values
# the generator may produce a single (NSIS, PackageMaker)
# or several package files (Archive Generators, RPM, DEB)
-cmake_minimum_required(VERSION 2.8.3 FATAL_ERROR)
+cmake_minimum_required(VERSION 2.8.3.20101130 FATAL_ERROR)
project(CPackComponentsForAll)
# Create the mylib library
diff --git a/Tests/CPackComponentsForAll/RunCPackVerifyResult.cmake
b/Tests/CPackComponentsForAll/RunCPackVerifyResult.cmake
index 6b471ca..b24ae5a 100644
--- a/Tests/CPackComponentsForAll/RunCPackVerifyResult.cmake
+++ b/Tests/CPackComponentsForAll/RunCPackVerifyResult.cmake
@@ -13,7 +13,14 @@ endif(NOT CPackGen)
if(NOT CPackCommand)
message(FATAL_ERROR CPackCommand not set)
endif(NOT CPackCommand)
+
+if(NOT CPackComponentWay)
+ message(FATAL_ERROR CPackComponentWay not set)
+endif(NOT CPackComponentWay)
+
set(expected_file_mask )
+# The usual default behavior is to expect a single file
+set(expected_count 1)
execute_process(COMMAND ${CPackCommand} -G ${CPackGen}
RESULT_VARIABLE result
@@ -23,10 +30,14 @@ execute_process(COMMAND ${CPackCommand} -G ${CPackGen}
if(CPackGen MATCHES ZIP)
set(expected_file_mask ${CPackComponentsForAll_BINARY_DIR}/MyLib-*.zip)
-set(expected_count 2)
+if (${CPackComponentWay} STREQUAL default)
+set(expected_count 1)
+endif(${CPackComponentWay} STREQUAL default)
endif(CPackGen MATCHES ZIP)
-
+# Now verify if the number of expected file is OK
+# - using expected_file_mask and
+# - expected_count
if(expected_file_mask)
file(GLOB expected_file ${expected_file_mask})
@@ -35,12 +46,12 @@ if(expected_file_mask)
message(STATUS expected_file_mask='${expected_file_mask}')
if(NOT expected_file)
-message(FATAL_ERROR error: expected_file does not exist:
CPackComponentsForAll test fails.)
+message(FATAL_ERROR error: expected_file=${expected_file} does not exist:
CPackComponentsForAll
[Cmake-commits] CMake branch, next, updated. v2.8.3-806-gc9c1272
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 c9c1272a165b5e7f081746b975881b404d888586 (commit)
via b316087c095e23e131bf2ccf5eb7110b35df0e29 (commit)
via 68cd3fe038471b5a60d396eac141a69414b3064d (commit)
from 9323fedf89a7bac078c684220e47c237fba360cd (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=c9c1272a165b5e7f081746b975881b404d888586
commit c9c1272a165b5e7f081746b975881b404d888586
Merge: 9323fed b316087
Author: Marcus D. Hanwell marcus.hanw...@kitware.com
AuthorDate: Sat Dec 11 12:13:18 2010 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sat Dec 11 12:13:18 2010 -0500
Merge topic 'external-project-args-file' into next
b316087 Escape file write expansion, and build up lists.
68cd3fe Added CMAKE_CACHE_ARGS to ExternalProject.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b316087c095e23e131bf2ccf5eb7110b35df0e29
commit b316087c095e23e131bf2ccf5eb7110b35df0e29
Author: Marcus D. Hanwell marcus.hanw...@kitware.com
AuthorDate: Fri Dec 10 20:03:58 2010 -0500
Commit: Marcus D. Hanwell marcus.hanw...@kitware.com
CommitDate: Sat Dec 11 12:11:27 2010 -0500
Escape file write expansion, and build up lists.
Escaped the @var@ in the file writes - this was being expanded at file
write and so not causing a reconfigure at the right time. I also took
care of build up lists of lists in the variables, especially important
for things like MPI_EXTRA_LIBRARY. Added some error checking, and use
the tmp_dir for initial cache file.
diff --git a/Modules/ExternalProject.cmake b/Modules/ExternalProject.cmake
index c575a73..542dbc2 100644
--- a/Modules/ExternalProject.cmake
+++ b/Modules/ExternalProject.cmake
@@ -554,23 +554,36 @@ function(_ep_write_initial_cache script_filename args)
# Write out values into an initial cache, that will be passed to CMake with
-C
set(script_initial_cache )
set(regex ^([^:]+):([^=]+)=(.*)$)
+ set(setArg )
foreach(line ${args})
-string(REGEX REPLACE ^-D line ${line})
-if(${line} MATCHES ${regex})
- string(REGEX MATCH ${regex} match ${line})
- set(name ${CMAKE_MATCH_1})
- set(type ${CMAKE_MATCH_2})
- set(value ${CMAKE_MATCH_3})
- set(setArg set(${name} \${value}\ CACHE ${type} \Initial cache\
FORCE))
- set(script_initial_cache ${script_initial_cache}\n${setArg})
+if(${line} MATCHES ^-D)
+ if(setArg)
+# This is required to build up lists in variables, or complete an entry
+set(setArg ${setArg}${accumulator}\ CACHE ${type} \Initial cache\
FORCE))
+set(script_initial_cache ${script_initial_cache}\n${setArg})
+set(accumulator )
+set(setArg )
+ endif()
+ string(REGEX REPLACE ^-D line ${line})
+ if(${line} MATCHES ${regex})
+string(REGEX MATCH ${regex} match ${line})
+set(name ${CMAKE_MATCH_1})
+set(type ${CMAKE_MATCH_2})
+set(value ${CMAKE_MATCH_3})
+set(setArg set(${name} \${value})
+ else()
+message(WARNING Line '${line}' does not match regex. Ignoring.)
+ endif()
+else()
+ # Assume this is a list to append to the last var
+ set(accumulator ${accumulator};${line})
endif()
endforeach()
# Write out the initial cache file to the location specified.
if(NOT EXISTS ${script_filename}.in)
-file(WRITE ${script_filename}.in @script_initial_ca...@\n)
+file(WRITE ${script_filename}.in \...@script_initial_cache\@\n)
endif()
configure_file(${script_filename}.in ${script_filename})
-
endfunction(_ep_write_initial_cache)
@@ -1251,7 +1264,7 @@ function(_ep_add_configure_command name)
# If there are any CMAKE_CACHE_ARGS, write an initial cache and use it
get_property(cmake_cache_args TARGET ${name} PROPERTY _EP_CMAKE_CACHE_ARGS)
if(cmake_cache_args)
- set(_ep_cache_args_script
${CMAKE_CURRENT_BINARY_DIR}/${name}-cache.cmake)
+ set(_ep_cache_args_script ${tmp_dir}/${name}-cache.cmake)
_ep_write_initial_cache(${_ep_cache_args_script} ${cmake_cache_args})
list(APPEND cmd -C${_ep_cache_args_script})
endif()
@@ -1274,7 +1287,7 @@ function(_ep_add_configure_command name)
# Fixes issue http://public.kitware.com/Bug/view.php?id=10258
#
if(NOT EXISTS ${tmp_dir}/${name}-cfgcmd.txt.in)
-file(WRITE ${tmp_dir}/${name}-cfgcmd.txt.in cmd='@cmd@'\n)
+file(WRITE ${tmp_dir}/${name}-cfgcmd.txt.in cmd='\...@cmd\@'\n)
endif()
configure_file(${tmp_dir}/${name}-cfgcmd.txt.in
${tmp_dir}/${name}-cfgcmd.txt)
list(APPEND file_deps
[Cmake-commits] CMake branch, master, updated. v2.8.3-168-g1b98d99
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 1b98d99c28949347c7c6a1e5ee67ee8e49670277 (commit) from da4c2f6214e8c86c7fa2a49095e7672ea377c8c2 (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=1b98d99c28949347c7c6a1e5ee67ee8e49670277 commit 1b98d99c28949347c7c6a1e5ee67ee8e49670277 Author: KWSys Robot kwro...@kitware.com AuthorDate: Sun Dec 12 00:01:04 2010 -0500 Commit: KWSys Robot kwro...@kitware.com CommitDate: Sun Dec 12 00:10:02 2010 -0500 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 266cb26..5f8a661 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2010) SET(KWSYS_DATE_STAMP_MONTH 12) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 11) +SET(KWSYS_DATE_STAMP_DAY 12) --- 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
