[cmake-developers] Should CMAKE_LINK_DEPENDS_NO_SHARED be on by default?

Hi, CMAKE_LINK_DEPENDS_NO_SHARED was introduced in this cycle, but off by default. It seems useful enough to be on by default. Is there any reason not to enable it by default? Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at

[cmake-developers] [CMake 0013948]: Physfs version checking

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=13948 == Reported By:Vittorio Giovara Assigned To:

[cmake-developers] [CMake 0013949]: FAIL_REGULAR_EXPRESSION doesn't match beginning-of-line properly

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=13949 == Reported By:Dave Abrahams Assigned To:

Re: [CMake] Please critique my hello world CMakeLists.txt and Config.cmake

Hi Chris, On Sunday 24 February 2013, Chris Stankevitz wrote: Hello, Would you please critique my CMakeLists.txt and helloConfig.cmake.in files? I am particularly interested in comments that will help me fix these problems: - In helloConfig.cmake.in, I assume static libraries will be

Re: [CMake] Please critique my hello world CMakeLists.txt and Config.cmake

# You don't need the .in file. CMAKE_MINIMUM_REQUIRED(VERSION 2.8) PROJECT(hello) set (hello_VERSION_MAJOR 1) set (hello_VERSION_MINOR 1) ENABLE_TESTING() ADD_LIBRARY(hello hello.cpp) # This works just the same. Unless I'm missing something. SET(hello_INCLUDE_DIRS

Re: [CMake] Please critique my hello world CMakeLists.txt and Config.cmake

On Sun, Feb 24, 2013 at 2:23 AM, Ansis Māliņš ansis.mal...@gmail.comwrote: # You don't need the .in file. CMAKE_MINIMUM_REQUIRED(VERSION 2.8) PROJECT(hello) set (hello_VERSION_MAJOR 1) set (hello_VERSION_MINOR 1) ENABLE_TESTING() ADD_LIBRARY(hello hello.cpp) # This works just the

Re: [CMake] Please critique my hello world CMakeLists.txt and Config.cmake

On Sunday 24 February 2013, J Decker wrote: On Sun, Feb 24, 2013 at 2:23 AM, Ansis Māliņš ansis.mal...@gmail.comwrote: # You don't need the .in file. CMAKE_MINIMUM_REQUIRED(VERSION 2.8) PROJECT(hello) set (hello_VERSION_MAJOR 1) set (hello_VERSION_MINOR 1) ENABLE_TESTING()

Re: [CMake] CMake'ified Boost

Hi James, Make sens. Thanks for the follow up. Jc On Sat, Feb 23, 2013 at 5:06 AM, James Turner james.tur...@kdab.com wrote: No I'm simply using custom build and update commands to run bootstrap.sh and bjam with appropriate args. I suspect this is the piece the Xcode generator can't cope

Re: [CMake] Please critique my hello world CMakeLists.txt and Config.cmake

On Sun, Feb 24, 2013 at 2:20 AM, Alexander Neundorf neund...@kde.org wrote: * export the target (use the EXPORT option in install(TARGETS)) * the install this export, using install(EXPORT ...), this will install a cmake script file * include() this export-file in the Config.cmake file * use

Re: [CMake] Please critique my hello world CMakeLists.txt and Config.cmake

Hi Chris, On Sunday 24 February 2013, Chris Stankevitz wrote: On Sun, Feb 24, 2013 at 2:20 AM, Alexander Neundorf neund...@kde.org wrote: * export the target (use the EXPORT option in install(TARGETS)) * the install this export, using install(EXPORT ...), this will install a cmake script

Re: [CMake] Please critique my hello world CMakeLists.txt and Config.cmake

On Sun, Feb 24, 2013 at 12:37 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: github links: https://github.com/chrisstankevitz/hello https://github.com/chrisstankevitz/hello-client Maybe we'll start with the old way and get to the new way. Alex, Thank you again. I updated the

Re: [CMake] Toolchain file: Texas Instrument C6000 Code Generation Tools

Here you can find the toolchain file I created: https://projects.kde.org/projects/playground/mobile/wiki-reader/repository/revisions/master/entry/frontends/blackberry/cmake/Toolchain-C6X.cmake I think the issue boils down to this: root /home/lpapp/Projects/qt/skeleton/build #

[CMake] Patch utility is installed, but my ExternalProject build step fails to execute it

I'm trying to patch and build a Makefile-based project using the ExternalProject module. My patch command looks like this: PATCH_COMMAND patch -p1 -t -N ${CMAKE_CURRENT_SOURCE_DIR}/IntelDFP.patch When building, however, I get this: [ 10%] Performing patch step for 'IntelDFP'

Re: [CMake] Patch utility is installed, but my ExternalProject build step fails to execute it

Silly me... It was the quotes around the command. Sorry! On Sun, Feb 24, 2013 at 7:58 PM, David Brown cypher...@gmail.com wrote: I'm trying to patch and build a Makefile-based project using the ExternalProject module. My patch command looks like this: PATCH_COMMAND patch -p1 -t -N

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2316-g5cbeeef

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 5cbeeef9ccb4d6bc9a46b8a559c4f4eaa9c64958 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-747-ge597ba2

Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 073a09a..fdf42bb 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 10) -set(CMake_VERSION_TWEAK 20130224