Thompson, KT wrote:
Stephen Kelly wrote:
# GSL_INCLUDE_DIRS - Location of GSL header files.
# GSL_LIBRARIES - The GSL libraries.
I'm curious: Given that you provide IMPORTED targets, what would a user
need these variables for? Do you have a particular use-case that needs
them?
On 12/04/2014 02:29 PM, Stephen Kelly wrote:
# GSL_INCLUDE_DIRS - Location of GSL header files.
# GSL_LIBRARIES - The GSL libraries.
These are defined mostly as a courtesy for folks who don't use imported
targets yet.
Yes. They are useful at least when a FindXXX does not provide
On Thu, Dec 04, 2014 at 10:32:53AM -0500, Brad King wrote:
On 12/04/2014 10:09 AM, Erik Sjölund wrote:
I think it is a good idea to rename FindXerces to FindXercesC or
something similar, just to indicate that is about the C++
implementation.
Thanks for pointing out the distinct
Hallo,
does CMake run on 64-bit OS (e.g. Ubuntu 14.10 64-bit) without problems
or are there some workarounds necessary to get it run? If so, is there a
description available?
Greetings
Michael
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
does CMake run on 64-bit OS (e.g. Ubuntu 14.10 64-bit) without problems
or are there some workarounds necessary to get it run? If so, is there a
description available?
I have not had any real issue with cmake (32 or 64 bit binary) on 64
bit linux or windows.
John
--
Powered by
Hallo Michael,
does CMake run on 64-bit OS (e.g. Ubuntu 14.10 64-bit) without problems or
are there some workarounds necessary
to get it run? If so, is there a description available?
CMake runs smoothly on much more exotic than 64-bit OS, so what makes you think
it wouldn't work on those?
Hi: I'm trying to create a 64-bit Visual Studio 12 (aka 2013) project with
CMake 3.0.2. My CMakeLists.txt file is really simple:
cmake_minimum_required( VERSION 3.0 )
project( cmc CXX )
# What compiler did we find?
message( C++: ${CMAKE_CXX_COMPILER} )
From a windows shell I do:
c:\Program
I have a global include file used by all of the CMakeLists.txt files in my
project. In it, I set the value of CMAKE_INSTALL_PREFIX, as well as a
number of other variables and functions.
In my CMakeLists.txt file, I had this:
cmake_minimum_require(VERSION 2.8.4)
include(global.inc)
I find it's better to define CMAKE_INSTALL_PREFIX on the command line when
building
I do have this bit of code...
IF(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
SET(CMAKE_INSTALL_PREFIX
${CMAKE_BINARY_DIR}/../${CMAKE_BUILD_TYPE}_out CACHE PATH Install
default 'out' in this directory.
Hello all,
I’m trying to use the docopt.cpp parser for my project[1]:
https://github.com/docopt/docopt.cpp https://github.com/docopt/docopt.cpp
The usual invocation to build works:
┌─[adam][Hapkido][±][docopt ✗][~/CDT-plusplus/src/docopt]
└─▪ clang++ --std=c++11 --stdlib=libc++ -I . docopt.cpp
I should note that I'm doing an out of source build, and that for my
project the following line works:
┌─[*adam*][Hapkido][*±*][docopt *✓*][~/CDT-plusplus/build]
└─▪ clang++ --std=c++11 --stdlib=libc++ -I ../src/docopt
../src/docopt/docopt.cpp ../src/cdt-docopt.cpp -o cdt_docopt
On Thu, Dec 4,
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 72edefcf8a04d5ee9404cccd33090dd0d2025005 (commit)
via
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 ba98442610024cf50cb407a5cc09f25096a7c79a (commit)
via
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 5484291dfcc5cc17c97881711d71b5f1cadfde6a (commit)
via
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 1c104c019a23392563befb3564dd5c679cc2c585 (commit)
via
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 466abce5f276f99678137ea06f6a59fdf26d563c (commit)
via
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 d08809ae30abab134b1eb375124eb08f1c5b1bde (commit)
via
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 2928ab107e096ade189d410433311bab7298740b (commit)
via
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 470c549c622d0be3ae63945e40a1cad85923 (commit)
via
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 09f797c19ccf8fb5e4241008e9845ba9ab7200bf (commit)
via
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 d91dc129c690510c32b10bbcb8efe17ebed72455 (commit)
via
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 264d65529e0487d0af19fad578a92a28d18e770b (commit)
via
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 cdcb21844397efd56862fd4fad67f4b4d8045f6b (commit)
via
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 da1ba8eb418d6f08b2d21892ee83a82626da4663 (commit)
via
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 6fe28452898c3fea0bf021cacfe0885686e517dd (commit)
via
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 3bce2ae4240a701c7e05cd05514d0ae9443ce778 (commit)
via
20141204)
+set(CMake_VERSION_PATCH 20141205)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
27 matches
Mail list logo
