[cmake-developers] [CMake 0011383]: timeout test property not respected if zero
The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=11383 == Reported By:Clinton Stimpson Assigned To: == Project:CMake Issue ID: 11383 Category: CTest Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2010-10-29 17:44 EDT Last Modified: 2010-10-29 17:44 EDT == Summary:timeout test property not respected if zero Description: If I put this in my .ctest script set(CTEST_TEST_TIMEOUT 2) then in a CMakeLists.txt set_tests_properties(mytest PROPERTIES TIMEOUT 4) I get a 4 second timeout as expected. But if I change that to set_tests_properties(mytest PROPERTIES TIMEOUT 0) to remove the timeout, I get a 2 second timeout instead. == Issue History Date ModifiedUsername FieldChange == 2010-10-29 17:44 Clinton StimpsonNew Issue == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] CMake 2.8.3-rc4 ready for testing!
The CMake 2.8.3 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D EXCEPT: There are not yet Irix or Sun pre-built binary installers available for CMake 2.8.3-rc4. There is a failing (HTML documentation validity checking) test on some platforms that appears to be unrelated to any CMake source code changes. That test failure is preventing the release building process from completing today on those platforms. If that issue clears up soon, I'll re-do the installers on those platforms. If not, just use rc3, or build from source. We'll address this before the final release. This will be the LAST release candidate for 2.8.3 unless a major regression is reported. So please try it on your projects and let us know right away about any problems. Since we switched to git, and a new workflow, we're expecting to do more frequent releases. Because of that, our release candidate phases will be shorter than they have been historically. So, if you want to test this out and ask for a fix, do it soon, or hold your peace till the next release! Following is the list of changes in this release. Since we switched to git, this list is now the 'git log' one line summary written by the named CMake developers. Please try this version of CMake on your projects and report any issues to the list or the bug tracker. Happy building! -Dave Changes in CMake 2.8.3-rc4 (since 2.8.3-rc3) Bill Hoffman (1): When processing DartMeasurements use the tests working directory. David Cole (2): ExternalProject: No svn --username if empty (#11173) Avoid problem reading jni.h on Macs. David Partyka (5): Fixed appending PATH to dumpbin tool from growing without bounds. Switch to CMAKE_PATH when doing PATH comparisons on Windows. Remove unecessary TO_CMAKE_PATH for gp_cmd_dir. Append the gp_tool path to the system PATH using native slashes. Fixes to GetPrerequisites for cygwin Eric NOULARD (1): CPackDeb Added several optional debian binary package fields Marcus D. Hanwell (2): ENH: Added case for Python 2.7. Fixed parallel build for generators with EXTRA. Changes in CMake 2.8.3-rc3 (since 2.8.3-rc2) Alex Neundorf (4): Remove trailing whitespace Add automatic variable CMAKE_CURRENT_LIST_DIR(dir of CMAKE_CURRENT_LIST_FILE) Use absolute path to FindPackageHandleStandardArgs.cmake everywhere CodeBlocks Generator: Do not omit files in the project file listing. Brad King (4): VS10: Order .vcxproj dependencies deterministically (#10502) Document ENABLE_EXPORTS behavior on Mac (#11295) FindHDF5: Fix typo in parallel-IO support check (#11291) Xcode: Recognize .hh as C++ (#11307) Clinton Stimpson (1): Find imports dir in Qt 4.7 David Partyka (1): Update module to locate newely released MS MPI HPC Pack R2. Philip Lowman (1): Remove superfluous variable Boost_COMPAT_STATIC_RUNTIME. Rolf Eike Beer (2): FindSubversion: Fix for German localized client (#11273) FindSubversion: Use C locale to detect version (#11273) Changes in CMake 2.8.3-rc2 (since 2.8.3-rc1) Alex Neundorf (5): APPEND and not-APPEND mode of feature_summary() were swapped Set a default DESCRIPTION if none is given for ALL mode of feature_summary() Close ENDFUNCTION() properly with the same name as FUNCTION() Make cmake-gui remember whether the Advanced checkbox was checked or not Also store the required version number in the details message. Ben Boeckel (3): Add test that CMake errors with empty libs Fix which string is checked for in the test XCode generation should fail if lang isn't known Bill Hoffman (5): Fix the name of the variable being tested. Fix KWStyle line length issues. Add a delay after untar on windows to make external project work on windows 7 Add a new line to the end of the generated main.cxx for the hpux compiler. Fix for bug #11274, VS10 custom commands that create files in INTDIR fix. Brad King (12): Evaluate OBJECT_DIR rule variable for executables ccmake: Fix search with '/' MinGW: Support long object file lists Document IMPORTED_NO_SONAME target property FindMPI: Recoginze -f flags from mpicc (#10771) Add module-dir flag for Compaq Visual Fortran (#11248) FindPythonInterp: Look for python2.7 interpreter VS10: Use $(IntDir) for per-source output directory (#11270) Reset platform/compiler info status for each language Remove trailing whitespace from Xcode generator source VS10: Skip targets with no linker language (#11230) VS10: Encode custom command comments for echo (#11283) Clinton Stimpson (1): Fix regression in cross-compile patches with finding Qt libs.
[CMake] cmake policy setting
As there is no example in the documentaion, could someone clarify me if the change of any policy that should require an additional cmake_policy(SET CMP NEW) could also be requested at cmake invocation with --- # -D var:type=value: Create a cmake cache entry. When cmake is first run in an empty build tree, it creates a CMakeCache.txt file and populates it with customizable settings for the project. This option may be used to specify a setting that takes priority over the project's default value. The option may be repeated for as many cache entries as desired. --- Regards Marco ___ 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 define current working directory of command line tool
Are you trying to run the executable with ADD_TEST? In that case the working
directory is always CMAKE_CURRENT_BINARY_DIR. If you need to change it, create
a wrapper script (you can do so using the CMake language in order to not depend
on any other interpreter).
no, just add_executable and then starting the target in debug mode inside the
ide. but maybe add_test is the solution to my
problem, i have to look at it. is this for starting an executable with some
command line arguments?
-Jochen
It is for adding a single unit test which can then be run using CTest.
Michael
Perhaps adding unit tests for testing my command line tool is the right
way, but really practical would be to
have a target property to set the default debugging working directory
for a target.
In visual studio this is right click on a target, then properties. Then
on the left side Configuration Properties-Debugging
and on the right side Working Directory. This is used when you launch
the target from inside the IDE. I always have
to set it by hand. Even worse on macos: there I have to set it every
time cmake has run.
Therefore I still would request this feature (e.g.
set_target_properties(MyTarget PROPERTIES WORKING_DIRECTORY
${CMAKE_CURRENT_SOURCE_DIR}) )
-Jochen
___
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 policy setting
2010/10/29 Marco Atzeri marco_atz...@yahoo.it: As there is no example in the documentaion, could someone clarify me if the change of any policy that should require an additional cmake_policy(SET CMP NEW) could also be requested at cmake invocation with --- # -D var:type=value: Create a cmake cache entry. When cmake is first run in an empty build tree, it creates a CMakeCache.txt file and populates it with customizable settings for the project. This option may be used to specify a setting that takes priority over the project's default value. The option may be repeated for as many cache entries as desired. --- I do not think policy value reaches the CMake cache. and I don't know a way to set up policy from command line. I'll have to check the code but even if policy has the SET argument in it it does not share properties with the CMake set command itself. set and cmake_policy are 2 separate CMake commands. the -D var:type=value command line argument may replace set command in CMakeLists.txt but I am not aware of any command line args that may be used to enforce policy. Again I'll have to check the source code to be sure. -- 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
[CMake] How to differ?
Hi, I'm new to the cmake tool trying to find out how to apply this best to our system. Here's a problem I would like to know how to do best: Assume following setup: - /projects/libs/one - /projects/libs/two - /projects/apps/first - /projects/apps/two Both application are using both libraries. Being in /tmp/obj I have some options to prepare a build: - cmake /projects (this means: intending to build all) - cmake /projects/libs (this means: intending to build all libraries only) - cmake /projects/apps (this means: intending to build all applications) - cmake /projects/apps/first (this means: intending to build app first only) Now the question(s): - Using build all is fine. I'm using link_directories for both applications. But using the last two examples I fail with cannot find -lone (and two). How can I fix this? - I know I could use include_subdirectory but then I fail with first and third example. I will get a message like another target with same name already exists. Both question are relating to same. We would like to be flexible... Could somebody provide a little help please? Kind Regards Thomas Thomas Lehmann Scrum Master [cid:rts-logo.png@c547960bd3b149468eddcd645a5a1841] RTS Realtime Systems Software GmbH, Rembrandtstrasse 13, D-60596 Frankfurt am Main T: +49.69.61009.0 / F: +49.69.61009.181 Sitz: Frankfurt am Main - HRB 84467 Amtsgericht Frankfurt am Main Gesch?ftsf?hrer: Steffen Gemuenden, Igor Sluga www.rtsgroup.net This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify me immediately by return email and promptly delete this message and its attachments from your computer system. inline: rts-logo.png___ 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 differ?
2010/10/29 Thomas Lehmann t.lehm...@rtsgroup.net
Hi,
I’m new to the cmake tool trying to find out how to apply
this best to our system. Here’s a problem I would like
to know how to do best:
Assume following setup:
- /projects/libs/one
- /projects/libs/two
- /projects/apps/first
- /projects/apps/two
Both application are using both libraries.
Being in /tmp/obj ….
What does this mean being in /tmp/obj ?
I have some options to prepare a build:
- cmake /projects (this means: intending to build all)
- cmake /projects/libs (this means: intending to build all
libraries only)
- cmake /projects/apps (this means: intending to build all
applications)
- cmake /projects/apps/first (this means: intending to build app
“first” only)
Now the question(s):
- Using “build all” is fine. I’m using “link_directories” for both
applications.
But using the last two examples I fail with “cannot find –lone” (and two).
How can I fix this?
- I know I could use “include_subdirectory” but then I fail with
first and third
example. I will get a message like “another target with same name already
exists”.
Both question are relating to same.
I think I don't get it.
What do you want to do?
1) Write a single CMake-enabled project with which you may build all
or part of the project
2) Write several separate CMake-enabled project which are inter-dependant?
I would personnally try 1) unless you have good reason not to do so.
The projects/CMakeLists.txt would be the main project
consisting in some
add_subdirectory(libs/)
add_subdirectory(apps//)
then for each lib there will be some
projects/libs//CMakeLists.txt consisting in
add_library( list of source) command
and for each app there will be some
projects/apps//CMakeLists.txt which contains
add_executable( list of source)
target_link_library( )
include_directories(${CMAKE_SOURCE_DIR}/libs/)
from this structure you should be able to build part or all of the target
just by calling the appropriate one. CMake should take care of building
the dependencies using the target_link_library links.
However I may have misunderstood what you want?
Could you tell us what you want and may be send us some CMakeLists.txt
you already tried?
--
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 policy setting
On 10/29/2010 6:33 AM, Marco Atzeri wrote: As there is no example in the documentaion, could someone clarify me if the change of any policy that should require an additional cmake_policy(SET CMP NEW) could also be requested at cmake invocation with --- # -Dvar:type=value: Create a cmake cache entry. When cmake is first run in an empty build tree, it creates a CMakeCache.txt file and populates it with customizable settings for the project. This option may be used to specify a setting that takes priority over the project's default value. The option may be repeated for as many cache entries as desired. --- There is no way to change a policy from the cache. That is not really how policies are supposed to work. It is for the developer of the CmakeLists.txt files to set the policies as they see fit. The -D options are user options. In most cases, moving to a NEW policy will require changes to the CMakeLists.txt files so doing it from the command line would not make sense. Here is the documentation for polices: http://www.cmake.org/Wiki/CMake_Policies -Bill ___ 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 differ?
At the end you can see a version which was working well
but we found it somewhat complicated with the paths.
1) Write a single CMake-enabled project with which you may build all
or part of the project
2) Write several separate CMake-enabled project which are inter-
dependant?
I would personnally try 1) unless you have good reason not to do so.
The projects/CMakeLists.txt would be the main project
consisting in some
add_subdirectory(libs/)
add_subdirectory(apps//)
Yes. we do that.
then for each lib there will be some
projects/libs//CMakeLists.txt consisting in
add_library( list of source) command
Yes. we have this.
and for each app there will be some
projects/apps//CMakeLists.txt which contains
add_executable( list of source)
target_link_library( )
include_directories(${CMAKE_SOURCE_DIR}/libs/)
Yes. But how do that program generate the libraries
when they are not build yet?
from this structure you should be able to build part or all of the
target
just by calling the appropriate one. CMake should take care of building
the dependencies using the target_link_library links.
cmake can be used for different paths in a source tree.
Trying to create both apps both are trying to build both
libraries on different locations - cmake complains.
The command after here fails without handling to use
link_directories or add_subdirectory properly:
/tmp/obj cmake /projects/apps
1) I can rebuild all
2) I can build a set of applications
3) I can build just one application
Independent on what scenario I use I want to ensure that
all dependencies are built and used.
Thomas
Thomas Lehmann
Scrum Master
RTS Realtime Systems Software GmbH, Rembrandtstrasse 13, D-60596 Frankfurt am
Main
T: +49.69.61009.0 / F: +49.69.61009.181
Sitz: Frankfurt am Main - HRB 84467 Amtsgericht Frankfurt am Main
Gesch?ftsf?hrer: Steffen Gemuenden, Igor Sluga
www.rtsgroup.net
This email and any attachments are for the exclusive and confidential use of
the intended recipient. If you are not the intended recipient, or an employee
or agent responsible for delivering this message to the intended recipient,
please do not read, distribute or take action in reliance upon this message. If
you have received this in error, please notify me immediately by return email
and promptly delete this message and its attachments from your computer system.
___
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 differ?
2010/10/29 Thomas Lehmann t.lehm...@rtsgroup.net:
At the end you can see a version which was working well
but we found it somewhat complicated with the paths.
I did not see any attachment or inline copy of CMakeLists.txt
[...]
and for each app there will be some
projects/apps//CMakeLists.txt which contains
add_executable( list of source)
target_link_library( )
include_directories(${CMAKE_SOURCE_DIR}/libs/)
Yes. But how do that program generate the libraries
when they are not build yet?
Because CMake should handle the dependency because
of the target_link_library.
By the way which CMake version do you use?
And which CMake Generator (Makefile, Visual Studio project...)
on which platform (Linux, Windows, MacOS etc...)
from this structure you should be able to build part or all of the
target
just by calling the appropriate one. CMake should take care of building
the dependencies using the target_link_library links.
cmake can be used for different paths in a source tree.
Trying to create both apps both are trying to build both
libraries on different locations - cmake complains.
What do you mean by complains?
Could you copy/paste the complain you get from CMake?
The command after here fails without handling to use
link_directories or add_subdirectory properly:
/tmp/obj cmake /projects/apps
You could do:
/tmp/obj cmake /projects
the
1) rebuild all
2) build a set of applications
3) build just one application
1) I can rebuild all
2) I can build a set of applications
3) I can build just one application
Independent on what scenario I use I want to ensure that
all dependencies are built and used.
Then you should launch CMake on the whole set of (lib, apps etc...)
and only build what you want.
--
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] how to define current working directory of command line tool
On Fri, Oct 29, 2010 at 7:48 AM, Jochen Wilhelmy j.wilhe...@arcor.de wrote:
Are you trying to run the executable with ADD_TEST? In that case the
working directory is always CMAKE_CURRENT_BINARY_DIR. If you need to change
it, create a wrapper script (you can do so using the CMake language in
order
to not depend on any other interpreter).
no, just add_executable and then starting the target in debug mode inside
the ide. but maybe add_test is the solution to my
problem, i have to look at it. is this for starting an executable with
some command line arguments?
-Jochen
It is for adding a single unit test which can then be run using CTest.
Michael
Perhaps adding unit tests for testing my command line tool is the right way,
but really practical would be to
have a target property to set the default debugging working directory for a
target.
In visual studio this is right click on a target, then properties. Then on
the left side Configuration Properties-Debugging
and on the right side Working Directory. This is used when you launch the
target from inside the IDE. I always have
to set it by hand. Even worse on macos: there I have to set it every time
cmake has run.
Therefore I still would request this feature (e.g.
set_target_properties(MyTarget PROPERTIES WORKING_DIRECTORY
${CMAKE_CURRENT_SOURCE_DIR}) )
-Jochen
___
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
See my CreateLaunchers.cmake script here:
http://github.com/rpavlik/cmake-modules
--
Ryan Pavlik
HCI Graduate Student
Virtual Reality Applications Center
Iowa State University
rpav...@iastate.edu
http://academic.cleardefinition.com
Internal VRAC/HCI Site: http://tinyurl.com/rpavlik
___
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] Linking Boost on Linux on 64bit host and 32bit target
Hi all~
I have a project using Boost that should compile for both 64bit and 32bit on a
64bit host. This works fine for a 64bit target, but I can't get this to work
for a 32bit target. I've done a fair share of googling to find this answer,
but have not stumbled across anything that helps. In fact, the only flag that
I can find to distinguish between 32bit build and 64bit builds only applies to
windows with ${CMAKE_CL_64}.
In order to compile for 32bit on a 64bit host, I have a -D parameter called
BUILD64. Here is my logic to initialize this var:
if( WIN32 )
set( BUILD64 ${CMAKE_CL_64} )
else()
option( BUILD64 Build a 64-bit product OFF )
if( BUILD64 )
message( STATUS 64-bit build )
endif( )
endif()
The syntax for finding boost is thus:
set( Boost_USE_MULTITHREADED ON )
set( Boost_USE_STATIC_LIBS ON )
set( Boost_DETAILED_FAILURE_MSG ON )
# set( Boost_DEBUG ON )
find_package( Boost 1.33.0 COMPONENTS program_options )
The boost find package module doesn't appear at a glance to distinguish between
64bit and 32bit builds; I don't understand how it is supposed to work. I have
a feeling that it is expected that find_library is supposed to distinguish the
path behavior, but I don't have it set up right.
When I compile and link for 32bit, I get:
Scanning dependencies of target Foo
[ 72%] Building CXX object client/CMakeFiles/Foo.dir/Foo.cpp.o
[ 81%] Building CXX object client/CMakeFiles/Foo.dir/openCL.cpp.o
[ 90%] Building CXX object client/CMakeFiles/Foo.dir/StatisticalTimer.cpp.o
[100%] Building CXX object client/CMakeFiles/Foo.dir/stdafx.cpp.o
Linking CXX executable Foo
/usr/bin/ld: warning: i386:x86-64 architecture of input file
`/usr/local/boost_1_44_0/lib64/libboost_program_options.a(cmdline.o)' is
incompatible with i386 output
/usr/bin/ld: warning: i386:x86-64 architecture of input file
`/usr/local/boost_1_44_0/lib64/libboost_program_options.a(options_description.o)'
is incompatible with i386 output
As you can see, it is looking in lib64 instead of lib. How do I change that
behavior?
Thanks for any help,
Kent
___
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 2.8.3-rc4 ready for testing!
The CMake 2.8.3 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D EXCEPT: There are not yet Irix or Sun pre-built binary installers available for CMake 2.8.3-rc4. There is a failing (HTML documentation validity checking) test on some platforms that appears to be unrelated to any CMake source code changes. That test failure is preventing the release building process from completing today on those platforms. If that issue clears up soon, I'll re-do the installers on those platforms. If not, just use rc3, or build from source. We'll address this before the final release. This will be the LAST release candidate for 2.8.3 unless a major regression is reported. So please try it on your projects and let us know right away about any problems. Since we switched to git, and a new workflow, we're expecting to do more frequent releases. Because of that, our release candidate phases will be shorter than they have been historically. So, if you want to test this out and ask for a fix, do it soon, or hold your peace till the next release! Following is the list of changes in this release. Since we switched to git, this list is now the 'git log' one line summary written by the named CMake developers. Please try this version of CMake on your projects and report any issues to the list or the bug tracker. Happy building! -Dave Changes in CMake 2.8.3-rc4 (since 2.8.3-rc3) Bill Hoffman (1): When processing DartMeasurements use the tests working directory. David Cole (2): ExternalProject: No svn --username if empty (#11173) Avoid problem reading jni.h on Macs. David Partyka (5): Fixed appending PATH to dumpbin tool from growing without bounds. Switch to CMAKE_PATH when doing PATH comparisons on Windows. Remove unecessary TO_CMAKE_PATH for gp_cmd_dir. Append the gp_tool path to the system PATH using native slashes. Fixes to GetPrerequisites for cygwin Eric NOULARD (1): CPackDeb Added several optional debian binary package fields Marcus D. Hanwell (2): ENH: Added case for Python 2.7. Fixed parallel build for generators with EXTRA. Changes in CMake 2.8.3-rc3 (since 2.8.3-rc2) Alex Neundorf (4): Remove trailing whitespace Add automatic variable CMAKE_CURRENT_LIST_DIR(dir of CMAKE_CURRENT_LIST_FILE) Use absolute path to FindPackageHandleStandardArgs.cmake everywhere CodeBlocks Generator: Do not omit files in the project file listing. Brad King (4): VS10: Order .vcxproj dependencies deterministically (#10502) Document ENABLE_EXPORTS behavior on Mac (#11295) FindHDF5: Fix typo in parallel-IO support check (#11291) Xcode: Recognize .hh as C++ (#11307) Clinton Stimpson (1): Find imports dir in Qt 4.7 David Partyka (1): Update module to locate newely released MS MPI HPC Pack R2. Philip Lowman (1): Remove superfluous variable Boost_COMPAT_STATIC_RUNTIME. Rolf Eike Beer (2): FindSubversion: Fix for German localized client (#11273) FindSubversion: Use C locale to detect version (#11273) Changes in CMake 2.8.3-rc2 (since 2.8.3-rc1) Alex Neundorf (5): APPEND and not-APPEND mode of feature_summary() were swapped Set a default DESCRIPTION if none is given for ALL mode of feature_summary() Close ENDFUNCTION() properly with the same name as FUNCTION() Make cmake-gui remember whether the Advanced checkbox was checked or not Also store the required version number in the details message. Ben Boeckel (3): Add test that CMake errors with empty libs Fix which string is checked for in the test XCode generation should fail if lang isn't known Bill Hoffman (5): Fix the name of the variable being tested. Fix KWStyle line length issues. Add a delay after untar on windows to make external project work on windows 7 Add a new line to the end of the generated main.cxx for the hpux compiler. Fix for bug #11274, VS10 custom commands that create files in INTDIR fix. Brad King (12): Evaluate OBJECT_DIR rule variable for executables ccmake: Fix search with '/' MinGW: Support long object file lists Document IMPORTED_NO_SONAME target property FindMPI: Recoginze -f flags from mpicc (#10771) Add module-dir flag for Compaq Visual Fortran (#11248) FindPythonInterp: Look for python2.7 interpreter VS10: Use $(IntDir) for per-source output directory (#11270) Reset platform/compiler info status for each language Remove trailing whitespace from Xcode generator source VS10: Skip targets with no linker language (#11230) VS10: Encode custom command comments for echo (#11283) Clinton Stimpson (1): Fix regression in cross-compile patches with finding Qt libs.
Re: [CMake] CMake 2.8.3-rc4 ready for testing!
On Fri, Oct 29, 2010 at 6:03 PM, David Cole david.c...@kitware.com wrote: The CMake 2.8.3 release candidate stream continues! You can find the source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D EXCEPT: There are not yet Irix or Sun pre-built binary installers available for CMake 2.8.3-rc4. There is a failing (HTML documentation validity checking) test on some platforms that appears to be unrelated to any CMake source code changes. That test failure is preventing the release building process from completing today on those platforms. If that issue clears up soon, I'll re-do the installers on those platforms. If not, just use rc3, or build from source. We'll address this before the final release. This will be the LAST release candidate for 2.8.3 unless a major regression is reported. So please try it on your projects and let us know right away about any problems. I know its probably too late for 2.8.3 but can someone please look at the following bug: http://cmake.org/Bug/view.php?id=11206 This affects me on every single (in house) release of my application. John ___ 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 2.8.3-rc4 ready for testing!
Am 30.10.2010 00:45, schrieb John Drescher: I know its probably too late for 2.8.3 but can someone please look at the following bug: http://cmake.org/Bug/view.php?id=11206 This affects me on every single (in house) release of my application. Same for this one: http://www.cmake.org/Bug/view.php?id=10798 There is already a patch available. Regards, Karl ___ 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 2.8.3-rc4 ready for testing!
I know its probably too late for 2.8.3 but can someone please look at the following bug: http://cmake.org/Bug/view.php?id=11206 This affects me on every single (in house) release of my application. A workaround is to do a monolithic install. SET(CPACK_MONOLITHIC_INSTALL 1) ... INCLUDE(CPack) Does that not work for you? Thanks. I will try that next build.. John ___ 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 2.8.3-rc4 ready for testing!
On Fri, Oct 29, 2010 at 8:17 PM, Karl Wallner cm...@karlwallner.de wrote: Am 30.10.2010 00:45, schrieb John Drescher: I know its probably too late for 2.8.3 but can someone please look at the following bug: http://cmake.org/Bug/view.php?id=11206 This affects me on every single (in house) release of my application. Same for this one: http://www.cmake.org/Bug/view.php?id=10798 There is already a patch available. I think you have the wrong bug # because that does not appear to have anything to do with the generation of NSIS packages. John ___ 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] Converting from autoconf to cmake problem
Hi All I am converting a code from configure.ac to cmake. Can any one please advice me about what is the corresponding macro for the following. I have searched the cmake wiki and documentation and didnot find any. AC_HEADER_STDBOOL AC_C_CONST AC_TYPE_PID_T AC_TYPE_SIZE_T AC_STRUCT_TM # Checks for library functions. AC_FUNC_CLOSEDIR_VOID AC_FUNC_ERROR_AT_LINE AC_FUNC_FORK AC_FUNC_MALLOC AC_FUNC_REALLOC AC_TYPE_SIGNAL AC_FUNC_VPRINTF Thank u Mina ___ 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] call already made makefile
Hi All I have an open source code that I use in my project. This open source code already has Makefile coded for it. I want to use cmake so that before it compile my project it first call the cmake of these open source code, which will compile it to .la library. Then using this library, it compile my code. Thanks for your help Mina From: mina adel elecengineer_m...@yahoo.com To: cmake@cmake.org Sent: Fri, October 29, 2010 11:45:25 PM Subject: Converting from autoconf to cmake problem Hi All I am converting a code from configure.ac to cmake. Can any one please advice me about what is the corresponding macro for the following. I have searched the cmake wiki and documentation and didnot find any. AC_HEADER_STDBOOL AC_C_CONST AC_TYPE_PID_T AC_TYPE_SIZE_T AC_STRUCT_TM # Checks for library functions. AC_FUNC_CLOSEDIR_VOID AC_FUNC_ERROR_AT_LINE AC_FUNC_FORK AC_FUNC_MALLOC AC_FUNC_REALLOC AC_TYPE_SIGNAL AC_FUNC_VPRINTF Thank u Mina ___ 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] Converting from autoconf to cmake problem
On Fri, Oct 29, 2010 at 8:45 PM, mina adel elecengineer_m...@yahoo.com wrote: Hi All I am converting a code from configure.ac to cmake. Can any one please advice me about what is the corresponding macro for the following. I have searched the cmake wiki and documentation and didnot find any. AC_HEADER_STDBOOL AC_C_CONST AC_TYPE_PID_T AC_TYPE_SIZE_T AC_STRUCT_TM # Checks for library functions. AC_FUNC_CLOSEDIR_VOID AC_FUNC_ERROR_AT_LINE AC_FUNC_FORK AC_FUNC_MALLOC AC_FUNC_REALLOC AC_TYPE_SIGNAL AC_FUNC_VPRINTF Read up on: check_function_exists() check_type_size() check_include_file() -- Aaron Turner http://synfin.net/ Twitter: @synfinatic http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix Windows Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin carpe diem quam minimum credula postero ___ 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.2-1136-ga4fafa1
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 a4fafa12fef5154423d36a9a99b6f829b054ae6c (commit)
via 4f8d752972a312f2132e293a414b1caf0a980577 (commit)
via 57eea54720a378712735b5ec6386cef745855325 (commit)
from 63529b1c6d7eb82b662a8fe672585c7339d12930 (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=a4fafa12fef5154423d36a9a99b6f829b054ae6c
commit a4fafa12fef5154423d36a9a99b6f829b054ae6c
Merge: 63529b1 4f8d752
Author: David Cole david.c...@kitware.com
AuthorDate: Fri Oct 29 09:07:53 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Oct 29 09:07:53 2010 -0400
Merge topic 'revert_fix_ctest_working_dir' into next
4f8d752 Revert When processing DartMeasurements use the tests working
directory.
57eea54 KWSys Nightly Date Stamp
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4f8d752972a312f2132e293a414b1caf0a980577
commit 4f8d752972a312f2132e293a414b1caf0a980577
Author: David Cole david.c...@kitware.com
AuthorDate: Fri Oct 29 09:03:56 2010 -0400
Commit: David Cole david.c...@kitware.com
CommitDate: Fri Oct 29 09:03:56 2010 -0400
Revert When processing DartMeasurements use the tests working directory.
This reverts commit 3f94c7cc395d3f20890a6c9a14aa2795a5a9ce87.
diff --git a/Source/CTest/cmCTestRunTest.cxx b/Source/CTest/cmCTestRunTest.cxx
index 76ff23a..6570d0e 100644
--- a/Source/CTest/cmCTestRunTest.cxx
+++ b/Source/CTest/cmCTestRunTest.cxx
@@ -264,17 +264,7 @@ bool cmCTestRunTest::EndTest(size_t completed, size_t
total, bool started)
{
*this-TestHandler-LogFile Test time = buf std::endl;
}
-
- // Set the working directory to the tests directory
- std::string oldpath = cmSystemTools::GetCurrentWorkingDirectory();
- cmSystemTools::ChangeDirectory(this-TestProperties-Directory.c_str());
-
this-DartProcessing();
-
- // restore working directory
- cmSystemTools::ChangeDirectory(oldpath.c_str());
-
-
// if this is doing MemCheck then all the output needs to be put into
// Output since that is what is parsed by cmCTestMemCheckHandler
if(!this-TestHandler-MemCheck started)
---
Summary of changes:
Source/CTest/cmCTestRunTest.cxx | 10 --
Source/kwsys/kwsysDateStamp.cmake |2 +-
2 files changed, 1 insertions(+), 11 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.2-1138-gc661741
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 c661741aad274d6e10f227c61a73400a865815f9 (commit)
via f4f8e5ad336d85d3dfd05fca7b097a75ad709c00 (commit)
from a4fafa12fef5154423d36a9a99b6f829b054ae6c (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=c661741aad274d6e10f227c61a73400a865815f9
commit c661741aad274d6e10f227c61a73400a865815f9
Merge: a4fafa1 f4f8e5a
Author: David Cole david.c...@kitware.com
AuthorDate: Fri Oct 29 14:18:31 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Oct 29 14:18:31 2010 -0400
Merge topic 'revert_fix_ctest_working_dir' into next
f4f8e5a Revert Revert When processing DartMeasurements ... working
directory.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f4f8e5ad336d85d3dfd05fca7b097a75ad709c00
commit f4f8e5ad336d85d3dfd05fca7b097a75ad709c00
Author: David Cole david.c...@kitware.com
AuthorDate: Fri Oct 29 14:17:01 2010 -0400
Commit: David Cole david.c...@kitware.com
CommitDate: Fri Oct 29 14:17:01 2010 -0400
Revert Revert When processing DartMeasurements ... working directory.
This reverts commit 4f8d752972a312f2132e293a414b1caf0a980577.
Bill and I have run the newly-failing test on dash8 today, and
it fails with and without this change. So, Bill wants to keep it.
So I'm reverting the revert I made earlier today... :-)
diff --git a/Source/CTest/cmCTestRunTest.cxx b/Source/CTest/cmCTestRunTest.cxx
index 6570d0e..76ff23a 100644
--- a/Source/CTest/cmCTestRunTest.cxx
+++ b/Source/CTest/cmCTestRunTest.cxx
@@ -264,7 +264,17 @@ bool cmCTestRunTest::EndTest(size_t completed, size_t
total, bool started)
{
*this-TestHandler-LogFile Test time = buf std::endl;
}
+
+ // Set the working directory to the tests directory
+ std::string oldpath = cmSystemTools::GetCurrentWorkingDirectory();
+ cmSystemTools::ChangeDirectory(this-TestProperties-Directory.c_str());
+
this-DartProcessing();
+
+ // restore working directory
+ cmSystemTools::ChangeDirectory(oldpath.c_str());
+
+
// if this is doing MemCheck then all the output needs to be put into
// Output since that is what is parsed by cmCTestMemCheckHandler
if(!this-TestHandler-MemCheck started)
---
Summary of changes:
Source/CTest/cmCTestRunTest.cxx | 10 ++
1 files changed, 10 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, release, updated. v2.8.2-623-ge5b50a9
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, release has been updated via e5b50a9ada44f83978cd7c153fdc0c48cf6a6057 (commit) via f54715170bf0df621ee6fa9f55a6769fb004f3fd (commit) via 57eea54720a378712735b5ec6386cef745855325 (commit) via 9bf662a92a8d0b6a215bc81cdbf61284f2d67694 (commit) via e561a46c1a852516dcbb1d435a4b8c6f95f636c3 (commit) via a3edde36ad870d669c054701bccf6c1d14d2d72c (commit) via 3f3f3e5f546fc953c899a6054f76b42851421b67 (commit) via ec93cd2ead86ea068577105a1903f92d604b6912 (commit) via 5b43d8f8b1cfd3e3acf1576b5bf2f910fb3c50db (commit) via 424ba550e5b06c68df753ef7a190c0308b31b1b7 (commit) via 70101ee8e7da58e5729fdc0fbb6a48cb3740ba9e (commit) via 48e80eb7246683f471f3886436020d34c784be86 (commit) via 01a90e9622bc74cf9d32e550f9342374b082a7fd (commit) via bee4802840607c22d9d37cda8464c17fcdf26529 (commit) via 8e550ba31e6b68d85f96bcb833d65e937a7139e2 (commit) via 16841987064cb79d3556034384458a36c4ceecef (commit) via 7db02e9b3a37e41f86431e0509b5935044e31b73 (commit) via c8f39193e01e15a13a37ca227f02a2e4472f3d8a (commit) via a74972402910610ab3ab62066d6b9e65b5202078 (commit) via be94c494eda5437bd7c026f6619d6ab040593e7a (commit) via 06b5eaa3cf7dc534415473eb1f3bfef191008999 (commit) via de81f2a4ee5f704ebd22875ba368d5623f919fa4 (commit) via 185582d5feb2925975cb669b0874a4a9cbe452d9 (commit) via 6e1282f840fe50707c928079465ab315f07a59fe (commit) via beeca11c9bcfd0cc211c8c73f4b00709c914eac3 (commit) via 91b5bc3efa814ba27cbc52280edc363f8991d0cc (commit) via e42160f3e057a338f5f5ac22bd4362b779a66254 (commit) via 3f94c7cc395d3f20890a6c9a14aa2795a5a9ce87 (commit) via 1f369a71c80d606c8610b7e79c8aeaecba81a87f (commit) from 144ee51760c33c0486ee907a83cb42dde9c05432 (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=e5b50a9ada44f83978cd7c153fdc0c48cf6a6057 commit e5b50a9ada44f83978cd7c153fdc0c48cf6a6057 Author: David Cole david.c...@kitware.com AuthorDate: Fri Oct 29 15:21:36 2010 -0400 Commit: David Cole david.c...@kitware.com CommitDate: Fri Oct 29 15:21:36 2010 -0400 CMake 2.8.3-rc4 diff --git a/CMakeLists.txt b/CMakeLists.txt index 0e46a62..f023b15 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -420,7 +420,7 @@ SET(CMake_VERSION_MAJOR 2) SET(CMake_VERSION_MINOR 8) SET(CMake_VERSION_PATCH 3) SET(CMake_VERSION_TWEAK 0) -SET(CMake_VERSION_RC 3) +SET(CMake_VERSION_RC 4) # Releases define a tweak level. IF(DEFINED CMake_VERSION_TWEAK) diff --git a/ChangeLog.manual b/ChangeLog.manual index cff9d06..7edab54 100644 --- a/ChangeLog.manual +++ b/ChangeLog.manual @@ -1,3 +1,26 @@ +Changes in CMake 2.8.3-rc4 (since 2.8.3-rc3) + +Bill Hoffman (1): + When processing DartMeasurements use the tests working directory. + +David Cole (2): + ExternalProject: No svn --username if empty (#11173) + Avoid problem reading jni.h on Macs. + +David Partyka (5): + Fixed appending PATH to dumpbin tool from growing without bounds. + Switch to CMAKE_PATH when doing PATH comparisons on Windows. + Remove unecessary TO_CMAKE_PATH for gp_cmd_dir. + Append the gp_tool path to the system PATH using native slashes. + Fixes to GetPrerequisites for cygwin + +Eric NOULARD (1): + CPackDeb Added several optional debian binary package fields + +Marcus D. Hanwell (2): + ENH: Added case for Python 2.7. + Fixed parallel build for generators with EXTRA. + Changes in CMake 2.8.3-rc3 (since 2.8.3-rc2) Alex Neundorf (4): http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f54715170bf0df621ee6fa9f55a6769fb004f3fd commit f54715170bf0df621ee6fa9f55a6769fb004f3fd Merge: 57eea54 144ee51 Author: David Cole david.c...@kitware.com AuthorDate: Fri Oct 29 15:17:46 2010 -0400 Commit: David Cole david.c...@kitware.com CommitDate: Fri Oct 29 15:17:46 2010 -0400 Merge branch 'release' --- Summary of changes: CMakeLists.txt |2 +- ChangeLog.manual | 23 +++ Modules/CPackDeb.cmake | 38 +- Modules/ExternalProject.cmake | 21 -- Modules/FindPythonLibs.cmake |2 +- Modules/GetPrerequisites.cmake | 51 +++-
[Cmake-commits] CMake branch, master, updated. v2.8.2-617-g2d3952d
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 2d3952d5210546ec4a861676b12edac249dd2f18 (commit) from 57eea54720a378712735b5ec6386cef745855325 (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=2d3952d5210546ec4a861676b12edac249dd2f18 commit 2d3952d5210546ec4a861676b12edac249dd2f18 Author: KWSys Robot kwro...@kitware.com AuthorDate: Sat Oct 30 00:01:06 2010 -0400 Commit: KWSys Robot kwro...@kitware.com CommitDate: Sat Oct 30 00:11:07 2010 -0400 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 8d44da0..53ab6aa 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 10) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 29) +SET(KWSYS_DATE_STAMP_DAY 30) --- 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
