Re: [cmake-developers] Targets for FindGTK2.cmake
Daniele,
Your changes look fine to me although my experience with imported targets
is limited so someone with more experience should review your changes there.
I'm not sure if there is a way to develop automated unit tests and mark
them to not run by default. That would be useful for regression testing of
modules even if it the tests had to be run manually. Would be a good
question for some of the more active developers (read: not me) :).
If compilation of the hello world examples is still working for you, that
would be a pretty good sign you didn't break anything.
https://developer.gnome.org/gtk-tutorial/stable/c39.html#SEC-HELLOWORLD
https://developer.gnome.org/gtkmm-tutorial/2.24/sec-helloworld.html.en
Here's some old test code I had lying around which obviously could be much
improved.
*CMakeLists.txt*
project(foo)
cmake_minimum_required(VERSION 2.6)
set(GTK2_DEBUG TRUE)
set(CMAKE_MODULE_PATH ${CMAKE_CURRENT_SOURCE_DIR})
find_package(GTK2 2.16 REQUIRED gtk glade gtkmm glademm)
message(GTK2_INCLUDE_DIRS = ${GTK2_INCLUDE_DIRS})
message(GTK2_LIBRARIES = ${GTK2_LIBRARIES})
include_directories(${GTK2_INCLUDE_DIRS})
add_executable(bar bar.cc helloworld.cc)
target_link_libraries(bar ${GTK2_LIBRARIES}
*bar.cc:*
#include gtkmm/main.h
#include helloworld.h
int main (int argc, char *argv[])
{
Gtk::Main kit(argc, argv);
HelloWorld helloworld;
//Shows the window and returns when it is closed.
Gtk::Main::run(helloworld);
return 0;
}
*helloworld.cc*
#include helloworld.h
#include iostream
HelloWorld::HelloWorld()
: m_button(Hello World) // creates a new button with label Hello
World.
{
// Sets the border width of the window.
set_border_width(10);
// When the button receives the clicked signal, it will call the
// on_button_clicked() method defined below.
m_button.signal_clicked().connect(sigc::mem_fun(*this,
HelloWorld::on_button_clicked));
// This packs the button into the Window (a container).
add(m_button);
// The final step is to display this newly created widget...
m_button.show();
}
HelloWorld::~HelloWorld()
{
}
void HelloWorld::on_button_clicked()
{
std::cout Hello World std::endl;
}
*helloworld.h*
#ifndef GTKMM_EXAMPLE_HELLOWORLD_H
#define GTKMM_EXAMPLE_HELLOWORLD_H
#include gtkmm/button.h
#include gtkmm/window.h
class HelloWorld : public Gtk::Window
{
public:
HelloWorld();
virtual ~HelloWorld();
protected:
//Signal handlers:
void on_button_clicked();
//Member widgets:
Gtk::Button m_button;
};
#endif // GTKMM_EXAMPLE_HELLOWORLD_H
On Mon, Aug 5, 2013 at 11:00 AM, Daniele E. Domenichelli
daniele.domeniche...@gmail.com wrote:
Hello all,
I'd like to introduce imported targets in FindGTK2.cmake, in a similar
manner as they are used in FindQT4.cmake.
The aim is to be able to do something like:
find_package(GTK2 gtk gtkmm)
target_link_libraries(target GTK2::gtkmm)
(In the future I want to handle dependencies on modules as well, at the
moment I think that if you don't include the gtk module it will not work)
If you want to review my changes, you can checkout the FindGTK2-targets
topic. I tested it on Windows and Linux, but unfortunately there are not
unit tests afaik.
Cheers,
Daniele
--
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
--
Philip Lowman
--
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-commits] CMake branch, next, updated. v2.8.9-995-gdd7e797
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 dd7e7979b4c7a28ecf13c5ef7e77fc756998be55 (commit)
via 0594bee578fbe017f8ef194557b4cddfa12b7dae (commit)
via 8093f6cedea37b488a1e7f61bc363e149fa43428 (commit)
via 06638039aaa01c5431e6b4f0c153390afbe82c46 (commit)
via b74267745b012e1f3769ea5a7802c79f5480852b (commit)
from 19321e4f3055898ccb816bcdc3747f60c40d2f1b (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=dd7e7979b4c7a28ecf13c5ef7e77fc756998be55
commit dd7e7979b4c7a28ecf13c5ef7e77fc756998be55
Merge: 19321e4 0594bee
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Thu Oct 4 01:10:25 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Oct 4 01:10:25 2012 -0400
Merge topic 'FindGTK2Fixes' into next
0594bee FindGTK2: Update local changelog
8093f6c FindGTK2: #12596 Missing paths for FindGTK2 on NetBSD
0663803 FindGTK2: #12049 fix detection of header files on multiarch systems
b742677 FindGTK2: Rollback lib64 changes which broke header file finding
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0594bee578fbe017f8ef194557b4cddfa12b7dae
commit 0594bee578fbe017f8ef194557b4cddfa12b7dae
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Wed Oct 3 05:03:53 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Wed Oct 3 05:03:53 2012 -0400
FindGTK2: Update local changelog
diff --git a/Modules/FindGTK2.cmake b/Modules/FindGTK2.cmake
index b9be78a..517a9ac 100644
--- a/Modules/FindGTK2.cmake
+++ b/Modules/FindGTK2.cmake
@@ -54,7 +54,7 @@
#=
# Copyright 2009 Kitware, Inc.
-# Copyright 2008-2009 Philip Lowman phi...@yhbt.com
+# Copyright 2008-2012 Philip Lowman phi...@yhbt.com
#
# Distributed under the OSI-approved BSD License (the License);
# see accompanying file Copyright.txt for details.
@@ -66,10 +66,13 @@
# (To distribute this file outside of CMake, substitute the full
# License text for the above reference.)
+# Version 1.4 (10/4/2012) (CMake 2.8.10)
+# * 12596: Missing paths for FindGTK2 on NetBSD
+# * 12049: Fixed detection of GTK include files in the lib folder on
+#multiarch systems.
# Version 1.3 (11/9/2010) (CMake 2.8.4)
# * 11429: Add support for detecting GTK2 built with Visual Studio 10.
#Thanks to Vincent Levesque for the patch.
-
# Version 1.2 (8/30/2010) (CMake 2.8.3)
# * Merge patch for detecting gdk-pixbuf library (split off
# from core GTK in 2.21). Thanks to Vincent Untz for the patch
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8093f6cedea37b488a1e7f61bc363e149fa43428
commit 8093f6cedea37b488a1e7f61bc363e149fa43428
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Wed Oct 3 04:57:45 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Wed Oct 3 04:57:45 2012 -0400
FindGTK2: #12596 Missing paths for FindGTK2 on NetBSD
diff --git a/Modules/FindGTK2.cmake b/Modules/FindGTK2.cmake
index 119ad0e..b9be78a 100644
--- a/Modules/FindGTK2.cmake
+++ b/Modules/FindGTK2.cmake
@@ -211,6 +211,8 @@ function(_GTK2_FIND_INCLUDE_DIR _var _hdr)
/sw/lib
/opt/local/include
/opt/local/lib
+/usr/pkg/lib
+/usr/pkg/include/glib
$ENV{GTKMM_BASEPATH}/include
$ENV{GTKMM_BASEPATH}/lib
[HKEY_CURRENT_USER\\SOFTWARE\\gtkmm\\2.4;Path]/include
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=06638039aaa01c5431e6b4f0c153390afbe82c46
commit 06638039aaa01c5431e6b4f0c153390afbe82c46
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Wed Oct 3 04:52:35 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Wed Oct 3 04:52:35 2012 -0400
FindGTK2: #12049 fix detection of header files on multiarch systems
diff --git a/Modules/FindGTK2.cmake b/Modules/FindGTK2.cmake
index 2373422..119ad0e 100644
--- a/Modules/FindGTK2.cmake
+++ b/Modules/FindGTK2.cmake
@@ -190,8 +190,15 @@ function(_GTK2_FIND_INCLUDE_DIR _var _hdr)
include suffixes = ${_suffixes})
endif()
+if(CMAKE_LIBRARY_ARCHITECTURE)
+ set(_gtk2_arch_dir /usr/lib/${CMAKE_LIBRARY_ARCHITECTURE})
+ if(GTK2_DEBUG)
+message(STATUS Adding ${_gtk2_arch_dir} to search path for multiarch
support)
+ endif()
+endif()
find_path(${_var} ${_hdr}
PATHS
+${_gtk2_arch_dir}
/usr/local/lib64
/usr/local/lib
/usr/lib64
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h
[Cmake-commits] CMake branch, next, updated. v2.8.9-691-g9a49bd7
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 9a49bd7107b74669baf8dc6b29985ca4fe0f301c (commit)
via a7227804984383ed864ba1b2b6081d28b103ddff (commit)
from 15a3d70fd097768783ac7d58cb5167d852c78f81 (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=9a49bd7107b74669baf8dc6b29985ca4fe0f301c
commit 9a49bd7107b74669baf8dc6b29985ca4fe0f301c
Merge: 15a3d70 a722780
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Fri Sep 21 23:15:48 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Sep 21 23:15:48 2012 -0400
Merge topic 'DetermineVsServicePack2012' into next
a722780 CMakeDetermineVSServicePack: Visual Studio 2012 added
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a7227804984383ed864ba1b2b6081d28b103ddff
commit a7227804984383ed864ba1b2b6081d28b103ddff
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Fri Sep 21 23:11:18 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Fri Sep 21 23:11:18 2012 -0400
CMakeDetermineVSServicePack: Visual Studio 2012 added
diff --git a/Modules/CMakeDetermineVSServicePack.cmake
b/Modules/CMakeDetermineVSServicePack.cmake
index 33f0141..98e5bb8 100644
--- a/Modules/CMakeDetermineVSServicePack.cmake
+++ b/Modules/CMakeDetermineVSServicePack.cmake
@@ -9,6 +9,7 @@
#vc90sp1
#vc100
#vc100sp1
+#vc110
#
# Usage:
# ===
@@ -54,6 +55,8 @@ function(_DetermineVSServicePackFromCompiler _OUT_VAR
_cl_version)
set(_version vc100)
elseif(${_cl_version} VERSION_EQUAL 16.00.40219.01)
set(_version vc100sp1)
+ elseif(${_cl_version} VERSION_EQUAL 17.00.50727.1)
+ set(_version vc110)
else()
set(_version )
endif()
---
Summary of changes:
Modules/CMakeDetermineVSServicePack.cmake |3 +++
1 files changed, 3 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.9-141-g69fa443
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 69fa443a58699281437577b4ba3a037592ed158a (commit)
via dd60ed2f4f523fecf2d9757d6b52f2bd0fa2bfac (commit)
via 224b5dea785d20a9054a2b7fb9e737c106084879 (commit)
from f9c04e2f1738d06b4a23549b32f5a7a6e708abcc (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=69fa443a58699281437577b4ba3a037592ed158a
commit 69fa443a58699281437577b4ba3a037592ed158a
Merge: f9c04e2 dd60ed2
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Aug 18 17:05:35 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sat Aug 18 17:05:35 2012 -0400
Merge topic 'FindOpenSceneGraph_13094' into next
dd60ed2 Merge topic 'lib64-cleanup' into FindOpenSceneGraph_13094
224b5de FindOpenSceneGraph: CMake variable OSG_DIR influences detection now
too
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dd60ed2f4f523fecf2d9757d6b52f2bd0fa2bfac
commit dd60ed2f4f523fecf2d9757d6b52f2bd0fa2bfac
Merge: 224b5de cfe4ac4
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Aug 18 17:03:18 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sat Aug 18 17:03:18 2012 -0400
Merge topic 'lib64-cleanup' into FindOpenSceneGraph_13094
Resolved a few conflicts due to changes made in 13094 to paths
Conflicts:
Modules/FindOpenThreads.cmake
Modules/Findosg_functions.cmake
diff --cc Modules/FindOpenThreads.cmake
index 7668107,36247c1..e059960
--- a/Modules/FindOpenThreads.cmake
+++ b/Modules/FindOpenThreads.cmake
@@@ -58,15 -53,14 +58,15 @@@
find_path(OPENTHREADS_INCLUDE_DIR OpenThreads/Thread
HINTS
- $ENV{OPENTHREADS_INCLUDE_DIR}
- $ENV{OPENTHREADS_DIR}
- $ENV{OSG_INCLUDE_DIR}
- $ENV{OSG_DIR}
- $ENV{OSGDIR}
- $ENV{OpenThreads_ROOT}
- $ENV{OSG_ROOT}
-# enough environment variables?
+ ENV OPENTHREADS_INCLUDE_DIR
+ ENV OPENTHREADS_DIR
+ ENV OSG_INCLUDE_DIR
+ ENV OSG_DIR
+ ENV OSGDIR
+ ENV OpenThreads_ROOT
+ ENV OSG_ROOT
+${OPENTHREADS_DIR}
+${OSG_DIR}
PATHS
/sw # Fink
/opt/local # DarwinPorts
@@@ -80,15 -74,13 +80,15 @@@
find_library(OPENTHREADS_LIBRARY
NAMES OpenThreads OpenThreadsWin32
HINTS
- $ENV{OPENTHREADS_LIBRARY_DIR}
- $ENV{OPENTHREADS_DIR}
- $ENV{OSG_LIBRARY_DIR}
- $ENV{OSG_DIR}
- $ENV{OSGDIR}
- $ENV{OpenThreads_ROOT}
- $ENV{OSG_ROOT}
+ ENV OPENTHREADS_LIBRARY_DIR
+ ENV OPENTHREADS_DIR
+ ENV OSG_LIBRARY_DIR
+ ENV OSG_DIR
+ ENV OSGDIR
+ ENV OpenThreads_ROOT
+ ENV OSG_ROOT
+${OPENTHREADS_DIR}
+${OSG_DIR}
PATHS
/sw
/opt/local
@@@ -101,16 -93,14 +101,16 @@@
find_library(OPENTHREADS_LIBRARY_DEBUG
NAMES OpenThreadsd OpenThreadsWin32d
HINTS
- $ENV{OPENTHREADS_DEBUG_LIBRARY_DIR}
- $ENV{OPENTHREADS_LIBRARY_DIR}
- $ENV{OPENTHREADS_DIR}
- $ENV{OSG_LIBRARY_DIR}
- $ENV{OSG_DIR}
- $ENV{OSGDIR}
- $ENV{OpenThreads_ROOT}
- $ENV{OSG_ROOT}
+ ENV OPENTHREADS_DEBUG_LIBRARY_DIR
+ ENV OPENTHREADS_LIBRARY_DIR
+ ENV OPENTHREADS_DIR
+ ENV OSG_LIBRARY_DIR
+ ENV OSG_DIR
+ ENV OSGDIR
+ ENV OpenThreads_ROOT
+ ENV OSG_ROOT
+${OPENTHREADS_DIR}
+${OSG_DIR}
PATHS
/sw
/opt/local
diff --cc Modules/Findosg_functions.cmake
index e65e858,3a8a0f5..2e90837
--- a/Modules/Findosg_functions.cmake
+++ b/Modules/Findosg_functions.cmake
@@@ -27,12 -26,10 +27,12 @@@ function(OSG_FIND_PATH module header
# Try the user's environment request before anything else.
find_path(${module_uc}_INCLUDE_DIR ${header}
HINTS
- $ENV{${module_uc}_DIR}
- $ENV{OSG_DIR}
- $ENV{OSGDIR}
- $ENV{OSG_ROOT}
+ ENV ${module_uc}_DIR
+ ENV OSG_DIR
+ ENV OSGDIR
+ ENV OSG_ROOT
+${${module_uc}_DIR}
+${OSG_DIR}
PATH_SUFFIXES include
PATHS
/sw # Fink
@@@ -53,13 -50,11 +53,13 @@@ function(OSG_FIND_LIBRARY module librar
find_library(${module_uc}_LIBRARY
NAMES ${library}
HINTS
- $ENV{${module_uc}_DIR}
- $ENV{OSG_DIR}
- $ENV{OSGDIR}
- $ENV{OSG_ROOT}
+ ENV ${module_uc}_DIR
+ ENV OSG_DIR
+ ENV
[Cmake-commits] CMake branch, next, updated. v2.8.9-144-gfd7fa92
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 fd7fa92fb1e2d7dd87c526a1855acf34b01bf41c (commit)
via ad30210ccf4c8d17ef4d3f01a2094b5dc5e020d7 (commit)
via ea2fcabbaf424d5270243f6e69a4093e07c43b00 (commit)
from 69fa443a58699281437577b4ba3a037592ed158a (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=fd7fa92fb1e2d7dd87c526a1855acf34b01bf41c
commit fd7fa92fb1e2d7dd87c526a1855acf34b01bf41c
Merge: 69fa443 ad30210
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Aug 18 17:59:51 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sat Aug 18 17:59:51 2012 -0400
Merge topic 'FindGTK2_12306' into next
ad30210 FindGTK2: Add GTK2_CAIROMMCONFIG_INCLUDE_DIR for cairommconfig.h
ea2fcab CMake Nightly Date Stamp
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ad30210ccf4c8d17ef4d3f01a2094b5dc5e020d7
commit ad30210ccf4c8d17ef4d3f01a2094b5dc5e020d7
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Aug 18 17:56:46 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sat Aug 18 17:56:46 2012 -0400
FindGTK2: Add GTK2_CAIROMMCONFIG_INCLUDE_DIR for cairommconfig.h
diff --git a/Modules/FindGTK2.cmake b/Modules/FindGTK2.cmake
index d10b419..05fe509 100644
--- a/Modules/FindGTK2.cmake
+++ b/Modules/FindGTK2.cmake
@@ -469,6 +469,7 @@ foreach(_GTK2_component ${GTK2_FIND_COMPONENTS})
_GTK2_FIND_LIBRARY(GTK2_GTKMM_LIBRARY gtkmm true true)
_GTK2_FIND_INCLUDE_DIR(GTK2_CAIROMM_INCLUDE_DIR cairomm/cairomm.h)
+_GTK2_FIND_INCLUDE_DIR(GTK2_CAIROMMCONFIG_INCLUDE_DIR cairommconfig.h)
_GTK2_FIND_LIBRARY(GTK2_CAIROMM_LIBRARY cairomm true true)
_GTK2_FIND_INCLUDE_DIR(GTK2_PANGOMM_INCLUDE_DIR pangomm.h)
---
Summary of changes:
Modules/FindGTK2.cmake|1 +
Source/CMakeVersion.cmake |2 +-
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
Re: [cmake-developers] FindBoost: boost version vs cached variables
Andriy,
Sorry for the delay in responding. I did some additional testing tonight
and merged the changes into next. Thanks again for reporting this.
On Thu, Jun 21, 2012 at 1:12 PM, Andriy Gapon a...@icyb.net.ua wrote:
on 20/06/2012 07:39 Philip Lowman said the following:
I wasn't aware of this defect. Thanks for pointing it out.
Could you give the attached version a whirl? I got rid of the odd
caching
behavior (not sure exactly why FindBoost was written that way to begin
with) and
this appears to resolve the bug.
Yes, thank you very much!
With the attached version the Boost detection works as expected. And just
in
case: I haven't run into any regressions with a real/larger project.
On Tue, Jun 19, 2012 at 10:54 AM, Andriy Gapon a...@icyb.net.ua
mailto:a...@icyb.net.ua wrote:
FindBoost.cmake currently (as of CMake 2.8.8) has fairly simply
logic to see if
Boost is already found and the relevant variables are cached.
Essentially that logic verifies that Boost_INCLUDE_DIR and
Boost_${COMPONENT}_FOUND variables are set.
What it doesn't do is validate that the found/cached Boost version
satisfies the
requested version. At least it seems so. And this is amplified by
the fact that
the variables remained set and cached even if the original search
for Boost
couldn't find a satisfactory version.
A sample CMakeLists.txt file:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
PROJECT(boost_test)
FIND_PACKAGE(Boost 1.51)
IF(Boost_FOUND)
MESSAGE(Boost 1.51 found!!!)
ELSE(Boost_FOUND)
MESSAGE(Boost 1.51 not found...)
ENDIF(Boost_FOUND)
As you know, Boost 1.51 doesn't exist yet.
But on a system with Boost 1.48.0 installed I get:
$ cmake .
-- The C compiler identification is GNU 4.2.1
-- The CXX compiler identification is GNU 4.2.1
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Could NOT find Boost
Boost 1.51 not found...
-- Configuring done
-- Generating done
-- Build files have been written to: /home/avg/tmp/boost-test
So far so good. Running cmake again:
$ cmake .
Boost 1.51 found!!!
-- Configuring done
-- Generating done
-- Build files have been written to: /home/avg/tmp/boost-test
Adding SET(Boost_DEBUG TRUE) I get the following for a secondary run:
$ cmake .
-- [ /usr/local/share/cmake/Modules/FindBoost.cmake:519 ] boost
1.48.0 is already
in the cache. To view debugging messages, please clear the cache.
Boost 1.51 found!!!
-- Configuring done
-- Generating done
-- Build files have been written to: /home/avg/tmp/boost-test
So FindBoost correctly knows that it has seen boost 1.48.0, but it
misreports that
boost 1.51 is available.
--
Andriy Gapon
--
Powered by www.kitware.com http://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
--
Philip Lowman
--
Andriy Gapon
--
Philip Lowman
--
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-commits] CMake branch, next, updated. v2.8.8-3351-g98dd8b9
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 98dd8b9c3c238043a96ae164136637df443b2db0 (commit)
via ca90709fd67dc0a83ca6f75d793eab38967745a3 (commit)
via accd0428f4f76feef5122117699b196d04dca84a (commit)
from 03f870a7660880db3792ea4a9b3c62a8a5cb802c (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=98dd8b9c3c238043a96ae164136637df443b2db0
commit 98dd8b9c3c238043a96ae164136637df443b2db0
Merge: 03f870a ca90709
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Mon Jul 2 00:13:03 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Jul 2 00:13:03 2012 -0400
Merge topic 'FindBoostNotFoundBug' into next
ca90709 FindBoost: Future proof to 1.56
accd042 FindBoost: Fix bug where Boost_FOUND could be false when version
specified
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ca90709fd67dc0a83ca6f75d793eab38967745a3
commit ca90709fd67dc0a83ca6f75d793eab38967745a3
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Jun 30 03:40:37 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sat Jun 30 03:40:37 2012 -0400
FindBoost: Future proof to 1.56
diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index 4826da6..ad6b159 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -66,7 +66,8 @@
# 1.36, 1.36.0, 1.36.1, 1.37, 1.37.0, 1.38, 1.38.0, 1.39, 1.39.0,
# 1.40, 1.40.0, 1.41, 1.41.0, 1.42, 1.42.0, 1.43, 1.43.0, 1.44, 1.44.0,
# 1.45, 1.45.0, 1.46, 1.46.0, 1.46.1, 1.47, 1.47.0, 1.48, 1.48.0,
-# 1.49, 1.49.0, 1.50, 1.50.0
+# 1.49, 1.49.0, 1.50, 1.50.0, 1.51, 1.51.0, 1.52, 1.52.0,
+# 1.53, 1.53.0, 1.54, 1.54.0, 1.55, 1.55.0, 1.56, 1.56.0
#
# NOTE: If you add a new major 1.x version in Boost_ADDITIONAL_VERSIONS you
should
# add both 1.x and 1.x.0 as shown above. Official Boost include directories
@@ -528,6 +529,8 @@ else(Boost_FIND_VERSION_EXACT)
# The user has not requested an exact version. Among known
# versions, find those that are acceptable to the user request.
set(_Boost_KNOWN_VERSIONS ${Boost_ADDITIONAL_VERSIONS}
+1.56.0 1.56 1.55.0 1.55 1.54.0 1.54
+1.53.0 1.53 1.52.0 1.52 1.51.0 1.51
1.50.0 1.50 1.49.0 1.49 1.48.0 1.48 1.47.0 1.47 1.46.1
1.46.0 1.46 1.45.0 1.45 1.44.0 1.44 1.43.0 1.43 1.42.0
1.42
1.41.0 1.41 1.40.0 1.40 1.39.0 1.39 1.38.0 1.38 1.37.0
1.37
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=accd0428f4f76feef5122117699b196d04dca84a
commit accd0428f4f76feef5122117699b196d04dca84a
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Jun 30 03:33:56 2012 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sat Jun 30 03:33:56 2012 -0400
FindBoost: Fix bug where Boost_FOUND could be false when version specified
Fixes a problem where when specifying a version number without the REQUIRED
parameter, Boost_FOUND would be true on the first configure but false on
subsequent configures.
diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index 7504ea4..4826da6 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -246,7 +246,7 @@
# Copyright 2007 Wengo
# Copyright 2007 Mike Jackson
# Copyright 2008 Andreas Pakulat ap...@gmx.de
-# Copyright 2008-2010 Philip Lowman phi...@yhbt.com
+# Copyright 2008-2012 Philip Lowman phi...@yhbt.com
#
# Distributed under the OSI-approved BSD License (the License);
# see accompanying file Copyright.txt for details.
@@ -298,6 +298,7 @@ endif()
#---
# FindBoost functions macros
#
+
#
# Check the existence of the libraries.
@@ -428,18 +429,95 @@ function(_Boost_CHECK_SPELLING _var)
endif()
endfunction()
+# Guesses Boost's compiler prefix used in built library names
+# Returns the guess by setting the variable pointed to by _ret
+function(_Boost_GUESS_COMPILER_PREFIX _ret)
+ if(${CMAKE_CXX_COMPILER_ID} STREQUAL Intel
+ OR ${CMAKE_CXX_COMPILER} MATCHES icl
+ OR ${CMAKE_CXX_COMPILER} MATCHES icpc)
+if(WIN32)
+ set (_boost_COMPILER -iw)
+else()
+ set (_boost_COMPILER -il)
+endif()
+ elseif (MSVC11)
+set(_boost_COMPILER -vc110)
+ elseif (MSVC10)
+set(_boost_COMPILER -vc100)
+ elseif (MSVC90)
+set(_boost_COMPILER -vc90)
+ elseif (MSVC80)
+set(_boost_COMPILER -vc80)
+ elseif (MSVC71)
+set(_boost_COMPILER -vc71)
+ elseif (MSVC70) # Good luck!
+set(_boost_COMPILER -vc7) # yes, this is correct
+ elseif (MSVC60) # Good luck!
+set(_boost_COMPILER -vc6
[Cmake-commits] CMake branch, next, updated. v2.8.7-2568-ge0a918e
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 e0a918e0996bfbde1bf511486c7810359b2731e0 (commit) via 815485e9333e07fbbac66bfc415fa2ae5cbe8a85 (commit) from 5994d9dab7647a44d88bc6e7aadee60e379daf9f (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=e0a918e0996bfbde1bf511486c7810359b2731e0 commit e0a918e0996bfbde1bf511486c7810359b2731e0 Merge: 5994d9d 815485e Author: Philip Lowman phi...@yhbt.com AuthorDate: Sat Feb 11 18:55:00 2012 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Sat Feb 11 18:55:00 2012 -0500 Merge topic 'alsa_prefix_include_fix' into next 815485e FindALSA: Fix incorrect include path detection http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=815485e9333e07fbbac66bfc415fa2ae5cbe8a85 commit 815485e9333e07fbbac66bfc415fa2ae5cbe8a85 Author: Philip Lowman phi...@yhbt.com AuthorDate: Sat Feb 11 18:51:22 2012 -0500 Commit: Philip Lowman phi...@yhbt.com CommitDate: Sat Feb 11 18:51:22 2012 -0500 FindALSA: Fix incorrect include path detection This fixes a bug where the alsa include path was being detected incorrectly (e.g. /usr/local/include/alsa instead of /usr/local/include) diff --git a/Modules/FindALSA.cmake b/Modules/FindALSA.cmake index ec6e3a8..41c4e30 100644 --- a/Modules/FindALSA.cmake +++ b/Modules/FindALSA.cmake @@ -12,8 +12,8 @@ # #= -# Copyright 2009 Kitware, Inc. -# Copyright 2009 Philip Lowman phi...@yhbt.com +# Copyright 2009-2011 Kitware, Inc. +# Copyright 2009-2011 Philip Lowman phi...@yhbt.com # # Distributed under the OSI-approved BSD License (the License); # see accompanying file Copyright.txt for details. @@ -25,8 +25,9 @@ # (To distribute this file outside of CMake, substitute the full # License text for the above reference.) -find_path(ALSA_INCLUDE_DIR NAMES asoundlib.h - PATH_SUFFIXES alsa +# Try to find asoundlib.h both in PREFIX/include/alsa and PREFIX/include +# since older versions of ALSA put it in include directly +find_path(ALSA_INCLUDE_DIR NAMES alsa/asoundlib.h asoundlib.h DOC The ALSA (asound) include directory ) --- Summary of changes: Modules/FindALSA.cmake |9 + 1 files changed, 5 insertions(+), 4 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.7-2570-ga2e8cbf
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 a2e8cbf70204b2c9fec6414d224be2da9fd2cf5f (commit)
via 11cf52ebce8ee9bef4e79cfee3043016387f75b0 (commit)
from e0a918e0996bfbde1bf511486c7810359b2731e0 (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=a2e8cbf70204b2c9fec6414d224be2da9fd2cf5f
commit a2e8cbf70204b2c9fec6414d224be2da9fd2cf5f
Merge: e0a918e 11cf52e
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Feb 11 20:40:37 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sat Feb 11 20:40:37 2012 -0500
Merge topic 'alsa_prefix_include_fix' into next
11cf52e FindALSA: Fix version detection after last commit
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=11cf52ebce8ee9bef4e79cfee3043016387f75b0
commit 11cf52ebce8ee9bef4e79cfee3043016387f75b0
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sat Feb 11 20:37:48 2012 -0500
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sat Feb 11 20:37:48 2012 -0500
FindALSA: Fix version detection after last commit
Also, removed detection of header file from PREFIX/include.
Can't find any example in alsa source code where the library headers
were installed outside of PREFIX/include/alsa.
diff --git a/Modules/FindALSA.cmake b/Modules/FindALSA.cmake
index 41c4e30..4a0b693 100644
--- a/Modules/FindALSA.cmake
+++ b/Modules/FindALSA.cmake
@@ -25,9 +25,7 @@
# (To distribute this file outside of CMake, substitute the full
# License text for the above reference.)
-# Try to find asoundlib.h both in PREFIX/include/alsa and PREFIX/include
-# since older versions of ALSA put it in include directly
-find_path(ALSA_INCLUDE_DIR NAMES alsa/asoundlib.h asoundlib.h
+find_path(ALSA_INCLUDE_DIR NAMES alsa/asoundlib.h
DOC The ALSA (asound) include directory
)
@@ -35,8 +33,8 @@ find_library(ALSA_LIBRARY NAMES asound
DOC The ALSA (asound) library
)
-if(ALSA_INCLUDE_DIR AND EXISTS ${ALSA_INCLUDE_DIR}/version.h)
- file(STRINGS ${ALSA_INCLUDE_DIR}/version.h alsa_version_str REGEX
^#define[\t ]+SND_LIB_VERSION_STR[\t ]+\.*\)
+if(ALSA_INCLUDE_DIR AND EXISTS ${ALSA_INCLUDE_DIR}/alsa/version.h)
+ file(STRINGS ${ALSA_INCLUDE_DIR}/alsa/version.h alsa_version_str REGEX
^#define[\t ]+SND_LIB_VERSION_STR[\t ]+\.*\)
string(REGEX REPLACE ^.*SND_LIB_VERSION_STR[\t ]+\([^\]*)\.*$ \\1
ALSA_VERSION_STRING ${alsa_version_str})
unset(alsa_version_str)
---
Summary of changes:
Modules/FindALSA.cmake |8 +++-
1 files changed, 3 insertions(+), 5 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.7-2503-g8513847
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 85138471659200d3650ea7b7d0a000ce1c873755 (commit) via 5d5bccd804f5ead01091b967a7c0aed80d58d500 (commit) from 7e8cbbe4d1d6a939ee5944a17cc7934e51f67379 (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=85138471659200d3650ea7b7d0a000ce1c873755 commit 85138471659200d3650ea7b7d0a000ce1c873755 Merge: 7e8cbbe 5d5bccd Author: Philip Lowman phi...@yhbt.com AuthorDate: Wed Feb 8 07:47:33 2012 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Feb 8 07:47:33 2012 -0500 Merge topic 'FindProtobuf_import_dirs' into next 5d5bccd Revert FindProtobuf: Remove CMake version comments http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5d5bccd804f5ead01091b967a7c0aed80d58d500 commit 5d5bccd804f5ead01091b967a7c0aed80d58d500 Author: Philip Lowman phi...@yhbt.com AuthorDate: Wed Feb 8 07:43:44 2012 -0500 Commit: Philip Lowman phi...@yhbt.com CommitDate: Wed Feb 8 07:43:44 2012 -0500 Revert FindProtobuf: Remove CMake version comments This reverts commit 29b2426d8321d0ffb0ccc8d6cb43d614753147a6. Brings back the version number diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake index 6faa262..1e1e493 100644 --- a/Modules/FindProtobuf.cmake +++ b/Modules/FindProtobuf.cmake @@ -8,13 +8,14 @@ # for libraries and binaries. # # PROTOBUF_IMPORT_DIRS - List of additional directories to be searched for -# imported .proto files. +# imported .proto files. (New in CMake 2.8.8) # # Defines the following variables: # # PROTOBUF_FOUND - Found the Google Protocol Buffers library (libprotobuf header files) # PROTOBUF_INCLUDE_DIRS - Include directories for Google Protocol Buffers # PROTOBUF_LIBRARIES - The protobuf libraries +# [New in CMake 2.8.5] # PROTOBUF_PROTOC_LIBRARIES - The protoc libraries # PROTOBUF_LITE_LIBRARIES - The protobuf-lite libraries # @@ -23,6 +24,7 @@ # PROTOBUF_PROTOC_LIBRARY - The protoc library # PROTOBUF_INCLUDE_DIR - The include directory for protocol buffers # PROTOBUF_PROTOC_EXECUTABLE - The protoc compiler +# [New in CMake 2.8.5] # PROTOBUF_LIBRARY_DEBUG - The protobuf library (debug) # PROTOBUF_PROTOC_LIBRARY_DEBUG - The protoc library (debug) # PROTOBUF_LITE_LIBRARY - The protobuf lite library --- Summary of changes: 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.7-1951-g1359324
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 135932415b3de7975a6fc90606b04b9e0471523d (commit) via 27bc9e2631a2f7b6d78064f5adf0b528982a2de7 (commit) from af18e7643ed2be76678080b9e543a575bafd32fa (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=135932415b3de7975a6fc90606b04b9e0471523d commit 135932415b3de7975a6fc90606b04b9e0471523d Merge: af18e76 27bc9e2 Author: Philip Lowman phi...@yhbt.com AuthorDate: Tue Jan 3 19:51:43 2012 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Jan 3 19:51:43 2012 -0500 Merge topic 'FindProtobuf_import_dirs' into next 27bc9e2 FindProtobuf: Update documentation comment for 2.8.8 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=27bc9e2631a2f7b6d78064f5adf0b528982a2de7 commit 27bc9e2631a2f7b6d78064f5adf0b528982a2de7 Author: Philip Lowman phi...@yhbt.com AuthorDate: Tue Jan 3 19:47:05 2012 -0500 Commit: Philip Lowman phi...@yhbt.com CommitDate: Tue Jan 3 19:47:05 2012 -0500 FindProtobuf: Update documentation comment for 2.8.8 diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake index ac6fd86..1e1e493 100644 --- a/Modules/FindProtobuf.cmake +++ b/Modules/FindProtobuf.cmake @@ -8,7 +8,7 @@ # for libraries and binaries. # # PROTOBUF_IMPORT_DIRS - List of additional directories to be searched for -# imported .proto files. (New in CMake 2.8.7) +# imported .proto files. (New in CMake 2.8.8) # # Defines the following variables: # --- Summary of changes: Modules/FindProtobuf.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
[Cmake-commits] CMake branch, next, updated. v2.8.6-2278-g894d532
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 894d5321585d323b1d9e964b51a5ac724290d903 (commit)
via 84079c92ca5c401e35aefacbcca25e0ac3e644d6 (commit)
from 8279bae5fdfde13c65d996bffd17aba2c200a11f (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=894d5321585d323b1d9e964b51a5ac724290d903
commit 894d5321585d323b1d9e964b51a5ac724290d903
Merge: 8279bae 84079c9
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sun Dec 18 18:21:54 2011 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sun Dec 18 18:21:54 2011 -0500
Merge topic 'FindProtobuf_import_dirs' into next
84079c9 FindProtobuf: Merge patch that allows extra import dirs
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=84079c92ca5c401e35aefacbcca25e0ac3e644d6
commit 84079c92ca5c401e35aefacbcca25e0ac3e644d6
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sun Dec 18 18:02:48 2011 -0500
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sun Dec 18 18:02:48 2011 -0500
FindProtobuf: Merge patch that allows extra import dirs
Added support for additional import paths during protoc invocation
time to the PROTOBUF_GENERATE_CPP public macro via a new
PROTOBUF_IMPORT_DIRS optional variable.
Patch courtesy of Miroslav Kes m...@ra.rockwell.com
diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake
index 5344304..ac6fd86 100644
--- a/Modules/FindProtobuf.cmake
+++ b/Modules/FindProtobuf.cmake
@@ -7,6 +7,9 @@
# (vsprojects/Debug vsprojects/Release) will be
searched
# for libraries and binaries.
#
+# PROTOBUF_IMPORT_DIRS - List of additional directories to be searched
for
+# imported .proto files. (New in CMake 2.8.7)
+#
# Defines the following variables:
#
# PROTOBUF_FOUND - Found the Google Protocol Buffers library (libprotobuf
header files)
@@ -91,6 +94,16 @@ function(PROTOBUF_GENERATE_CPP SRCS HDRS)
set(_protobuf_include_path -I ${CMAKE_CURRENT_SOURCE_DIR})
endif()
+ if(DEFINED PROTOBUF_IMPORT_DIRS)
+foreach(DIR ${PROTOBUF_IMPORT_DIRS})
+ get_filename_component(ABS_PATH ${DIR} ABSOLUTE)
+ list(FIND _protobuf_include_path ${ABS_PATH} _contains_already)
+ if(${_contains_already} EQUAL -1)
+ list(APPEND _protobuf_include_path -I ${ABS_PATH})
+ endif()
+endforeach()
+ endif()
+
set(${SRCS})
set(${HDRS})
foreach(FIL ${ARGN})
---
Summary of changes:
Modules/FindProtobuf.cmake | 13 +
1 files changed, 13 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
Re: [CMake] Protobuf Module
On Wed, Oct 12, 2011 at 8:46 AM, James Anderson
japanwikidon...@gmail.comwrote:
PROTOBUF_GENERATE_CPP does not seem to work at all in ubuntu. I was working
with 2.8.3 and since it wasn't working I have compiled the latest cmake
(2.8.6) but still no luck. I also tried with --debug-output but after
finding protobuf no other related output.
Here's the relevant segment:
FIND_PACKAGE(Protobuf)
IF(PROTOBUF_FOUND)
INCLUDE_DIRECTORIES(${PROTOBUF_INCLUDE_DIRS})
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR})
PROTOBUF_GENERATE_CPP(PROTO_SRCS PROTO_HDRS data.proto)
ENDIF()
Yet the protoc compiler is never invoked and the data.pb.cc and .h files are
never created (even tried without the IF statement).
James,
PROTO_SRCS PROTO_HDRS (in the code snippit you list above) are simply
lists of source header files to generate. You need to use them in a
target in order for CMake to cause them to be generated.
E.g.
add_executable(foo foo.cc ${PROTO_SRCS} ${PROTO_HDRS})
target_link_libraries(foo ${PROTOBUF_LIBRARIES})
Hope that solves your problem.
--
Philip Lowman
--
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.6-1575-g280a278
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 280a27891bddf2d9c8446d6a124dfd5c42fce037 (commit)
via a481d84ff72f554bc2e98fe4d9d63f960cf0ebfc (commit)
from b6440da5b53aa0ac837bd521be45163c1d72f347 (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=280a27891bddf2d9c8446d6a124dfd5c42fce037
commit 280a27891bddf2d9c8446d6a124dfd5c42fce037
Merge: b6440da a481d84
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Wed Oct 12 23:45:03 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Oct 12 23:45:03 2011 -0400
Merge topic 'FindProtoBuf_doc_clarify' into next
a481d84 FindProtoBuf: Documented limitation of the public macro
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a481d84ff72f554bc2e98fe4d9d63f960cf0ebfc
commit a481d84ff72f554bc2e98fe4d9d63f960cf0ebfc
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Wed Oct 12 23:44:40 2011 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Wed Oct 12 23:44:40 2011 -0400
FindProtoBuf: Documented limitation of the public macro
diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake
index 38f5a75..5344304 100644
--- a/Modules/FindProtobuf.cmake
+++ b/Modules/FindProtobuf.cmake
@@ -39,7 +39,11 @@
# target_link_libraries(bar ${PROTOBUF_LIBRARIES})
#
# NOTE: You may need to link against pthreads, depending
-# on the platform.
+# on the platform.
+#
+# NOTE: The PROTOBUF_GENERATE_CPP macro add_executable() or add_library()
+# calls only work properly within the same directory.
+#
#
#
# PROTOBUF_GENERATE_CPP (public function)
---
Summary of changes:
Modules/FindProtobuf.cmake |6 +-
1 files changed, 5 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
Re: [cmake-developers] FindBullet (was: CMake branch, next, updated. v2.8.5-1956-gd66bbbd)
Yes, I will contact the bullet developers about adding exports to a future release. Thanks for the link. On Fri, Sep 23, 2011 at 8:14 AM, Brad King brad.k...@kitware.com wrote: On 9/22/2011 11:35 PM, Philip Lowman wrote: 6f935d7 FindBullet: Also search for _Debug postfixed library names This is is a good fix for the short term. However, since Bullet itself builds with CMake the upstream developers of that project should create a modern package configuration file: http://www.cmake.org/Wiki/**CMake/Tutorials#CMake_Packageshttp://www.cmake.org/Wiki/CMake/Tutorials#CMake_Packages Then FindBullet can start with something like find_package(Bullet NO_MODULE) and fall back to the old search only when a BulletConfig.cmake is not found. -Brad -- Philip Lowman -- 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-commits] CMake branch, next, updated. v2.8.5-1956-gd66bbbd
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 d66bbbda7f7ed904a06effdda0a29693167dfe65 (commit) via 6f935d7f55af5c96d18d23b72991e87d1e029dda (commit) from 83cabdf85c8637c76a6afada5a5656fcc9072db5 (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=d66bbbda7f7ed904a06effdda0a29693167dfe65 commit d66bbbda7f7ed904a06effdda0a29693167dfe65 Merge: 83cabdf 6f935d7 Author: Philip Lowman phi...@yhbt.com AuthorDate: Thu Sep 22 23:35:30 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu Sep 22 23:35:30 2011 -0400 Merge topic 'FindBulletLibRenames' into next 6f935d7 FindBullet: Also search for _Debug postfixed library names http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6f935d7f55af5c96d18d23b72991e87d1e029dda commit 6f935d7f55af5c96d18d23b72991e87d1e029dda Author: Philip Lowman phi...@yhbt.com AuthorDate: Thu Sep 22 23:31:37 2011 -0400 Commit: Philip Lowman phi...@yhbt.com CommitDate: Thu Sep 22 23:31:37 2011 -0400 FindBullet: Also search for _Debug postfixed library names diff --git a/Modules/FindBullet.cmake b/Modules/FindBullet.cmake index cebb828..aea9158 100644 --- a/Modules/FindBullet.cmake +++ b/Modules/FindBullet.cmake @@ -59,13 +59,13 @@ find_path(BULLET_INCLUDE_DIR NAMES btBulletCollisionCommon.h # Find the libraries _FIND_BULLET_LIBRARY(BULLET_DYNAMICS_LIBRARYBulletDynamics) -_FIND_BULLET_LIBRARY(BULLET_DYNAMICS_LIBRARY_DEBUG BulletDynamics_d) +_FIND_BULLET_LIBRARY(BULLET_DYNAMICS_LIBRARY_DEBUG BulletDynamics_Debug BulletDynamics_d) _FIND_BULLET_LIBRARY(BULLET_COLLISION_LIBRARY BulletCollision) -_FIND_BULLET_LIBRARY(BULLET_COLLISION_LIBRARY_DEBUG BulletCollision_d) -_FIND_BULLET_LIBRARY(BULLET_MATH_LIBRARYLinearMath BulletMath) -_FIND_BULLET_LIBRARY(BULLET_MATH_LIBRARY_DEBUG LinearMath_d BulletMath_d) +_FIND_BULLET_LIBRARY(BULLET_COLLISION_LIBRARY_DEBUG BulletCollision_Debug BulletCollision_d) +_FIND_BULLET_LIBRARY(BULLET_MATH_LIBRARYBulletMath LinearMath) +_FIND_BULLET_LIBRARY(BULLET_MATH_LIBRARY_DEBUG BulletMath_Debug BulletMath_d LinearMath_d) _FIND_BULLET_LIBRARY(BULLET_SOFTBODY_LIBRARYBulletSoftBody) -_FIND_BULLET_LIBRARY(BULLET_SOFTBODY_LIBRARY_DEBUG BulletSoftBody_d) +_FIND_BULLET_LIBRARY(BULLET_SOFTBODY_LIBRARY_DEBUG BulletSoftBody_Debug BulletSoftBody_d) # handle the QUIETLY and REQUIRED arguments and set BULLET_FOUND to TRUE if --- Summary of changes: Modules/FindBullet.cmake | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
Re: [CMake] FindBoost PATH_SUFFIXES fix
On Wed, Jun 15, 2011 at 12:06 PM, Todd Gamblin tgamb...@llnl.gov wrote: Hi Todd, I'm the FindBoost maintainer. I was somewhat perplexed that FindBoost doesn't properly search the default install layout of the boost-cmake build. i.e. if you set BOOST_ROOT to point to something that looks like this: snip things will break. This is, unfortunately, the default install layout for the CMake build of boost. The script only checks path suffixes under the *include* directory, and it expects them to use underscores instead of periods, e.g.: I'm not sure exactly why boost-cmake decided to make their output directories use periods instead of underscores. It seems like a first step towards replacing bjam would at least be to match its install path format, but I digress. I've pasted below a patch that adds the version numbers with periods to the list of searched path suffixes, and that uses the path suffix list for both the library search and the header search. Any objections to my submitting this as a topic branch and pushing it out to next? I'm not sure I have permission to do that with the FindBoost module, so let me know what the right procedure is. The patch looks good. Feel free to submit it and push it to next. Thanks for asking for permission, by the way. In general, feel free to propose changes via email or even topic stages for FindBoost. I do welcome the help. I would like to review changes before they are pushed to next though (mainly to prevent people from breaking things). -- Philip Lowman ___ 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] CMakeDetermineVSServicePack.cmake
Aaron,
Thanks. Please see my comments in the ticket you reopened with the patch
you sent in yesterday.
BTW -- If you would like to volunteer to take ownership of this module I
would be happy to hand it over to someone else. Since I no longer use
Visual Studio I'm probably the wrong maintainer for this module.
http://www.itk.org/Wiki/CMake:Module_Maintainers
On Tue, Jun 7, 2011 at 1:53 PM, aaron.mead...@thomsonreuters.com wrote:
I’ve reopened Issue 0011279. CMakeDetermineVSServicePack.cmake has been
broken again, this time by VS2010 switching to MSBuild. This has caused the
version string to change. I’ve created a patch and uploaded it to the
Issue:
--8ß
-
--- CMakeDetermineVSServicePack.cmake 2011-06-06 17:40:02.92300 -0500
+++ CMakeDetermineVSServicePackWithVS2010MSBuild.cmake 2011-06-06 17:47:
04.057552300 -0500
@@ -47,7 +47,9 @@
set(_version vc90)
elseif(${_cl_version} VERSION_EQUAL 15.00.30729.01)
set(_version vc90sp1)
- elseif(${_cl_version} VERSION_EQUAL 16.00.30319.01)
+ elseif(${_cl_version} VERSION_EQUAL 16.00.30319.01) # Pre-release
VS2010 version number
+ set(_version vc100pre)
+ elseif(${_cl_version} VERSION_EQUAL 4.00.30319.01) # Release version
of VS2010 which uses MSBuild version number
set(_version vc100)
else()
set(_version )
@@ -74,6 +76,13 @@
if(DETERMINED_VS_SERVICE_PACK AND _output)
string(REGEX MATCH Compiler Version
[0-9]+.[0-9]+.[0-9]+.[0-9]+
_cl_version ${_output})
+
+# If the above didn't work, this may be VS 2010, which has a
different output with MSBuild
+if(NOT _cl_version)
+string(REGEX MATCH Build Engine Version
[0-9]+.[0-9]+.[0-9]+.[0-9]+
+_cl_version ${_output})
+endif()
+
if(_cl_version)
string(REGEX MATCHALL [0-9]+
_cl_version_list ${_cl_version})
*Aaron Meadows*
Software Engineer
*Thomson Reuters*
Phone: 314.468.3530
Mobile: 636.541.6139
aaron.mead...@thomsonreuters.com
thomsonreuters.com
___
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
--
Philip Lowman
___
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.4-1696-g3f18b6c
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 3f18b6c49ac0809e88e54e2a9981cbbfb0a17261 (commit)
via 51c786058989be0fb83f4f54c92ce8ea9856ae8d (commit)
via c7c2c4cc987a9290f08602fada86bf053ab9c867 (commit)
via 44310e95d63edd71974ad223a4f39e6ca74bf630 (commit)
via 08b109a87f43406f70a125552a2e0aaf54d3b782 (commit)
from 6e076e9413ff2c66088894def809d248880d432e (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=3f18b6c49ac0809e88e54e2a9981cbbfb0a17261
commit 3f18b6c49ac0809e88e54e2a9981cbbfb0a17261
Merge: 6e076e9 51c7860
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Tue Jun 7 01:11:34 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Jun 7 01:11:34 2011 -0400
Merge topic '10997_PROTOBDUF_GENERATE_CPP_returns_wrong_path' into next
51c7860 10997: PROTOBUF_GENERATE_CPP now supports proto files outside
current dir
c7c2c4c Revert previous patch to 10997, doesn't work for include directive
44310e9 Merge branch 'master' of git://public.kitware.com/cmake into
10997_PROTOBDUF_GENERATE_CPP_returns_wrong_path
08b109a KWSys Nightly Date Stamp
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=51c786058989be0fb83f4f54c92ce8ea9856ae8d
commit 51c786058989be0fb83f4f54c92ce8ea9856ae8d
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Tue Jun 7 01:07:41 2011 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Tue Jun 7 01:07:41 2011 -0400
10997: PROTOBUF_GENERATE_CPP now supports proto files outside current dir
diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake
index de1e569..b8929ad 100644
--- a/Modules/FindProtobuf.cmake
+++ b/Modules/FindProtobuf.cmake
@@ -73,6 +73,20 @@ function(PROTOBUF_GENERATE_CPP SRCS HDRS)
return()
endif(NOT ARGN)
+ if(PROTOBUF_GENERATE_CPP_APPEND_PATH)
+# Create an include path for each file specified
+foreach(FIL ${ARGN})
+ get_filename_component(ABS_FIL ${FIL} ABSOLUTE)
+ get_filename_component(ABS_PATH ${ABS_FIL} PATH)
+ list(FIND _protobuf_include_path ${ABS_PATH} _contains_already)
+ if(${_contains_already} EQUAL -1)
+ list(APPEND _protobuf_include_path -I ${ABS_PATH})
+ endif()
+endforeach()
+ else()
+set(_protobuf_include_path -I ${CMAKE_CURRENT_SOURCE_DIR})
+ endif()
+
set(${SRCS})
set(${HDRS})
foreach(FIL ${ARGN})
@@ -86,7 +100,7 @@ function(PROTOBUF_GENERATE_CPP SRCS HDRS)
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/${FIL_WE}.pb.cc
${CMAKE_CURRENT_BINARY_DIR}/${FIL_WE}.pb.h
COMMAND ${PROTOBUF_PROTOC_EXECUTABLE}
- ARGS --cpp_out ${CMAKE_CURRENT_BINARY_DIR} --proto_path
${CMAKE_CURRENT_SOURCE_DIR} ${ABS_FIL}
+ ARGS --cpp_out ${CMAKE_CURRENT_BINARY_DIR} ${_protobuf_include_path}
${ABS_FIL}
DEPENDS ${ABS_FIL}
COMMENT Running C++ protocol buffer compiler on ${FIL}
VERBATIM )
@@ -125,11 +139,17 @@ function(_protobuf_find_libraries name filename)
endif()
endfunction()
-
#
# Main.
#
+# By default have PROTOBUF_GENERATE_CPP macro pass -I to protoc
+# for each directory where a proto file is referenced.
+if(NOT DEFINED PROTOBUF_GENERATE_CPP_APPEND_PATH)
+ set(PROTOBUF_GENERATE_CPP_APPEND_PATH TRUE)
+endif()
+
+
# Google's provided vcproj files generate libraries with a lib
# prefix on Windows
if(MSVC)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c7c2c4cc987a9290f08602fada86bf053ab9c867
commit c7c2c4cc987a9290f08602fada86bf053ab9c867
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Tue Jun 7 00:54:09 2011 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Tue Jun 7 00:54:09 2011 -0400
Revert previous patch to 10997, doesn't work for include directive
diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake
index 07110c9..de1e569 100644
--- a/Modules/FindProtobuf.cmake
+++ b/Modules/FindProtobuf.cmake
@@ -77,8 +77,7 @@ function(PROTOBUF_GENERATE_CPP SRCS HDRS)
set(${HDRS})
foreach(FIL ${ARGN})
get_filename_component(ABS_FIL ${FIL} ABSOLUTE)
-file(RELATIVE_PATH REL_FIL ${CMAKE_CURRENT_SOURCE_DIR} ${ABS_FIL})
-string(REGEX REPLACE .proto$ FIL_WE ${REL_FIL})
+get_filename_component(FIL_WE ${FIL} NAME_WE)
list(APPEND ${SRCS} ${CMAKE_CURRENT_BINARY_DIR}/${FIL_WE}.pb.cc)
list(APPEND ${HDRS} ${CMAKE_CURRENT_BINARY_DIR}/${FIL_WE}.pb.h)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=44310e95d63edd71974ad223a4f39e6ca74bf630
commit 44310e95d63edd71974ad223a4f39e6ca74bf630
Merge: abd9327 08b109a
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Tue Jun 7 00:48
[Cmake-commits] CMake branch, next, updated. v2.8.4-1618-g08a5024
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 08a5024306cf00c4aa06bab6995f89d18b2154d9 (commit) via 517837fb470e41ee47d1f267e47f069bc8f00441 (commit) via 162f3fb413fc862c5c75a0402fdfbdc6dd19468b (commit) from 1f4e39e7539a193981a6bdabf5174bea3e0da271 (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=08a5024306cf00c4aa06bab6995f89d18b2154d9 commit 08a5024306cf00c4aa06bab6995f89d18b2154d9 Merge: 1f4e39e 517837f Author: Philip Lowman phi...@yhbt.com AuthorDate: Thu May 26 02:23:21 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu May 26 02:23:21 2011 -0400 Merge topic '12128_FindProtobuf_module_behavior_under_Windows_is_annoying' into next 517837f Fix , to - in Copyright message so it passes CMake.ModuleNotices test 162f3fb Merge branch 'master' of git://public.kitware.com/cmake into 12128_FindProtobuf_module_behavior_under_Windows_is_annoying http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=517837fb470e41ee47d1f267e47f069bc8f00441 commit 517837fb470e41ee47d1f267e47f069bc8f00441 Author: Philip Lowman phi...@yhbt.com AuthorDate: Thu May 26 02:21:58 2011 -0400 Commit: Philip Lowman phi...@yhbt.com CommitDate: Thu May 26 02:21:58 2011 -0400 Fix , to - in Copyright message so it passes CMake.ModuleNotices test diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake index e20c448..88ef7cd 100644 --- a/Modules/FindProtobuf.cmake +++ b/Modules/FindProtobuf.cmake @@ -54,7 +54,7 @@ #= # Copyright 2009 Kitware, Inc. -# Copyright 2009,2011 Philip Lowman phi...@yhbt.com +# Copyright 2009-2011 Philip Lowman phi...@yhbt.com # Copyright 2008 Esben Mose Hansen, Ange Optimization ApS # # Distributed under the OSI-approved BSD License (the License); http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=162f3fb413fc862c5c75a0402fdfbdc6dd19468b commit 162f3fb413fc862c5c75a0402fdfbdc6dd19468b Merge: ca000a0 8b17fd6 Author: Philip Lowman phi...@yhbt.com AuthorDate: Wed May 25 22:10:19 2011 -0400 Commit: Philip Lowman phi...@yhbt.com CommitDate: Wed May 25 22:10:19 2011 -0400 Merge branch 'master' of git://public.kitware.com/cmake into 12128_FindProtobuf_module_behavior_under_Windows_is_annoying --- Summary of changes: Modules/FindProtobuf.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
[Cmake-commits] CMake branch, next, updated. v2.8.4-1613-g4b1bd05
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 4b1bd050a90944babc637eca6a9e822c3f057055 (commit)
via ca000a0948023961130d1ee389d65228a746629a (commit)
from 94ce752bdbd7886e68f897cf3d33f3d8b01dd30d (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=4b1bd050a90944babc637eca6a9e822c3f057055
commit 4b1bd050a90944babc637eca6a9e822c3f057055
Merge: 94ce752 ca000a0
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Wed May 25 22:04:25 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed May 25 22:04:25 2011 -0400
Merge topic '12128_FindProtobuf_module_behavior_under_Windows_is_annoying'
into next
ca000a0 FindProtobuf: Better MSVC support, Searching for protobuf lite
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ca000a0948023961130d1ee389d65228a746629a
commit ca000a0948023961130d1ee389d65228a746629a
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Wed May 25 22:01:49 2011 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Wed May 25 22:01:49 2011 -0400
FindProtobuf: Better MSVC support, Searching for protobuf lite
Add support for finding debug libraries
Add support for searching Google provided MSVC project dir structure for
libs
Add support for finding Protobuf Lite libraries
diff --git a/Modules/FindProtobuf.cmake b/Modules/FindProtobuf.cmake
index a6e6653..e20c448 100644
--- a/Modules/FindProtobuf.cmake
+++ b/Modules/FindProtobuf.cmake
@@ -1,15 +1,31 @@
# Locate and configure the Google Protocol Buffers library.
+#
+# The following variables can be set and are optional:
+#
+# PROTOBUF_SRC_ROOT_FOLDER - When compiling with MSVC, if this cache
variable is set
+# the protobuf-default VS project build locations
+# (vsprojects/Debug vsprojects/Release) will be
searched
+# for libraries and binaries.
+#
# Defines the following variables:
#
-# PROTOBUF_FOUND - Found the Google Protocol Buffers library
+# PROTOBUF_FOUND - Found the Google Protocol Buffers library (libprotobuf
header files)
# PROTOBUF_INCLUDE_DIRS - Include directories for Google Protocol Buffers
-# PROTOBUF_LIBRARIES - The protobuf library
+# PROTOBUF_LIBRARIES - The protobuf libraries
+# [New in CMake 2.8.5]
+# PROTOBUF_PROTOC_LIBRARIES - The protoc libraries
+# PROTOBUF_LITE_LIBRARIES - The protobuf-lite libraries
#
-# The following cache variables are also defined:
+# The following cache variables are also available to set or use:
# PROTOBUF_LIBRARY - The protobuf library
# PROTOBUF_PROTOC_LIBRARY - The protoc library
# PROTOBUF_INCLUDE_DIR - The include directory for protocol buffers
# PROTOBUF_PROTOC_EXECUTABLE - The protoc compiler
+# [New in CMake 2.8.5]
+# PROTOBUF_LIBRARY_DEBUG - The protobuf library (debug)
+# PROTOBUF_PROTOC_LIBRARY_DEBUG - The protoc library (debug)
+# PROTOBUF_LITE_LIBRARY - The protobuf lite library
+# PROTOBUF_LITE_LIBRARY_DEBUG - The protobuf lite library (debug)
#
#
# Example:
@@ -20,7 +36,7 @@
# include_directories(${CMAKE_CURRENT_BINARY_DIR})
# PROTOBUF_GENERATE_CPP(PROTO_SRCS PROTO_HDRS foo.proto)
# add_executable(bar bar.cc ${PROTO_SRCS} ${PROTO_HDRS})
-# target_link_libraries(bar ${PROTOBUF_LIBRARY})
+# target_link_libraries(bar ${PROTOBUF_LIBRARIES})
#
# NOTE: You may need to link against pthreads, depending
# on the platform.
@@ -38,7 +54,7 @@
#=
# Copyright 2009 Kitware, Inc.
-# Copyright 2009 Philip Lowman phi...@yhbt.com
+# Copyright 2009,2011 Philip Lowman phi...@yhbt.com
# Copyright 2008 Esben Mose Hansen, Ange Optimization ApS
#
# Distributed under the OSI-approved BSD License (the License);
@@ -81,41 +97,85 @@ function(PROTOBUF_GENERATE_CPP SRCS HDRS)
set(${HDRS} ${${HDRS}} PARENT_SCOPE)
endfunction()
+# Internal function: search for normal library as well as a debug one
+#if the debug one is specified also include debug/optimized keywords
+#in *_LIBRARIES variable
+function(_protobuf_find_libraries name filename)
+ find_library(${name}_LIBRARY
+ NAMES ${filename}
+ PATHS ${PROTOBUF_SRC_ROOT_FOLDER}/vsprojects/Release)
+ mark_as_advanced(${name}_LIBRARY)
+
+ find_library(${name}_LIBRARY_DEBUG
+ NAMES ${filename}
+ PATHS ${PROTOBUF_SRC_ROOT_FOLDER}/vsprojects/Debug)
+ mark_as_advanced(${name}_LIBRARY_DEBUG)
+
+ if(NOT ${name}_LIBRARY_DEBUG
Re: [CMake] [CMake General][FindBoost] CMake and Boost 1.46.1
On Mon, May 2, 2011 at 1:53 AM, Robert Nelson boardmaster...@gmail.comwrote: try ... setting Boost_DEBUG On Great suggestion! I looked at the debug output as you recommended and discovered that findboost only searches for filenames that start with boost while all the files in the lib directory start with libboost I copied and renamed the regex files in the lib directory to start with boost instead and it found the regex library but not the others. So a possible solution would be to rename all the files in the folder. This, however, is less than elegant. Is this a breaking change in the way the boost library files are named, a bug in findboost, or did I install boost wrong somehow? On Windows, the boost convention is to prefix shared libraries with boost and static libraries with libboost. By default FindBoost searches for shared libraries since this matches CMake default behavior on Unix platforms. If you want FindBoost to search for static libraries instead, simply set: set(Boost_USE_STATIC_LIBS ON) -- Philip Lowman ___ 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 General][FindBoost] CMake and Boost 1.46.1
FindBoost is a bit of a pain to get working.
I'm wondering if the REQUIRED and 1.46 in the find_package() is causing it
to skip 1.46.1? You could clear your cache and try changing the version to
1.46.1 or remove the REQUIRED.
If that's not it, try clearing your cache, setting Boost_DEBUG On and having
a look at the output and/or pasting it in here.
On Sun, May 1, 2011 at 5:18 PM, Robert Nelson boardmaster...@gmail.comwrote:
I just tried adding
SET(Boost_ADDITIONAL_VERSIONS 1.46.1)
clearing the cache, and running configure again. I still get the same
error message as before. While I agree that your addition is
necessary to make it work, it seems that something else is also
needed.
PROJECT(schema)
cmake_minimum_required(VERSION 2.8.4)
SET( Boost_NO_SYSTEM_PATHS true )
SET( BOOST_INCLUDEDIR C:/Boost/include/boost-1_46_1 )
SET( BOOST_LIBRARYDIR C:/Boost/lib )
SET(Boost_ADDITIONAL_VERSIONS 1.46.1 )
find_package(Boost 1.46 COMPONENTS regex program_options pthread
filesystem REQUIRED)
link_directories(${Boost_LIBRARY_DIRS} )
include_directories( ${Boost_INCLUDE_DIRS} )
#if you don't want the full compiler output, remove the following line
SET(CMAKE_VERBOSE_MAKEFILE ON)
add_executable(schema
main.cpp
)
___
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
--
Philip Lowman
___
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-827-g1f70d7a
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 1f70d7aa3829e8fab044a33f457449febab3180d (commit)
via a80d6e9828b3089519fedbd4eee4c199ce3b8597 (commit)
from dda80352ba5f2cf94933a9e603d393ccc1442b02 (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=1f70d7aa3829e8fab044a33f457449febab3180d
commit 1f70d7aa3829e8fab044a33f457449febab3180d
Merge: dda8035 a80d6e9
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Mon Dec 13 01:23:36 2010 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Dec 13 01:23:36 2010 -0500
Merge topic '11445-workaround' into next
a80d6e9 Add Boost 1.46
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a80d6e9828b3089519fedbd4eee4c199ce3b8597
commit a80d6e9828b3089519fedbd4eee4c199ce3b8597
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Mon Dec 13 01:21:46 2010 -0500
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Mon Dec 13 01:21:46 2010 -0500
Add Boost 1.46
diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index dd16f1e..8930405 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -65,7 +65,7 @@
# 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, 1.35, 1.35.0, 1.35.1,
# 1.36, 1.36.0, 1.36.1, 1.37, 1.37.0, 1.38, 1.38.0, 1.39, 1.39.0,
# 1.40, 1.40.0, 1.41, 1.41.0, 1.42, 1.42.0, 1.43, 1.43.0, 1.44, 1.44.0,
-# 1.45, 1.45.0
+# 1.45, 1.45.0, 1.46, 1.46.0
#
# NOTE: If you add a new major 1.x version in Boost_ADDITIONAL_VERSIONS you
should
# add both 1.x and 1.x.0 as shown above. Official Boost include directories
@@ -378,7 +378,7 @@ else(Boost_FIND_VERSION_EXACT)
# The user has not requested an exact version. Among known
# versions, find those that are acceptable to the user request.
set(_Boost_KNOWN_VERSIONS ${Boost_ADDITIONAL_VERSIONS}
-1.45.0 1.45 1.44.0 1.44 1.43.0 1.43 1.42.0 1.42
+1.46.0 1.46 1.45.0 1.45 1.44.0 1.44 1.43.0 1.43 1.42.0
1.42
1.41.0 1.41 1.40.0 1.40 1.39.0 1.39 1.38.0 1.38 1.37.0
1.37
1.36.1 1.36.0 1.36 1.35.1 1.35.0 1.35 1.34.1 1.34.0
1.34 1.33.1 1.33.0 1.33)
---
Summary of changes:
Modules/FindBoost.cmake |4 ++--
1 files changed, 2 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
Re: [CMake] CMake bug tracker discussion
On Thu, Dec 9, 2010 at 5:06 PM, David Cole david.c...@kitware.com wrote: Hello CMake users and devs, (And now for something completely different...) Controversial questions: - Should we eliminate the bug tracker entirely and just do all discussion and patches on the mailing list? (Why have two sources of information...?) - Or, alternatively, should we eliminate the bulk of mailing list traffic, and insist on issues in the bug tracker being the main conversational forum for the whole community? I'd like to have this discussion here publicly, to try to get a good sense of varous community members attitudes and feelings. I like the bug tracker. Even people that use it, however, know that hitting up the mailing list tends to improve the chance that the bug is actually researched and fixed. Also, sometimes it seems wrong to take an issue raised on the mailing list and force it into the bug tracker. It seems a little rude to the person that emailed about the issue because you might be asking them to deal with the rigmarole of creating a mantis account when they already went through the hassle of joining the mailing list and making the post. -- Philip Lowman ___ 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] FindBoost: find both win32 and x64 static libs
On Sunday, December 5, 2010, Hicham Mouline hic...@mouline.org wrote: I've built both win32 and x64 versions of boost thread library with the following 2 lines: 1. 32bit cl.exe from msvc9 directory in the %PATH% bjam --with-thread --layout=versioned toolset=msvc address-model=64 variant=release link=static threading=multi runtime-link=shared 2. 64bit cl.exe from msvc9 directory in the %PATH% bjam --with-thread --layout=versioned toolset=msvc address-model=64 variant=release link=static threading=multi runtime-link=shared however, the resulting .lib files have identical names however: libboost_thread-vc90-mt-1_44.lib libboost_thread-vc90-mt.lib Dmytro, there is no distinction between 32bit and 64bit. The 64bit lib size is approximately double the 32bit lib. boost-build, how to change this to include the bitness in the boost lib name? If it's impossible, Philip, perhaps FindBoost could be changed to allow for different directories under BOOST_ROOT for the lib directories, something like lib\win32 and lib\x64 or whatever names can be agreed on. If the user is compiling 32-bit code I could make FindBoost search lib32 before lib and for 64-bit code I can make it search lib64 before lib. If the user had an empty lib64 directory for some reason, it would still find the boost libraries in lib. Would this work for you? The BOOST_LIBRARYDIR variable is the only other workaround I can think to this 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://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Wiki: version compatibility matrix
Wow. Thank you for making this. I think it will be a huge resource for CMake users. Nothing is more annoying than having to track down when something was added, or not realizing that the behavior that you rely upon did not exist in a previous version. On Saturday, December 4, 2010, Johannes Zarl johannes.z...@jku.at wrote: Hello, The compatibility matrix for different versions of cmake is now complete and awaits review: http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix Apart from factual errors and things I might have missed, I am also interested if someone has a better idea for embedding the comments: they make the tables broader than they need to be. Also, the wiki warns that the page might be to big for some browsers. Should the page be divided into subpages? If no one objects, I will add a link to the main-page under Development Topics by Wednesday next week (2010-12-08). Cheers, 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 -- Philip Lowman ___ 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] Makefile to CMakeLists.txt (GTEST)
On Wed, Dec 1, 2010 at 10:59 AM, Kevyn-Alexandre Paré
kap...@rogue-research.com wrote:
Philip,
Thx for the reply. Neither of these solutions change a thing.
I try to play with ADD_CUSTOM_TARGET but same error...
ADD_CUSTOM_TARGET(RRThread.o ALL COMMAND ${CMAKE_C_COMPILER} -I
${MICRONTRACKER_COMMON_PATH} -I${GTEST_HEADER_PATH} -lpthread -c
${MICRONTRACKER_COMMON_PATH}RRThread.c
${UNIT_TEST_PATH}common/UT_RRThread.cc)
ADD_CUSTOM_TARGET(UT_RRThread ALL COMMAND ${CMAKE_CXX_COMPILER} -I
${MICRONTRACKER_COMMON_PATH} -I${GTEST_HEADER_PATH} -lpthread RRThread.o
UT_RRThread.o ${GTEST_LIB_PATH}gtest.a ${GTEST_LIB_PATH}gtest_main.a -o
UT_RRThread)
Result:
UT_RRThread.o: In function `thread_proc(void*)':
UT_RRThread.cc:(.text+0x28): undefined reference to `exitThread()'
...
I'm not sure what exactly has gone wrong here. You might want to try to
find the exitThread symbol to see where it lives using nm or strings on
the libraries that you have. If all else fails, perhaps check on a GTest
forum? I've never had this problem before but I don't recall ever using the
gtest static libraries either.
I pretty sure that I'm missing little detail. How can I implicitly add
dependency to the object during the linking?
I don't see anything wrong with what you have in terms of the GCC
invocation. You'll need to explicitly specify the libraries during compile
time to resolve those symbols and produce a binary as far as I know.
I'm not sure why you're using add_custom_target() when you could just use
add_executable() and target_link_libraries(), but I doubt this has anything
to do with your undefined symbol reference.
--
Philip Lowman
___
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] FindBoost: find both win32 and x64 static libs
On Tue, Nov 30, 2010 at 5:37 PM, Hicham Mouline hic...@mouline.org wrote:
As boost libraries naming convention doesn't include in the lib names
whether they are built by msvc9 win32 or x64, I am forced on a winxp 64 box
where I hold both versions to have a different lib directory under
boost_root.
I set BOOST_ROOT then call FIND_PACKAGE(Boost 1.44 COMPONENTS ...).
Am I supposed to detect which of vc9 32bit or 64bit am I generating for
and then set BOOST_LIBRARYDIR depending on that before calling FIND_PACKAGE?
How do I detect bitness?
You could try something like this:
include(CheckTypeSize)
CHECK_TYPE_SIZE(void* SIZEOF_PTR)
message(size of pointer = ${SIZEOF_PTR})
Then if SIZEOF_PTR is 4, you would set BOOST_LIBRARYDIR to be
${BOOST_ROOT}/lib32 and if it is 8, you set it to ${BOOST_ROOT}/lib64.
--
Philip Lowman
___
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] FindBoost: find both win32 and x64 static libs
On Saturday, December 4, 2010, Hicham Mouline hic...@mouline.org wrote: I was wrong. Dmytro pointed out that bjam allows building boost libraries with the compiler and bitness in the boost library name --layout=versioned. Therefore, I could have both 32 and 64bit versions in the same directory. I wonder then if FindBoost is able to detect automatically the right ones based on the name of the libs. I could probably add this feature, I'm pretty sure there isn't support for it now. Could you create a feature request on the CMake bug tracker and include what the filenames look like when generated by visual studio? If you want to try to patch FindBoost yourself, please make sure you're playing with the version from 2.8.3. http://www.cmake.org/Bug -- Philip Lowman ___ 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] Makefile to CMakeLists.txt (GTEST)
Try adding the gtest.a library as well. Also, order does matter when you
are linking static libraries so you might need to play with the ordering.
Also, when you get some time, have a look at FindGTest.cmake. It may help
you simplify adding your tests.
On Mon, Nov 29, 2010 at 5:55 PM, Kevyn-Alexandre Paré
kap...@rogue-research.com wrote:
Hi,
/// - What I trying to do is to compile my unit test with google test
with cmake from a working Makefile.
/// - Here the Makefile
RRThread.o : $(USER_DIR)/RRThread.c $(USER_DIR)/RRThread.h
$(GTEST_HEADERS)
$(CXX) $(CPPFLAGS) $(CXXFLAGS) -c $(USER_DIR)/RRThread.c
UT_RRThread.o : $(UNITTEST_DIR)/UT_RRThread.cc \
$(USER_DIR)/RRThread.h $(GTEST_HEADERS)#
$(CXX) $(CPPFLAGS) $(CXXFLAGS) -I$(USER_DIR) -c
$(UNITTEST_DIR)/UT_RRThread.cc
UT_RRThread : RRThread.o UT_RRThread.o gtest_main.a
$(CXX) $(CPPFLAGS) $(CXXFLAGS) -lpthread $^ -o $@
/// - Here how I thought of doing it with CMakeLists.txt:::
INCLUDE_DIRECTORIES(${GTEST_HEADER} ${USER_DIR})
ADD_EXECUTABLE(UT ${USER_DIR}RRThread.c ${UNIT_TEST_PATH}UT_RRThread.cc)
TARGET_LINK_LIBRARIES(UT pthread ${GTEST_LIB_PATH}gtest_main.a)
/// - My result:
Linking CXX executable UT
/usr/bin/cmake -E cmake_link_script CMakeFiles/UT.dir/link.txt
--verbose=1
/usr/bin/c++ CMakeFiles/UT.dir/common/RRThread.c.o
CMakeFiles/UT.dir/UnitTests/common/UT_RRThread.cc.o -o UT -rdynamic
-lpthread
/home/andromeda/rogue-research/3rdParty/gtest/trunk/Release/lib/gtest_main.a
CMakeFiles/UT.dir/UnitTests/common/UT_RRThread.cc.o: In function
`thread_proc(void*)':
UT_RRThread.cc:(.text+0x28): undefined reference to `exitThread()'
/// - My question and my problem is:
Since I'm including the USER_DIR with INCLUDE_DIRECTORIES why is it
complaining about not finding reference that is in that header file?
Best Regards,
--
Kevyn-Alexandre Paré
___
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
--
Philip Lowman
___
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] Eciipse and multiple configuration
You really can't, unfortunately because only one configuration is possible per CMake build directory with the Makefile generator. Most people set CMAKE_BUILD_TYPE to Debug when using the Eclipse CDT4 Generator so they can debug. If you need to test regularly with release binaries, one solution is to create a second build directory with CMAKE_BUILD_TYPE set to Release pointing it to the same source tree as your Debug build. On Tue, Nov 16, 2010 at 7:09 AM, Andrea Galeazzi galea...@korg.it wrote: I followed the tutorial at http://www.cmake.org/Wiki/Eclipse_CDT4_Generator in order to generate an Eclipse project. The only difference is that I select eclipseCDT - MiinGW Makefiles instead of eclipseCDT -Unix Makefiles. What I don't understand is how can I manage multiple configurations in the same project (for example Debug/Release) if the cmake-gui requires a specific CMAKE_BUILD_TYPE. Sorry but I'm a CMake newbie.. ___ 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 -- Philip Lowman ___ 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] Bug fix requests for the *next* release of CMake...
On Sun, Nov 7, 2010 at 8:29 PM, Luigi Calori l.cal...@cineca.it wrote: On 07/11/2010 21.01, Philip Lowman wrote: On Fri, Nov 5, 2010 at 12:08 PM, Luigi Calori l.cal...@cineca.it wrote: +1 for FindBoost support to CMakeified version of Boost at http://gitorious.org/~denisarnaud/boost/denisarnauds-zeuners-boost-cmake/commits/1.44.0-denishttp://gitorious.org/%7Edenisarnaud/boost/denisarnauds-zeuners-boost-cmake/commits/1.44.0-denis : Luigi, Does the CMakeified version of Boost still not produce build outputs that match bjam by default? I remember when I looked at it a year or two ago there appeared to be only minor issues with the library names. I would have hoped that these issues would have been resolved by now. I just tried the build with cmake 2.8.2 under MSVC9 using release build and static linking: There seem to be a minor inconsistency: when building Boost with cmake the static libs do not have the prefix lib so boost the auto-linking fails. I have resolved by 1) when building boos, configure with -DLIBPREFIX=lib, 2) configure the project that search for boost with -DBoost_USE_STATIC_LIBS=ON During the installation step of cmakefied boost, Boost.cmake config files get installed but not sure if FindBoost use it I' m not sure if this can be solved in FindBoost, but was just raising attention on a (for me) much better build system for Boost Luigi, Thanks for the additional information. It sounds like a bug in the CMake build system for Boost. On WIN32 (but not CYGWIN) it should create static boost libraries with the lib prefix and shared boost libraries without it to match the long-established Boost/bjam conventions. This allows static shared libraries to exist alongside each other in the lib folder since otherwise their filenames would collide. -- Philip Lowman ___ 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] Bug fix requests for the *next* release of CMake...
On Fri, Nov 5, 2010 at 12:08 PM, Luigi Calori l.cal...@cineca.it wrote: +1 for FindBoost support to CMakeified version of Boost at http://gitorious.org/~denisarnaud/boost/denisarnauds-zeuners-boost-cmake/commits/1.44.0-denis : Luigi, Does the CMakeified version of Boost still not produce build outputs that match bjam by default? I remember when I looked at it a year or two ago there appeared to be only minor issues with the library names. I would have hoped that these issues would have been resolved by now. Could you elaborate in a bug report what does and doesn't work between FindBoost.cmake and the branch of Boost that you're referring to and I would be more than happy to look into the issue. I've heard reports of people getting FindBoost and CMakeified boost to play nice together but it involved changing build settings in CMakeified Boost (not quite ideal). -- Philip Lowman ___ 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] Bug fix requests for the *next* release of CMake...
On Fri, Nov 5, 2010 at 6:29 AM, Adam J Richardson fat...@crackmonkey.uswrote: Could you guys have a chat with the Boost guys and fix the future safety of FindBoost.cmake somehow? Fiddling with ADDITIONAL_VERSIONS is really a pain on a build farm. To implement this I think we would need wildcat version searching support for find_library() and friends. I had a proposal for this a while ago but it didn't go anywhere nor did I ever implement it. http://www.itk.org/Bug/view.php?id=8396 I suggested that support for searching for files or directories that match a particular regex that describes a version number be added. In other words, you could try to find: NAMES foo-([0-9])\.([0-9]) or PATHS bar([0-9]+) The module would be responsible of passing on the request to find the latest version number that matches, or it could specify an absolute version to find. It would probably have to be an extended form of the find_library(), find_path(), etc. commands. -- Philip Lowman ___ 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] Linking Boost on Linux on 64bit host and 32bit target
On Thu, Nov 4, 2010 at 12:31 PM, Michael Jackson mike.jack...@bluequartz.net wrote: Clean out your build folder first. export BOOST_ROOT=/home/kknox/sdk/boost_1_44_0 == that needs to be an actual installation, a staged area will probably NOT work to find boost as FindBoost is looking for a very specific path within BOOST_ROOT and if that path is NOT found then it will probably fall back on the system paths. FindBoost.cmake in CMake 2.8.3 supports a new option to prevent searching the system paths. You should enable it if you are 100% sure that you will never want to find something outside of BOOST_ROOT, CMAKE_PREFIX_PATH, etc. Boost_NO_SYSTEM_PATHS There was a bug related to not finding Boost libraries in a staging area. I believe this works now. Also, take a moment and set this new variable appropriately (nearly all users will want it to be OFF) Boost_USE_STATIC_RUNTIME -- Philip Lowman ___ 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] Linking Boost on Linux on 64bit host and 32bit
Can you grab the FindBoost.cmake with CMake 2.8.3, then set the following (new) variable and paste the debug output again? This will at least prevent it from finding stuff in /usr/lib which has been an issue for some people. Also there is more debugging now. http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindBoost.cmake;h=3ae4e1410b9ec04b81dc76ddf822601f17f173c1;hb=b58e44edfb8e4267028a4754a25114d3bfad0abe set(Boost_NO_SYSTEM_PATHS TRUE) Offhand, I think you're on the right track using BOOST_LIBRARYDIR to override the search path for your 32 vs. 64 bit directories. That should show up first in the search path list. On Thu, Nov 4, 2010 at 3:37 PM, Knox, Kent kent.k...@amd.com wrote: [Michael] # set( Boost_DEBUG ON ) Uncomment that and send the output. Yes, it will be A LOT of output but I am trying to figure out what is going wrong. [Kent] I took out the explicit setting of BOOST_LIBRARYDIR: kk...@ux2 ~/code/clAMD/trunk/bin/linux32 561 InitCmake.sh -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- UNICODE feature disabled on linux -- 64-bit build -- [ FindBoost.cmake:373 ] Boost not in cache -- [ FindBoost.cmake:376 ] _boost_TEST_VERSIONS = 1.44;1.44.0;1.41.0;1.41;1.40.0;1.40;1.39.0;1.39;1.38.0;1.38;1.37.0;1.37;1.36.1;1.36.0;1.36;1.35.1;1.35.0;1.35;1.34.1;1.34.0;1.34;1.33.1;1.33.0;1.33 -- [ FindBoost.cmake:378 ] Boost_USE_MULTITHREADED = ON -- [ FindBoost.cmake:380 ] Boost_USE_STATIC_LIBS = ON -- [ FindBoost.cmake:439 ] Declared as CMake or Environmental Variables: -- [ FindBoost.cmake:441 ] BOOST_ROOT = /home/kknox/sdk/boost_1_44_0 -- [ FindBoost.cmake:443 ] BOOST_INCLUDEDIR = -- [ FindBoost.cmake:445 ] BOOST_LIBRARYDIR = -- [ FindBoost.cmake:447 ] _boost_TEST_VERSIONS = 1.44;1.44.0;1.41.0;1.41;1.40.0;1.40;1.39.0;1.39;1.38.0;1.38;1.37.0;1.37;1.36.1;1.36.0;1.36;1.35.1;1.35.0;1.35;1.34.1;1.34.0;1.34;1.33.1;1.33.0;1.33 -- [FindBoost.cmake:496 ] Include debugging info: -- [FindBoost.cmake:498 ] _boost_INCLUDE_SEARCH_DIRS = /home/kknox/sdk/boost_1_44_0/include;/home/kknox/sdk/boost_1_44_0;C:/boost/include;C:/boost;/boost/include;/boost;/sw/local/include -- [ FindBoost.cmake:500 ] _boost_PATH_SUFFIXES = boost-1_44;boost-1_44_0;boost-1_41_0;boost-1_41;boost-1_40_0;boost-1_40;boost-1_39_0;boost-1_39;boost-1_38_0;boost-1_38;boost-1_37_0;boost-1_37;boost-1_36_1;boost-1_36_0;boost-1_36;boost-1_35_1;boost-1_35_0;boost-1_35;boost-1_34_1;boost-1_34_0;boost-1_34;boost-1_33_1;boost-1_33_0;boost-1_33 -- [FindBoost.cmake:524 ] location of version.hpp: /home/kknox/sdk/boost_1_44_0/boost/version.hpp -- [FindBoost.cmake:543 ] version.hpp reveals boost 1.44.0 -- [FindBoost.cmake:634 ] guessed _boost_COMPILER = -gcc44 -- [FindBoost.cmake:644 ] _boost_MULTITHREADED = -mt -- [FindBoost.cmake:661 ] _boost_STATIC_TAG = -- [FindBoost.cmake:663 ] _boost_ABI_TAG = d -- [FindBoost.cmake:696 ] _boost_LIBRARIES_SEARCH_DIRS = /home/kknox/sdk/boost_1_44_0/lib;/home/kknox/sdk/boost_1_44_0/stage/lib;/home/kknox/sdk/boost_1_44_0/lib;/home/kknox/sdk/boost_1_44_0/../lib;C:/boost/lib;C:/boost;/boost /boost_1_44_0/lib;/boost/boost_1_44/lib;/boost/lib;/boost;/sw/local/lib -- [ FindBoost.cmake:830 ] Boost_FOUND = TRUE -- Boost version: 1.44.0 -- Found the following Boost libraries: -- program_options -- Boost_PROGRAM_OPTIONS_LIBRARY: /usr/lib/libboost_program_options-mt.a -- Found FFTW: /usr/lib/libfftw3f.so -- Found GTest: /usr/lib/libgtest.so -- Detected GNU fortran compiler. -- CMAKE_CXX_COMPILER flags: -m64 -- CMAKE_CXX_COMPILER debug flags: -g -- CMAKE_CXX_COMPILER release flags: -O3 -DNDEBUG -- CMAKE_CXX_COMPILER relwithdebinfo flags: -O2 -g -- CMAKE_EXE_LINKER link flags: -- Boost_LIBRARIES: /usr/lib/libboost_program_options-mt.a -- Boost_PROGRAM_OPTIONS_LIBRARY: /usr/lib/libboost_program_options-mt.a -- Configuring done -- Generating done -- Build files have been written to: /home/kknox/code/clAMD/trunk /bin/linux32 I've shortened the FindBoost.cmake path to make it more readable: originally [/home/kknox/bin/cmake-2.8.2-Linux-i386/share/cmake-2.8/Modules/FindBoost.cmake] 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 -- Philip Lowman ___ Powered by www.kitware.com Visit other Kitware open
[Cmake-commits] CMake branch, next, updated. v2.8.2-1133-g63529b1
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 63529b1c6d7eb82b662a8fe672585c7339d12930 (commit)
via fffe1c07d9029293ef58512890ceb62d8de1df2b (commit)
from b32b3181173681ff0ce041b527638e9d08cbeda6 (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=63529b1c6d7eb82b662a8fe672585c7339d12930
commit 63529b1c6d7eb82b662a8fe672585c7339d12930
Merge: b32b318 fffe1c0
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Thu Oct 28 22:53:27 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Oct 28 22:53:27 2010 -0400
Merge topic '11363' into next
fffe1c0 11363: FindBoost.cmake fails to find debug libraries in tagged
layout install
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fffe1c07d9029293ef58512890ceb62d8de1df2b
commit fffe1c07d9029293ef58512890ceb62d8de1df2b
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Thu Oct 28 22:51:18 2010 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Thu Oct 28 22:51:18 2010 -0400
11363: FindBoost.cmake fails to find debug libraries in tagged layout
install
diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index 3ae4e14..28296f1 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -916,6 +916,7 @@ ELSE (_boost_IN_CACHE)
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}${_boost_DEBUG_ABI_TAG}-${Boost_LIB_VERSION}
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}${_boost_DEBUG_ABI_TAG}
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_MULTITHREADED}${_boost_DEBUG_ABI_TAG}-${Boost_LIB_VERSION}
+
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_MULTITHREADED}${_boost_DEBUG_ABI_TAG}
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_MULTITHREADED}
${Boost_LIB_PREFIX}boost_${COMPONENT} )
if(_boost_STATIC_RUNTIME_WORKAROUND)
---
Summary of changes:
Modules/FindBoost.cmake |1 +
1 files changed, 1 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.2-1054-gad39bab
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 ad39bab508c9b61616a6bf2f58e9ef931402f850 (commit)
via b867a3f1a81b2dcb399a3e39ea8b9454d8f0508f (commit)
from 94040d6299c4afc8bc5244ee8905f41731459bfe (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=ad39bab508c9b61616a6bf2f58e9ef931402f850
commit ad39bab508c9b61616a6bf2f58e9ef931402f850
Merge: 94040d6 b867a3f
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Mon Oct 11 22:56:59 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Oct 11 22:56:59 2010 -0400
Merge topic 'FindBoost_bugfix_cleanup' into next
b867a3f Remove superfluous variable Boost_COMPAT_STATIC_RUNTIME.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b867a3f1a81b2dcb399a3e39ea8b9454d8f0508f
commit b867a3f1a81b2dcb399a3e39ea8b9454d8f0508f
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Mon Oct 11 22:48:33 2010 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Mon Oct 11 22:48:33 2010 -0400
Remove superfluous variable Boost_COMPAT_STATIC_RUNTIME.
There is no need to introduce this extra variable as FindBoost
can simply rely on if Boost_USE_STATIC_RUNTIME is defined
or not to disable the old searching behavior for static runtime
libraries on WIN32.
diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index 2377e10..3ae4e14 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -20,7 +20,6 @@
# set(Boost_USE_STATIC_LIBSON)
# set(Boost_USE_MULTITHREADED ON)
# set(Boost_USE_STATIC_RUNTIMEOFF)
-# set(Boost_COMPAT_STATIC_RUNTIME OFF)
# find_package( Boost 1.36.0 COMPONENTS date_time filesystem system ... )
#
# if(Boost_FOUND)
@@ -94,7 +93,10 @@
#
# Boost_USE_STATIC_RUNTIME If enabled, searches for boost libraries
#linked against a static C++ standard library
-#('s' ABI tag). Defaults to OFF.
+#('s' ABI tag). This option should be set to
+#ON or OFF because the default behavior
+#if not specified is platform dependent
+#for backwards compatibility.
# [Since CMake 2.8.3]
#
# Boost_USE_DEBUG_PYTHON If enabled, searches for boost libraries
@@ -114,14 +116,6 @@
#Defaults to OFF.
# [Since CMake 2.8.3]
#
-# Boost_COMPAT_STATIC_RUNTIME Set to OFF to disable backwards compatible
-#searching for libraries with the 's' ABI
-#tag on WIN32 after normal searches. You
-#should set this to OFF and also set
-#Boost_USE_STATIC_RUNTIME appropriately.
-#If not specified, defaults to ON.
-# [Since CMake 2.8.3]
-#
# Other Variables used by this module which you may want to set.
#
# Boost_ADDITIONAL_VERSIONSA list of version numbers to use for searching
@@ -372,9 +366,6 @@ endfunction()
IF(NOT DEFINED Boost_USE_MULTITHREADED)
SET(Boost_USE_MULTITHREADED TRUE)
ENDIF()
-if(NOT DEFINED Boost_COMPAT_STATIC_RUNTIME)
- set(Boost_COMPAT_STATIC_RUNTIME TRUE)
-endif()
if(Boost_FIND_VERSION_EXACT)
# The version may appear in a directory with or without the patch
@@ -868,11 +859,11 @@ ELSE (_boost_IN_CACHE)
# 1. Search for static libs compiled against a SHARED C++ standard runtime
library (use if found)
# 2. Search for static libs compiled against a STATIC C++ standard runtime
library (use if found)
# We maintain this behavior since changing it could break people's builds.
- # To disable the ambiguous behavior, the user can
- # set Boost_COMPAT_STATIC_RUNTIME to FALSE
+ # To disable the ambiguous behavior, the user need only
+ # set Boost_USE_STATIC_RUNTIME either ON or OFF.
set(_boost_STATIC_RUNTIME_WORKAROUND false)
- if(Boost_COMPAT_STATIC_RUNTIME AND WIN32 AND Boost_USE_STATIC_LIBS)
-if(NOT Boost_USE_STATIC_RUNTIME)
+ if(WIN32 AND Boost_USE_STATIC_LIBS)
+if(NOT DEFINED Boost_USE_STATIC_RUNTIME)
set(_boost_STATIC_RUNTIME_WORKAROUND true)
endif()
endif()
---
Summary of changes:
Modules/FindBoost.cmake | 25 -
1 files changed, 8 insertions(+), 17 deletions(-)
hooks/post-receive
--
CMake
Re: [CMake] Disallowing in-source builds
On Thu, Oct 7, 2010 at 3:19 AM, Michael Wild them...@gmail.com wrote:
On 6. Oct, 2010, at 20:10 , aaron.mead...@thomsonreuters.com
aaron.mead...@thomsonreuters.com wrote:
Hi all.
Is there a good way to disallow in-source builds? Ideally, I'd like to
prevent it before any cruft is written into the source tree. I
experimented with writing a function into my CMakelists file and calling
it. The function checked if CMAKE_BINARY_DIR was equal to
CMAKE_SOURCE_DIR and messaged a FATAL_ERROR if that was the case. This
works ok, but still generates a CMakeFiles directory and a
CMakeCache.txt file.
I don't think there's a way to prevent that from happening. The bad thing
about this is that if the user doesn't clean away the in-source
CMakeCache.txt file, subsequent out-of-source builds will fail. Perhaps you
can do something like this:
# check for polluted source tree
if(EXISTS ${CMAKE_SOURCE_DIR}/CMakeCache.txt OR
EXISTS ${CMAKE_SOURCE_DIR}/CMakeFiles)
message(FATAL_ERROR
CMakeCache.txt or CMakeFiles exists in source directory!)
endif()
# make sure the user doesn't play dirty with symlinks
get_filename_component(srcdir ${CMAKE_SOURCE_DIR} REALPATH)
get_filename_component(bindir ${CMAKE_BINARY_DIR} REALPATH)
# disallow in-source builds
if(${srcdir} STREQUAL ${bindir})
message(FATAL_ERROR In-source builds are forbidden!)
endif()
The second half of the question is of course, is there an easy way to
clean out a source tree if an in-source build was accidentally kicked
off? (short of dividing the files by their timestamp and removing the
newer ones, etc..)
No, simply because CMake cannot. Your build system might have something
like the following:
execute_process(COMMAND echo BOOM ${CMAKE_BINARY_DIR}/boom.txt
VERBATIM)
CMake never knows that the file boom.txt is written, and therefor can't
clean it away.
I think this is a bit of a red herring. CMake could be perfectly capable of
cleaning up after itself (i.e. its own files).
If the user is doing things like making a bunch of files that CMake isn't
aware of (that aren't generated), these could be added to
ADDITIONAL_MAKE_CLEAN_FILES, or a new property could be added for custom
files that are to be deleted on a distclean.
--
Philip Lowman
___
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] Boost Library Search
On Wed, Oct 6, 2010 at 7:55 PM, assume_R assu...@gmail.com wrote: Hey all. So I noticed a possible bug with the way boost is searched in findboost.cmake. Essentially, if you have the boost static runtimes installed, that's what Visual Studio will require. For example, using the thread library, it will need libboost_thread*-sgd* Yet the non-static-runtime versions are what are searched first, so it only finds libboost_thread*-gd*, and visual studio will give you a link error. Yes, this is issue #11204. FindBoost searches for static libraries first with the -gd then -sgd prefix in that order when Boost_USE_STATIC_LIBS is enabled. There was no way to specify if you preferred the static library built against a dynamic runtime, or the static library built against a static runtime. http://www.cmake.org/Bug/view.php?id=11204 Changing the behavior the way you specified could potentially break people that prefer the static boost libraries but with a dynamic runtime, so a better solution was needed. The new version of FindBoost (which is in 2.8.3-rc2) allows you to set a new option (Boost_USE_STATIC_RUNTIME) which allows picking either a static or dynamic runtime. By default FindBoost maintains existing behavior of searching for dynamic then static on WIN32 (since that is the only platform we had this behavior before). On other platforms this wasn't an issue and the dynamic runtime was always used so the existing behavior is maintained there since the user must opt-in to setting Boost_USE_STATIC_RUNTIME. If you try out FindBoost in 2.8.3-rc2 you'll see a reference to Boost_COMPAT_STATIC_RUNTIME which disables the double search behavior if set to OFF. You can set this to OFF for now, but I realized the variable is redundant so if there are more RC's for CMake 2.8.3, I plan on removing it and just counting on if the user has defined Boost_USE_STATIC_RUNTIME or not (regardless if they set it ON or OFF) to disable the double search on WIN32. -- Philip Lowman ___ 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] Disallowing in-source builds
On Wed, Oct 6, 2010 at 2:10 PM, aaron.mead...@thomsonreuters.com wrote: *Hi all.* * * *Is there a good way to disallow in-source builds? Ideally, I’d like to prevent it before any cruft is written into the source tree. I experimented with writing a function into my CMakelists file and calling it. The function checked if CMAKE_BINARY_DIR was equal to CMAKE_SOURCE_DIR and messaged a FATAL_ERROR if that was the case. This works ok, but still generates a CMakeFiles directory and a CMakeCache.txt file.* * **The second half of the question is of course, is there an easy way to clean out a source tree if an in-source build was accidentally kicked off? (short of dividing the files by their timestamp and removing the newer ones, etc..)* CMake doesn't have a command to clean up after itself which seems to be what you're asking for (it would help for both use-cases you specify). This is kind of related to my ticket asking for a distclean target, so I'll just throw it out there in case anyone has some free time on their hands. http://www.cmake.org/Bug/view.php?id=6647 -- Philip Lowman ___ 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] CMakeDetermineVSServicePack.cmake support for vs2010
Aaron,
Thanks for posting. Could you open a new bug report and attach your patch
to it?
On Wed, Sep 29, 2010 at 9:33 PM, aaron.mead...@thomsonreuters.com wrote:
*Hi all. I noticed that CMakeDetermineVSServicePack.cmake only supports
vs2005, vs2005 sp1, vs2008, vs2008 sp1. I wanted to use it for vs2010.*
* *
*I looked for a bug but the only one I found was the one that resulted in
the scripts creation: http://public.kitware.com/Bug/view.php?id=8803*
* *
*I have a patch to fix it: (also attached)*
* *
CMakeDetermineVSServicePack.cmake 2010-06-28 09:42:36.0
-0500*
*--- CMakeDetermineVSServicePackWith2010.cmake 2010-09-29
20:26:20.530212900 -0500*
*
47,52 *
*--- 47,54 *
* set(_version vc90)*
* elseif(${_cl_version} VERSION_EQUAL 15.00.30729.01)*
* set(_version vc90sp1)*
*+elseif(${_cl_version} VERSION_EQUAL 16.00.30319.01)*
*+set(_version vc100)*
* else()*
* set(_version )*
* endif()*
* *
*Should I open a new bug for this and add a patch to it, or reopen the old
bug (feature request) with this patch?*
* *
*Thanks!*
* *
*--aaron*
* *
*Aaron Meadows*
Software Engineer
*Thomson Reuters*
Phone: 314.468.3530
Mobile: 636.541.6139
aaron.mead...@thomsonreuters.com
thomsonreuters.com
This email was sent to you by Thomson Reuters, the global news and
information company.
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of Thomson
Reuters.
___
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
--
Philip Lowman
___
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] CMakeDetermineVSServicePack.cmake support for vs2010
On Thu, Sep 30, 2010 at 11:04 AM, aaron.mead...@thomsonreuters.com wrote: *Done. Issue number 11279. [ http://public.kitware.com/Bug/view.php?id=11279]* * * *I also noted that the script could be improved by calling the compiler with the ‘/?’ switch and parsing it’s output instead of parsing the output from try_compile’ing a simple c file it writes. That would make it quite a bit faster.* Aaron, Thanks for the patch. I've pushed it to git next. Regarding your idea to use the output of cl /? to determine the version number, I think it is a good one. If you have time to rewrite the module to do this instead and test it I would merge the changes for a future version of CMake. Some potential issues. 1. cl /? appears to pause waiting for input, this would have to be mitigated somehow in a safe way or perhaps just cl could be executed as that appears to include the output. 2. cl or cl /? output would have to be verified on VS8 to ensure it outputs there as well (it appears to be there in VS9/Express) 3. You couldn't just run cl, you would have to find out the CMake variable for the compiler and run that. My time is really limited. If you're interested, please create a new ticket and submit a patch. It would save probably at least a second off of an initial configure. -- Philip Lowman ___ 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-851-gacee917
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 acee917d8fa06f8d0e64b13c1ca72cc65486777d (commit)
via 24cb498105703f6e311a5d1064057674dd0decaf (commit)
from c2c5534f1888606b9ef6ac0bbe9c78a66f9a4af2 (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=acee917d8fa06f8d0e64b13c1ca72cc65486777d
commit acee917d8fa06f8d0e64b13c1ca72cc65486777d
Merge: c2c5534 24cb498
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Mon Sep 20 22:31:12 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Sep 20 22:31:12 2010 -0400
Merge topic 'FindBoost_lots_of_fixes' into next
24cb498 Revert Lots of FindBoost bugfixes
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=24cb498105703f6e311a5d1064057674dd0decaf
commit 24cb498105703f6e311a5d1064057674dd0decaf
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Mon Sep 20 22:26:22 2010 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Mon Sep 20 22:29:12 2010 -0400
Revert Lots of FindBoost bugfixes
This reverts commit bc0b19aae0dfc4ec4d43593ad713dcce8c067e83.
and fixes whitespace
diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index 69deb9c..d76c9a8 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -17,10 +17,8 @@
#
# == Using actual libraries from within Boost: ==
#
-# set(Boost_USE_STATIC_LIBSON)
-# set(Boost_USE_MULTITHREADED ON)
-# set(Boost_USE_STATIC_RUNTIMEOFF)
-# set(Boost_COMPAT_STATIC_RUNTIME OFF)
+# set(Boost_USE_STATIC_LIBS ON)
+# set(Boost_USE_MULTITHREADED ON)
# find_package( Boost 1.36.0 COMPONENTS date_time filesystem system ... )
#
# if(Boost_FOUND)
@@ -86,42 +84,6 @@
# Boost_USE_STATIC_LIBSCan be set to ON to force the use of the
static
#boost libraries. Defaults to OFF.
#
-# Boost_NO_SYSTEM_PATHSSet to TRUE to suppress searching in system
-#paths (or other locations outside of
BOOST_ROOT
-#or BOOST_INCLUDEDIR). Useful when specifying
-#BOOST_ROOT. Defaults to OFF.
-# [Since CMake 2.8.3]
-#
-# Boost_USE_STATIC_RUNTIME If enabled, searches for boost libraries
-#linked against a static C++ standard library
-#('s' ABI tag). Defaults to OFF.
-# [Since CMake 2.8.3]
-#
-# Boost_USE_DEBUG_PYTHON If enabled, searches for boost libraries
-#compiled against a special debug build of
-#Python ('y' ABI tag). Defaults to OFF.
-# [Since CMake 2.8.3]
-#
-# Boost_USE_STLPORTIf enabled, searches for boost libraries
-#compiled against the STLPort standard
-#library ('p' ABI tag). Defaults to OFF.
-# [Since CMake 2.8.3]
-#
-# Boost_USE_STLPORT_DEPRECATED_NATIVE_IOSTREAMS
-#If enabled, searches for boost libraries
-#compiled against the deprecated STLPort
-#native iostreams feature ('n' ABI tag).
-#Defaults to OFF.
-# [Since CMake 2.8.3]
-#
-# Boost_COMPAT_STATIC_RUNTIME Set to OFF to disable backwards compatible
-#searching for libraries with the 's' ABI
-#tag on WIN32 after normal searches. You
-#should set this to OFF and also set
-#Boost_USE_STATIC_RUNTIME appropriately.
-#If not specified, defaults to ON.
-# [Since CMake 2.8.3]
-#
# Other Variables used by this module which you may want to set.
#
# Boost_ADDITIONAL_VERSIONSA list of version numbers to use for searching
@@ -144,28 +106,11 @@
#(e.g. -gcc43) if FindBoost has problems
finding
#the proper Boost installation
#
-# Boost_THREADAPIWhen building boost.thread, sometimes the
name of the
-#library contains an additional pthread or
win32
-#string known as the threadapi. This can
happen when
-#compiling against pthreads on Windows
[Cmake-commits] CMake branch, next, updated. v2.8.2-836-g2511163
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 25111637c9b67a6f8349413ad89aaf7aa833abfd (commit)
via 38691d91a58b416fd4698047b037c8123e133e2b (commit)
from 66551b4c1d035aeb36486ffc054b5b30be137876 (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=25111637c9b67a6f8349413ad89aaf7aa833abfd
commit 25111637c9b67a6f8349413ad89aaf7aa833abfd
Merge: 66551b4 38691d9
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sun Sep 19 23:58:26 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sun Sep 19 23:58:26 2010 -0400
Merge topic '11249_FindFLEX' into next
38691d9 FindFLEX.cmake: Fix issue 11249
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=38691d91a58b416fd4698047b037c8123e133e2b
commit 38691d91a58b416fd4698047b037c8123e133e2b
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sun Sep 19 23:56:34 2010 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sun Sep 19 23:56:34 2010 -0400
FindFLEX.cmake: Fix issue 11249
FindFLEX no longer sense a CMake fatal error if executing flex --version
fails
unless the REQUIRED argument was specified.
diff --git a/Modules/FindFLEX.cmake b/Modules/FindFLEX.cmake
index 55b5639..d42e514 100644
--- a/Modules/FindFLEX.cmake
+++ b/Modules/FindFLEX.cmake
@@ -78,7 +78,11 @@ IF(FLEX_EXECUTABLE)
RESULT_VARIABLE FLEX_version_result
OUTPUT_STRIP_TRAILING_WHITESPACE)
IF(NOT ${FLEX_version_result} EQUAL 0)
-MESSAGE(SEND_ERROR Command \${FLEX_EXECUTABLE} --version\ failed with
output:\n${FLEX_version_error})
+IF(FLEX_FIND_REQUIRED)
+ MESSAGE(SEND_ERROR Command \${FLEX_EXECUTABLE} --version\ failed with
output:\n${FLEX_version_output}\n${FLEX_version_error})
+ELSE()
+ MESSAGE(Command \${FLEX_EXECUTABLE} --version\ failed with
output:\n${FLEX_version_output}\n${FLEX_version_error}\nFLEX_VERSION will not
be available)
+ENDIF()
ELSE()
STRING(REGEX REPLACE ^flex (.*)$ \\1
FLEX_VERSION ${FLEX_version_output})
---
Summary of changes:
Modules/FindFLEX.cmake |6 +-
1 files changed, 5 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.2-834-g66551b4
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 66551b4c1d035aeb36486ffc054b5b30be137876 (commit) via 7016fae6d4c0a58fcbf74ee29bf25a7b5e2cf369 (commit) via c30c3ade9bfd865bea8e58d38e4044e4b00334a0 (commit) via 4b682e13fb0e4810d6cb8b76602c715a6fd74247 (commit) via 48a126717c2747e778f724fd536504e12e015b0c (commit) from a00839fa3b53cdcba1f2d13da593b06b9f9ae3a1 (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=66551b4c1d035aeb36486ffc054b5b30be137876 commit 66551b4c1d035aeb36486ffc054b5b30be137876 Merge: a00839f 7016fae Author: Philip Lowman phi...@yhbt.com AuthorDate: Sat Sep 18 13:51:33 2010 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Sat Sep 18 13:51:33 2010 -0400 Merge topic '11136' into next 7016fae Fix 11136: [patch] FindThreads.cmake documents the wrong variable c30c3ad KWSys Nightly Date Stamp 4b682e1 KWSys Nightly Date Stamp 48a1267 KWSys Nightly Date Stamp http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7016fae6d4c0a58fcbf74ee29bf25a7b5e2cf369 commit 7016fae6d4c0a58fcbf74ee29bf25a7b5e2cf369 Author: Philip Lowman phi...@yhbt.com AuthorDate: Sat Sep 18 13:46:08 2010 -0400 Commit: Philip Lowman phi...@yhbt.com CommitDate: Sat Sep 18 13:46:08 2010 -0400 Fix 11136: [patch] FindThreads.cmake documents the wrong variable Fixed documentation to be correct. diff --git a/Modules/FindThreads.cmake b/Modules/FindThreads.cmake index 25d48d1..4cb7451 100644 --- a/Modules/FindThreads.cmake +++ b/Modules/FindThreads.cmake @@ -6,7 +6,7 @@ # CMAKE_USE_PTHREADS_INIT- are we using pthreads # CMAKE_HP_PTHREADS_INIT - are we using hp pthreads # For systems with multiple thread libraries, caller can set -# CMAKE_THREAD_PREFER_PTHREADS +# CMAKE_THREAD_PREFER_PTHREAD #= # Copyright 2002-2009 Kitware, Inc. --- Summary of changes: Modules/FindThreads.cmake |2 +- Source/kwsys/kwsysDateStamp.cmake |2 +- 2 files changed, 2 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, next, updated. v2.8.2-755-gc134483
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 c134483df8c0fecd91f63796eb8f7fd9ca8e62c9 (commit)
via bc0b19aae0dfc4ec4d43593ad713dcce8c067e83 (commit)
via 3665e69bc660fd3e872a141090d38650c6c271ac (commit)
via c36f501a6465e024f69c8e9bfb13ba37229fd2fd (commit)
from 9c22a2f489de5bd01b15a04cedfc3b523ae421ad (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=c134483df8c0fecd91f63796eb8f7fd9ca8e62c9
commit c134483df8c0fecd91f63796eb8f7fd9ca8e62c9
Merge: 9c22a2f bc0b19a
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sun Sep 12 22:16:57 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Sun Sep 12 22:16:57 2010 -0400
Merge topic 'FindBoost_lots_of_fixes' into next
bc0b19a Lots of FindBoost bugfixes
3665e69 KWSys Nightly Date Stamp
c36f501 KWSys Nightly Date Stamp
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bc0b19aae0dfc4ec4d43593ad713dcce8c067e83
commit bc0b19aae0dfc4ec4d43593ad713dcce8c067e83
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Sun Sep 12 22:08:28 2010 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Sun Sep 12 22:16:09 2010 -0400
Lots of FindBoost bugfixes
(Due to a problem with one of my many git commits on my branch being
rejected on push due to whitespace issues, I have consolidated all of the
changes into one commit.)
* Fixes issue 11192 11187 compiling against a boost source tree with or
without compiled
libraries within it.
* Fixed issue 11204: FindBoost.cmake has trouble discovering libraries
when both -sgd and -gd libraries are available by adding a new option
Boost_USE_STATIC_RUNTIME. Maintained backwards compatibility of
searching for
the static runtime library when necessary (on WIN32),
although this behavior can be disabled by setting a compatibility
variable.
* Fixes issue 10436, Add an additional library filename permutation which
fixes
detection for some custom builds of Boost
* Fixes issue 11121, add support for finding Boost.Thread with special
THREADAPI flag
* Fixed issue 8529: FindBoost was unable to detect boost libraries compiled
against
STLport, by reworking the way the Boost ABI tag is calculated. There are
additional
options for configuring this now.
* Added Boost_NO_SYSTEM_PATHS variable for excluding the system paths from
the search,
this fixed several duplicate issues in the tracker (7725, 11019, 8412)
* Added additional debug output to include list of filenames being searched
for.
* Fixed bug where in rare circumstances a shared library (.so) would be
found when Boost_USE_STATIC_LIBS was enabled
* General code cleanup
diff --git a/Modules/FindBoost.cmake b/Modules/FindBoost.cmake
index 1a1b168..69deb9c 100644
--- a/Modules/FindBoost.cmake
+++ b/Modules/FindBoost.cmake
@@ -17,8 +17,10 @@
#
# == Using actual libraries from within Boost: ==
#
-# set(Boost_USE_STATIC_LIBS ON)
-# set(Boost_USE_MULTITHREADED ON)
+# set(Boost_USE_STATIC_LIBSON)
+# set(Boost_USE_MULTITHREADED ON)
+# set(Boost_USE_STATIC_RUNTIMEOFF)
+# set(Boost_COMPAT_STATIC_RUNTIME OFF)
# find_package( Boost 1.36.0 COMPONENTS date_time filesystem system ... )
#
# if(Boost_FOUND)
@@ -84,6 +86,42 @@
# Boost_USE_STATIC_LIBSCan be set to ON to force the use of the
static
#boost libraries. Defaults to OFF.
#
+# Boost_NO_SYSTEM_PATHSSet to TRUE to suppress searching in system
+#paths (or other locations outside of
BOOST_ROOT
+#or BOOST_INCLUDEDIR). Useful when specifying
+#BOOST_ROOT. Defaults to OFF.
+# [Since CMake 2.8.3]
+#
+# Boost_USE_STATIC_RUNTIME If enabled, searches for boost libraries
+#linked against a static C++ standard library
+#('s' ABI tag). Defaults to OFF.
+# [Since CMake 2.8.3]
+#
+# Boost_USE_DEBUG_PYTHON If enabled, searches for boost libraries
+#compiled against a special debug build of
+#Python ('y' ABI tag). Defaults to OFF.
+# [Since CMake 2.8.3]
+#
+# Boost_USE_STLPORTIf enabled, searches for boost libraries
+#compiled against the STLPort standard
[CMake] Volunteering to become maintainer of FindBoost.cmake
Hi everyone, I'm volunteering to become the primary maintainer of FindBoost.cmake. -- Philip Lowman ___ 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] Volunteering to become maintainer of FindBoost.cmake
Part of the problem is that it's not clear if the user has built boost-thread against pthreads or win32 threads. See the fix for #11121, I've added a variable to control which threading library gets used if the user crosscompiles boost-thread using a thread-api that isn't native on their system. http://www.cmake.org/Bug/view.php?id=11121 http://www.cmake.org/Bug/view.php?id=11121Maybe we can just require users to specify pthreads for this and when they do we could link to pthreads? But is this regular pthreads or pthreads-win32 we're talking about? Really we need to fix 6399 first. For now I would just recommend adding the target_link_library manually against pthreads when you're using it and ensure we have a bug filed for this issue in the tracker. On Fri, Sep 10, 2010 at 1:29 PM, Matthew Woehlke matthew.woeh...@kitware.com wrote: On 09/10/2010 09:02 AM, Philip Lowman wrote: Hi everyone, I'm volunteering to become the primary maintainer of FindBoost.cmake. First off, thank you for volunteering! I hope I will not frighten you off with a request so soon :-). I've run into a couple boost-using projects lately that fail to build because they use pthread (often via boost templates), but don't explicitly link pthread. (I think previously this was not an issue due to indirect linking, i.e. MyProject links to boost which links to pthread, therefore MyProject can use pthread. However, Fedora now disallows this sort of linking, such that MyProject must link pthread itself - I believe this is an early-adoption of new upstream practice.) Given how template-heavy boost is, I'm thinking the best solution is for Boost_LIBRARIES to include pthread, rather than such projects needing to find_package(threads) and link_libraries the libraries therefrom. What do you think? Any advice how to proceed patching FindBoost.cmake? -- Matthew -- Philip Lowman ___ 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] Loop expansion in find_library() seems backwards
Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4 nspr4a
HINTS ${CMAKE_CURRENT_SOURCE_DIR}
)
I'm somewhat surprised that the following code finds /usr/lib/libnspr4.so
instead of the alternate name for it (libnspr4a.so). This tells me that the
loop is backwards. Shouldn't the find_library() command be iterating the
list of library names across each directory. For example, the above should
search:
First ${CMAKE_CURRENT_SOURCE_DIR}...
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
Then the system directories...
(system paths)/lib/libnspr4.so
(system paths)/lib/libnspr4a.so
Etc.
The system is actually searching
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4.so
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
/usr/lib/libnspr4a.so
This is with CMake 2.8.2
--
Philip Lowman
___
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] Loop expansion in find_library() seems backwards
Wow, that's pretty bad. I even replied to one of those threads. Sorry for
the noise. The official bug post for this issue is here:
http://public.kitware.com/Bug/view.php?id=10718
I agree with Alan Irwin that it will continue to haunt users well into the
future.
On Wed, Sep 8, 2010 at 2:38 AM, Michael Wild them...@gmail.com wrote:
On 8. Sep, 2010, at 8:25 , Philip Lowman wrote:
Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4 nspr4a
HINTS ${CMAKE_CURRENT_SOURCE_DIR}
)
I'm somewhat surprised that the following code finds /usr/lib/libnspr4.so
instead of the alternate name for it (libnspr4a.so). This tells me that
the
loop is backwards. Shouldn't the find_library() command be iterating the
list of library names across each directory. For example, the above
should
search:
First ${CMAKE_CURRENT_SOURCE_DIR}...
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
Then the system directories...
(system paths)/lib/libnspr4.so
(system paths)/lib/libnspr4a.so
Etc.
The system is actually searching
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4.so
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
/usr/lib/libnspr4a.so
This is with CMake 2.8.2
--
Philip Lowman
Oh, no! This topic haunts the list ;-) See
http://www.mail-archive.com/cmake@cmake.org/msg30602.html
http://www.mail-archive.com/cmake@cmake.org/msg28946.html
http://www.mail-archive.com/cmake@cmake.org/msg27838.html
http://www.mail-archive.com/cmake@cmake.org/msg24565.html
Michael
--
There is always a well-known solution to every human problem -- neat,
plausible, and wrong.
H. L. Mencken
--
Philip Lowman
___
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] Loop expansion in find_library() seems backwards
On Wed, Sep 8, 2010 at 8:56 AM, Michael Hertling mhertl...@online.dewrote:
...which shows that 10718 is still alive. ;-)
Hi Philip,
what's your opinion on this topic, in particular
- swapping loops and the required effort, the related risks
and the expected results,
I'd like to know if there is a use case for the existing behavior. I don't
really have an opinion if this should be enabled optionally or by default
(or via policy) yet.
- find modules with hardcoded magic numbers and the continuous
need for maintenance,
- globbing or regex support for FIND_{PROGRAM,LIBRARY,PATH,FILE}?
I've griped about this for a while. So much that I even started working on
a patch for the issue back when I had some free time last year (but never
finished). What little time I have these days to spend on CMake I choose to
spend on supporting find modules, so if anyone wants to take this over... It
was one approach for how to solve the version number problem...
http://www.cmake.org/Bug/view.php?id=8396
--
Philip Lowman
___
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] FindBoost.cmake trouble with static libs (-gd vs -sgd issue)
Shane,
Thanks for opening ticket 11204 for this issue. My response is included
there.
http://public.kitware.com/Bug/view.php?id=11204
On Thu, Sep 2, 2010 at 4:08 PM, Dixon, Shane shane.di...@atmel.com wrote:
I found that when using the FindBoost.cmake and using the
Boost_USE_STATIC_LIBS option, it wouldn’t find the static libs in my
C:\Boost\libs folder. It kept coming back with files ending in –gd libs
instead of –sgd libs even though the option Boost_USE_STATIC_LIBS was set.
I found that it had to do with the order that the FIND_LIBRARY looks for the
files. I had BOTH the –gd and the –sgd libraries installed so it found the
–gd ones first and then ignores the next option. I fixed it by applying the
following:
728,729c728,729
NAMES
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}-${_boost_ABI_TAG}-${Boost_LIB_VERSION}
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}${_boost_STATIC_TAG}${_boost_ABI_TAG}-${Boost_LIB_VERSION}
---
NAMES
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}${_boost_STATIC_TAG}${_boost_ABI_TAG}-${Boost_LIB_VERSION}
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}-${_boost_ABI_TAG}-${Boost_LIB_VERSION}
I just switched the order to look for the more specific lib before the more
general one. If ${_boost_STATIC_TAG} is empty when Boost_USE_STATIC_LIBS is
OFF, then maybe this could just be one line:
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}${_boost_STATIC_TAG}${_boost_ABI_TAG}-${Boost_LIB_VERSION}
Which seems like it should find either –sgd or –gd files, but sould find
–sgd files first if the option was provided. Any thoughts? I defer to
anyone with more experience for the best way to do this.
--
Shane
___
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
--
Philip Lowman
___
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] FindOpenSSL.cmake
Officially, CMake modules are supposed to mark cache variables like this as advanced so they disappear as soon as they are set. Since it is finding DLL files the cache variables are being set and immediately hidden in the advanced section of the cache. You should be able to get at them from the advanced section of the cache editor and change them to the appropriate .LIB files to work around the issue (choose advanced from the select dropdown). The reason why it is detecting DLL files should be investigated. Can you please open a bug ticket with the information here? Also it should contain: 1. What version of OpenSSL are you using (precompiled or did you build it yourself). If the former please point to the location on the net, if the latter please include a directory listing of the install prefix. 2. What generator/compiler are you using with CMake (MinGW? Visual Studio X?) http://www.cmake.org/Bug On Tue, Aug 31, 2010 at 4:35 PM, Dixon, Shane shane.di...@atmel.com wrote: I’m having some trouble with the FindOpenSSL.cmake. While troubleshooting, I noticed that it has this line: MARK_AS_ADVANCED(OPENSSL_INCLUDE_DIR OPENSSL_LIBRARIES) Yet the OPENSSL_LIBRARIES never show up in the cmake-gui. I’m running 2.8.2 on Windows XP. Can someone tell me if I’m wrong to expect that to show up in the GUI when the “advanced” checkbox is checked? The OPENSSL_LIBRARIES always gets populated with .dll files instead of .lib files. I was going to manually set it to the correct thing (which seems to be the point of setting a variable to advanced) and the variable doesn’t show up at all. -- Shane ___ 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 -- Philip Lowman ___ 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] detecting libc version info
On Tue, Aug 31, 2010 at 3:01 PM, Tim St. Clair timoth...@gmail.com wrote: Is there a handy dandy marco for detecting libc details (e.g. version). Probably not. You can use preprocessor checks though. glibc: http://predef.sourceforge.net/prelib.html#sec3 gcc: http://predef.sourceforge.net/precomp.html#sec15 HTH -- Philip Lowman ___ 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-developers] Bug fix requests for the *next* release of CMake...
David, Thanks for enabling this. If anyone is wondering where to find the Target Release and Fixed In Version fields, they are under the Advanced Details link for each bug. When you mark a bug as fixed, it prompts you for Fixed In Version but the only way to set Target Release I can see is under Advanced (just an FYI for people). On Tue, Aug 31, 2010 at 6:35 PM, David Cole david.c...@kitware.com wrote: Great idea! There is now a roadmap page in Mantis for the CMake project. http://public.kitware.com/Bug/roadmap_page.php It has 33 issues listed as targeted for 2.8.3. 17 of these (51%) are resolved: fixed in 'next' already, or won't fix... ever. The remaining 16 shall be fixed (or marked as postponed to the next release) over the next couple of weeks, and then we'll be ready for the first RC of CMake 2.8.3. Thanks to all of you who participated in this thread. It helped us organize around what people think is most important. Cheers, David Cole Kitware, Inc. P.S. -- there were 40-something issues mentioned specifically in this thread. The 33 listed on the roadmap plus the following 13, which we decided should be looked at for a future release, if ever, but certainly not in the time remaining before 2.8.3 http://public.kitware.com/Bug/view.php?id=5796 http://public.kitware.com/Bug/view.php?id=7867 http://public.kitware.com/Bug/view.php?id=7919 http://public.kitware.com/Bug/view.php?id=8466 http://public.kitware.com/Bug/view.php?id=8486 http://public.kitware.com/Bug/view.php?id=10199 http://public.kitware.com/Bug/view.php?id=10200 http://public.kitware.com/Bug/view.php?id=10335 http://public.kitware.com/Bug/view.php?id=10389 http://public.kitware.com/Bug/view.php?id=10476 http://public.kitware.com/Bug/view.php?id=10752 http://public.kitware.com/Bug/view.php?id=10895 http://public.kitware.com/Bug/view.php?id=10939 There should be a note attached to each of these that says something like not working on this for 2.8.3... Thanks, D. On Fri, Jul 30, 2010 at 4:18 PM, Brian Davis bitmi...@gmail.com wrote: Can a roadmap be posted for CMake? Such as is for other projects at: http://www.cmake.org/Bug/roadmap_page.php ___ cmake-developers mailing list cmake-develop...@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- Philip Lowman ___ 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] FindBoost.cmake in 2.8.2 _Boost_KNOWN_VERSIONS variable
Someone has included 1.44 in the latest FindBoost.cmake in git.
On Wed, Aug 25, 2010 at 3:35 PM, Dixon, Shane shane.di...@atmel.com wrote:
I was had trouble getting FindBoost.cmake to work correctly and I found
that there was a variable I had to adjust in the FindBoost.cmake file:
set(_Boost_KNOWN_VERSIONS ${Boost_ADDITIONAL_VERSIONS}
1.41.0 1.41 1.40.0 1.40 1.39.0 1.39 1.38.0 1.38
1.37.0 1.37
1.36.1 1.36.0 1.36 1.35.1 1.35.0 1.35 1.34.1 1.34.0
1.34 1.33.1 1.33.0 1.33)
I’m using cmake 2.8.8. I had to add “1.44.0” to the list because that’s
the newest version. From their website it looks like this file ought to be
fixed to reflect the new versions:
set(_Boost_KNOWN_VERSIONS ${Boost_ADDITIONAL_VERSIONS}
“1.44.0” “1.44” “1.43.0” “1.43” “1.42.0” “1.42” 1.41.0 1.41
1.40.0 1.40
1.39.0 1.39 1.38.0 1.38 1.37.0 1.37 1.36.1 1.36.0
1.36 1.35.1 1.35.0
1.35 1.34.1 1.34.0 1.34 1.33.1 1.33.0 1.33)
Maybe there’s a pre-release checklist of items that get updated before each
list that this can be added to. It looks like this variable will need to be
constantly updated. After I added “1.44.0” to the list, it works as
expected.
--
Shane
___
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
--
Philip Lowman
___
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-543-g7485a2c
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 7485a2c94938a83187ea938ac6ebb690f7990abf (commit)
via 78289320dd40065864666432e0f7527e9b637157 (commit)
from 5cb07af0601286e1ab18a2208cb7ae07d2aaa411 (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=7485a2c94938a83187ea938ac6ebb690f7990abf
commit 7485a2c94938a83187ea938ac6ebb690f7990abf
Merge: 5cb07af 7828932
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Thu Aug 26 00:17:35 2010 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Aug 26 00:17:35 2010 -0400
Merge topic 'FindGTK2_10688' into next
7828932 10688: FindGTK2.cmake doesn't auto-detect macports
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=78289320dd40065864666432e0f7527e9b637157
commit 78289320dd40065864666432e0f7527e9b637157
Author: Philip Lowman phi...@yhbt.com
AuthorDate: Thu Aug 19 22:03:44 2010 -0400
Commit: Philip Lowman phi...@yhbt.com
CommitDate: Thu Aug 19 22:05:05 2010 -0400
10688: FindGTK2.cmake doesn't auto-detect macports
diff --git a/Modules/FindGTK2.cmake b/Modules/FindGTK2.cmake
index 3b99ae2..4f341e7 100644
--- a/Modules/FindGTK2.cmake
+++ b/Modules/FindGTK2.cmake
@@ -66,7 +66,9 @@
# (To distribute this file outside of CMake, substitute the full
# License text for the above reference.)
-# Version 1.0 (8/12/2010)
+# Version 1.1 (8/19/2010) (CMake 2.8.3)
+# * Add support for detecting GTK2 under macports (thanks to Gary Kramlich)
+# Version 1.0 (8/12/2010) (CMake 2.8.3)
# * Add support for detecting new pangommconfig.h header file
# (Thanks to Sune Vuorela the Debian Project for the patch)
# * Add support for detecting fontconfig.h header
@@ -184,6 +186,8 @@ function(_GTK2_FIND_INCLUDE_DIR _var _hdr)
/usr/openwin/lib
/sw/include
/sw/lib
+/opt/local/include
+/opt/local/lib
$ENV{GTKMM_BASEPATH}/include
$ENV{GTKMM_BASEPATH}/lib
[HKEY_CURRENT_USER\\SOFTWARE\\gtkmm\\2.4;Path]/include
---
Summary of changes:
Modules/FindGTK2.cmake |6 +-
1 files changed, 5 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
Re: [CMake] CTest: Any way around the one test == one program invocation assumption?
On Tue, Jun 8, 2010 at 4:32 AM, Chris Hillery chillery-cm...@lambda.nuwrote: On Tue, Jun 8, 2010 at 1:00 AM, Biddiscombe, John A. biddi...@cscs.chwrote: I'm sure someone has a better answer ... but ... I have complete control over the test program and can make it output whatever I want. Have a look at the XML produced by ctest itself and generate it yourself? then submit it and you should see each test separately (Just thinking out loud) Yeah, worst case I'll head down that path. It's a hairy path though. For instance, I'd still definitely want to run normal ctest tests as well, which means the XML would need to be merged in some fashion. Also, it seems like doing it that way opens you up to possible problems later if ctest or cdash change the XML format at all. All in all it'd be much nicer if there was some kind of hook in ctest which could be used to inform it that a number of tests had been run, and let it populate and submit the XML report based on that information. But, if there's any way to do that, it's highly undocumented... It doesn't appear like there is a class for storing the test results before serializing the XML document to a file. Sounds like that's what would have to be written. cmCTestTestHandler::GenerateDartOutput Looks like it may be a place to start? -- Philip Lowman ___ 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] FindThreads.cmake
26http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l26# Do we have sproc? 27http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l27IF(CMAKE_SYSTEM MATCHES IRIX) 28http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l28 CHECK_INCLUDE_FILES(sys/types.h;sys/prctl.h CMAKE_HAVE_SPROC_H) 29http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l29ENDIF() 30http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l30 31http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l31IF(CMAKE_HAVE_SPROC_H) 32http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l32 # We have sproc 33http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l33 SET(CMAKE_USE_SPROC_INIT 1) 34http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindThreads.cmake;h=459129bc4ab0634c2c42feabbd6f37dc4110c700;hb=HEAD#l34ELSE() Clinton, I would add a variable to FindThreads above that if set avoids the call to CHECK_INCLUDE_FILES(). Then you can test the pthread functionality in the ELSE() block and see if it works properly on IRIX and submit a patch to the bugtracker. On Tue, Jun 1, 2010 at 1:21 PM, Clinton Stimpson clin...@elemtech.comwrote: How can I make FindThreads.cmake find pthreads on IRIX instead of sproc? Thanks, Clint ___ 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 -- Philip Lowman ___ 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] FindBoost problem
Did you set Boost_ADDITIONAL_VERSIONS? Check the FindBoost documentation if you didn't do this. On Wed, May 26, 2010 at 1:52 PM, Nico Schlömer nico.schloe...@gmail.comwrote: Hi all, I'd like to use CMake for an application that I'm developing on an Ubuntu machine which needs to link against Boost, i.e., a custom-compiled installation at /opt/boost/1.43.0/. I compiled and installed CMake 2.8.1, FindBoost.cmake comes in handy. Ubuntu ships with its own Boost development package (1.40.0) which I cannot remove because it's used by other packages. By default, CMake finds the stock-Boost (I guess b/c it sits in those default folders), so I call cmake with cmake -DBOOST_ROOT:PATH=/opt/boost/1.43.0/ /path/to/source/ Boost is found, and the variables are set in CMakeCache.txt, e.g., Boost_INCLUDE_DIR:PATH=/opt/boost/1.43.0/include I however also notice that the actual libraries are *not* set correctly, as Boost_FILESYSTEM_LIBRARY:FILEPATH=/usr/lib/libboost_filesystem-mt.so This makes the build fail. Setting BOOST_LIBRARYDIR does not help. Could that be a bug in CMake? Cheers, Nico ___ 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 -- Philip Lowman ___ 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 link my project with Boost.Thread using CMake
I'm not sure what the problem is exactly, but I've seen that kind of error
message before so I think it's just a configuration problem. What version
of CMake are you running?
On Sun, May 23, 2010 at 11:38 AM, Clark Gaebel cg.wowus...@gmail.comwrote:
Yeah. Sorry, in my effort to remove the extra cruft I messed that up.
Just image they're matching :)
On 05/23/10 11:36, Philip Lowman wrote:
On Sun, May 23, 2010 at 10:31 AM, Clark Gaebel cg.wowus...@gmail.com
wrote:
When I link Boost.Thread to my boost_test executable, it gives me
make[2]: *** No rule to make target `/usr/lib64/libboost_thread-mt.so',
needed by `gogo/test/test_boost'. Stop.
when I make it. Here's the offending CMake code, what am I doing wrong?
add_executable(test_boost test_boost.cpp)
add_test(test_boost test_boost)
# Boost auto-links for MSVC, so we exclude
it.if(CMAKE_COMPILER_IS_GNUCXX)
target_link_libraries(test_boost #LINK_INTERFACE_LIBRARIES
${Boost_THREAD_LIBRARY}
)
endif()
Don't you want:
target_link_libraries(boost_test ${Boost_THREAD_LIBRARY})
instead of test_boost?
--
Regards,
-Clark
--
Philip Lowman
___
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 link my project with Boost.Thread using CMake
On Sun, May 23, 2010 at 10:31 AM, Clark Gaebel cg.wowus...@gmail.comwrote:
When I link Boost.Thread to my boost_test executable, it gives me
make[2]: *** No rule to make target `/usr/lib64/libboost_thread-mt.so',
needed by `gogo/test/test_boost'. Stop.
when I make it. Here's the offending CMake code, what am I doing wrong?
add_executable(boost_test boost_test.cpp)
add_test(boost_test boost_test)
# Boost auto-links for MSVC, so we exclude it.if(CMAKE_COMPILER_IS_GNUCXX)
target_link_libraries(test_boost #LINK_INTERFACE_LIBRARIES
${Boost_THREAD_LIBRARY}
)
endif()
Don't you want:
target_link_libraries(boost_test ${Boost_THREAD_LIBRARY})
instead of test_boost?
--
Philip Lowman
___
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.1 / Win: Neither if nor else?`
On Sat, May 22, 2010 at 4:50 AM, Droscy drosc...@yahoo.it wrote: The right construct is IF(ZLIB_FOUND) MESSAGE( WARNING HAVE system zlib ) ELSE(ZLIB_FOUND) MESSAGE( WARNING NO system zlib ) ENDIF(ZLIB_FOUND) And if compatibility with CMake 2.4.4 isn't a concern, an even better way to do this is: # set this at your topmost CMakeLists.txt set(CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS true) if(ZLIB_FOUND) message(HAVE system zlib) else() message(NO system zlib) endif() P.S. The WARNING option to message() is new to CMake 2.8. For better compatibility with CMake 2.6 and lower, simply omit it which should give you a similar effect. -- Philip Lowman ___ 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] Linking error with VS2005
It also may be caused by linking code compiled with /MT against code compiled with /MD (or vice versa). On Fri, May 21, 2010 at 10:48 AM, Chuck Atkins chuck.atk...@kitware.comwrote: Does the problem happen in both Debug and Release builds? Visual C++ has a well known problem of mixing debug and release libraries together. My suspicion is that you have some dependant libraries that are only built in Debug or only built in Release. With Visual C++ it is important that all libraries and dependencies as well as the project code it's self be built in the same Build Configuration (Debug or Release). Mixing the two will often give rise to problems such as these. Chuck Atkins -- Mathematicians are tools for turning coffee grounds into formulas., Paul Erdos On Fri, May 21, 2010 at 8:01 AM, Daanen Vincent daa...@koelis.com wrote: Dear Cmake users, I'm facing to a problem I can't resolve. I'm developping on a windows XP SP3 box with Visual Studio 2005. I have a project using itk which compile fine. For some reason, I try to use cmake to generate the same project and I got linker error (conflict between msvcrtd.lib and libcmtd.lib) - I check that the librairies are declared in the same order in both project and it's ok - Try to ignore either msvcrtd.lib or libcmtd.lib but I does not work : other linker errors appear. I could not find what is specifically added by cmake so that the cmake-generated project fails to build the binray whereas the manually-generated project file succeeds... Is there someone who could help me ? Thanks Vince ___ 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 -- Philip Lowman ___ 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] VS-C++ Express Version
This is Microsoft's fault. You should complain to them. The only workaround for VS Express is to close your solution and run CMake manually then open your solution back up again. The problem doesn't affect VS Professional (and I believe Standard) because they have support for macros which CMake takes advantage of to reload all of the VS project files without a lot of user interaction. On Fri, May 14, 2010 at 7:55 AM, Micha Renner micha.ren...@t-online.dewrote: There are some things in the cooperation of CMake and the Visual Studio Express-version, which which bothers me. Each change in a CMakeLists.txt file results in a message of VS Express like this: The filter file of your project changed outside VS! Do you want reload it? I could live with this, but this message is presented also for sub-projects whose CMakeLists.txt file was not changed. Let say one have a project with 5 sub-projects with one target. A change of one CMakeLists.txt results in the five-fold display of the message above plus the display for ALL_BUILD, RUN_TESTS, INSTALL and uninstall. This means I have to confirm 9 times that I want to reload the filter file of the projects. That is too much. More worse: If the the projects have more then one target, you have to confirm the reload of the filter files for each target. Greetings Micha ___ 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 -- Philip Lowman ___ 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] VS-C++ Express Version
David, Thanks for the clarification. I missed the filters part in the original message and don't have VS10. Does VS10 still have the same problem with there not being a Reload All button for modified project files that previous versions of VS had? If this small feature were added by Microsoft there would be no need for all of the crazy macro stuff. On Fri, May 14, 2010 at 10:53 AM, David Cole david.c...@kitware.com wrote: On Fri, May 14, 2010 at 8:02 AM, Philip Lowman phi...@yhbt.com wrote: This is Microsoft's fault. You should complain to them. Well, yes and no. It's a Visual Studio 2010 only thing... And it's partly CMake's fault. The *.filters files are presently unconditionally re-written at CMake time. We have a fix for that part of it that will be in the next release of CMake. (It's not even in git master, yet, though.) I'll push it today. And the reload macros are not working as well as they did in prior Visual Studio versions. This is a VS change that we have not figured out yet how to compensate for... The only workaround for VS Express is to close your solution and run CMake manually then open your solution back up again. The problem doesn't affect VS Professional (and I believe Standard) because they have support for macros which CMake takes advantage of to reload all of the VS project files without a lot of user interaction. The *.filters problem affects all versions of Visual Studio 2010. The fix will be in git master later today. Thanks, David Cole -- Philip Lowman ___ 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: could NOT find Boost
Usually you can get away with deleting just the cached variables that a find module create (i.e. ZLIB_LIBRARY, etc.). Boost is one of the few modules where this doesn't always work because it creates internal cached variables that don't show up in the cache editor. On Wed, May 5, 2010 at 9:57 AM, Michael Hertling mhertl...@online.dewrote: On 05/04/2010 07:19 PM, Mike Ladwig wrote: The clean build tree seems to have been the problem. Looks as if I needed to start clean every time I tried a new configuration approach. Much thanks! Typically, if FIND_PACKAGE() succeeds in locating a package the results are cached, and if you reconfigure later FIND_PACKAGE() usually doesn't search again, but reuses the previously found results from the cache. Therefore, you must ensure that FIND_PACKAGE() is lead to the desired package right at the first time. If this package is missed you should actually restart the configuration from within a clean directory, i.e. without a cache. In general, if you have installed multiple versions of the same package be particularly careful w.r.t. which of them is going to be found by FIND_PACKAGE(). Regards, Michael On Tue, May 4, 2010 at 1:01 PM, S Roderick kiwi@mac.com wrote: On May 4, 2010, at 12:41 , Mike Ladwig wrote: Hi. I'm having a problem compiling scantailor on CentOS 5.4. The version of cmake that comes with CentOS was too old, so I downloaded the current cmake binary, which seems to be working well. The problem is that the CentOS version of boost is also out-of-date, so I needed to download and build that, which I did successfully. I installed the new boost (1.42) in /usr/local and have been unable to get cmake to recognize it. I have tried -DBOOST_ROOT=/usr/local/ -DBOOSTROOT=/usr/local/ -DBOOST_INCLUDEDIR=/usr/local/include/ -DBOOST_LIBRARYDIR=/usr/local/lib/ -DBoost_ADDITIONALVERSIONS=1.42.0 and many variations on these. Am I missing something, or is cmake just unable to find boost anywhere other than default locations? Have you tried (in a clean build tree) export CMAKE_PREFIX_PATH=/usr/local cmake ... The above works with MacPorts installed boost v1.42 in /opt/local for Mac OS X. 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 -- Philip Lowman ___ 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] FIND_LIBRARY in FindBoost finds wrong library
On Mon, Mar 22, 2010 at 4:05 AM, Marcel Loose lo...@astron.nl wrote: Hi Chuck, Whatever way you look at it, problems will likely arise sooner or later with different Boost versions. I ran into this problem because /usr/lib/libboost_date_time-mt.so was found before /home/loose/boost-1.40.0/lib/libboost_date_time.so. My point in turning the loop inside out stems from the fact that there are dozens of FindXXX modules that may be vulnerable to the same problem. To name a few: FindGTK, FindLua50, FindPNG, FindWxWindows, etc. W.r.t. FindBoost, maybe it's wise to use BOOST_ROOT exclusively when specified. That would at least preclude the current problems. BTW: Is there a reason why I cannot specify options like NO_CMAKE_ENVIRONMENT_PATH, NO_SYSTEM_ENVIRONMENT_PATH, etc. with FIND_PACKAGE(), except when using config mode? You could modify the FIND_PACKAGE() interface to support options like these and then fix all of the CMake modules to handle the new options. Alternatively, there could be a global CMake property or variable for enabling these. A combination could also be used (if necessary, property is set at start of find_package() and subsequently unset at end). -- Philip Lowman ___ 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] FIND_LIBRARY in FindBoost finds wrong library
On Fri, Mar 19, 2010 at 10:22 AM, Chuck Atkins chuck.atk...@kitware.com wrote: /home/myuser/projects/boost-1.41.0/lib/libboost_date_time-mt.so /home/myuser/projects/boost-1.41.0/lib/libboost_thread-mt.so /usr/local/lib/libboost_filesystem-mt.so /usr/local/lib/libboost_python-mt.so This mix and match is definitely not desired. It almost seems like if the BOOST_ROOT variable is set then that should get used exclusively as the search path and not just appended to the front. I've had the same thought (and wish it had been implemented that way) but refrained from changing the behavior of this in the past, mainly because it could break some people's builds (some people may treat BOOST_ROOT as a use it if it's there feature or have it accidentally set while building on certain platforms where Boost is provided in the system path). Also, FindBoost would need to check the environment variables BOOST_ROOT and possibly BOOST_LIBRARYDIR and BOOST_INCLUDEDIR as well and if they are set enable this new behavior. Thoughts? I could add a public variable to FindBoost which disables searching the system paths and call it out in the documentation. It would basically set NO_CMAKE_SYSTEM_PATH on all of the find_library() and find_path() calls. Alternatively, we could make the module behave as you describe and hope that it doesn't break too many people. What do you think? -- Philip Lowman ___ 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] FIND_LIBRARY in FindBoost finds wrong library
Someone could add an option to FindBoost that will simply exclude the system paths from the search. This has never been implied by setting BOOST_ROOT. As long as the unversioned library names are being searched for with find_library they are likely going to be found. Currently the onus is on the user to double check what FindBoost discovers. On Mar 19, 2010 4:56 AM, Marcel Loose lo...@astron.nl wrote: Well, in my case, the library name was not even that specific. It found /usr/lib/libboost_date_time-mt.so before /home/loose/boost/boost-1.40.0/lib/libboost_date_time.so, simply because libboost_date_time-mt.so is searched for in *all* paths before libboost_date_time.so. Anyway, I still think this is (also) a CMake issue. IMHO it would make sense to turn the loop in cmFindLibraryCommand::FindNormalLibrary() inside out. What's your opinion? Best regards, Marcel Loose. On Thu, 2010-03-18 at 10:05 -0400, Michael Jackson wrote: I thought there was now an option the b... ___ 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] Skipping PATH when using find_library
On Thu, Mar 11, 2010 at 3:00 AM, mika.raj...@patria.fi wrote:
More reading documentation and attempts... but still not working.
Maybe there is no way?
The following works fine for me on CMake 2.8.0.
message(PATH = $ENV{PATH})
find_library(FOO foo NO_SYSTEM_ENVIRONMENT_PATH)
If you place a foo.lib in your PATH CMake shouldn't find it with that
option. NO_DEFAULT_PATH should work as well although it excludes all
of the default search paths not just the ones specified by the PATH
environment variable.
See:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:find_library
--
Philip Lowman
___
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] set proxy with cmake file download
Have you tried setting the http_proxy environment variable? export http_proxy=http://host:port; On Thu, Mar 11, 2010 at 7:47 AM, nader.akh...@laposte.net nader.akh...@laposte.net wrote: Hi, is it possible to set proxy to use before downloading with cmake? file(DOWNLOAD url file [TIMEOUT timeout] [STATUS status] [LOG log]) Nad Message du 11/03/10 10:28 De : cmake-requ...@cmake.org A : cmake@cmake.org Copie à : Objet : CMake Digest, Vol 71, Issue 49 Send CMake mailing list submissions to cmake@cmake.org To subscribe or unsubscribe via the World Wide Web, visit http://www.cmake.org/mailman/listinfo/cmake or, via email, send a message with subject or body 'help' to cmake-requ...@cmake.org You can reach the person managing the list at cmake-ow...@cmake.org When replying, please edit your Subject line so it is more specific than Re: Contents of CMake digest... [ Today's Topics (7 messages) (0.5 Ko) ] [ Digest Footer (0.1 Ko) ] [ Re: [CMake] adding same subdirectory multiple times. (5.3 Ko) ] [image: Pieddemail] http://www.laposte.net/rallye-des-gazelles ___ 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 -- Philip Lowman ___ 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_BUILD_TYPE should start as a drop-list option
The second line seems like a good idea to me. The user can always modify the property in their code if they have custom build types. The first line seems like a bad idea. I think the default build type should be left to the project. Currently you can set it manually before project(). I think a variable you could set before project() which initialized the cache variable for you isn't a bad idea so long as it says next to it in the docs not available in 2.8. On Mar 1, 2010 9:44 PM, J Decker d3c...@gmail.com wrote: set(CMAKE_BUILD_TYPE Debug CACHE STRING Set build type) set_property(CACHE CMAKE_BUILD_TYPE PROPERTY STRINGS Debug Release MinSizeRel RelWithDebInfo) This could be added to some default startup macro, no? ___ 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] FindCurses wide
If it's not too much trouble, could you please open a ticket for this? http://www.cmake.org/Bug On Sat, Feb 27, 2010 at 10:53 PM, Gary Briggs chu...@icculus.org wrote: I found this thread from a while ago while searching for how to get ncurses to support wide chars: http://www.mail-archive.com/cmake@cmake.org/msg15578.html Please find attached a modified version of FindCurses.cmake that looks for the wide variants of curses if asked. It's working for me... [this is against a 2.6 module. I checked the 2.8 and it looks like some boilerplate has been added, but it's otherwise the same]. Thanks, Gary (-; ___ 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 -- Philip Lowman ___ 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] Missing Software\Microsoft\VisualStudio\8.0\vsmacros\OtherProjects7
I have visual studio 8 sp1 installed and have keys in HKCU/Software/Microsoft/VisualStudio/8.0/vsmacros/OtherProjects7 On Feb 22, 2010 10:32 AM, Wheeler, Frederick W (GE, Research) whee...@ge.com wrote: I did an uninstall/reinstall and have some more info on this problem. From: David Cole Looking at the CMake source code, it does not appear that there is any way to suppress those er... I'm the only person who has used the machine. With the Pro Edition of VS, those keys should definitely be there. Perhaps a full uninstall / re-... I just did a complete uninstall of visual studio and all of the other packages it installs. I then reinstalled Visual Studio 2005 (8.0) Professional. During the install I did get one error message about Microsoft SQL Server 2005 Express Edition x86 failing to install. I doubt that is related to this issue. At this point, I ran Cmake on my project and the errors went away! So that was nice. However, as I had done before, I then also installed VS service pack 1 (VS80sp1-KB926601-X86-ENU.exe). The service pack installed without any error messages or anything unusual at all. After I installed the service pack I ran Cmake on the project again and the missing Software\Microsoft\VisualStudio\8.0\vsmacros\OtherProjects7 errors returned. I did not actually look at the registry entries before or after installing the service pack, but it seems that installing the service pack either A) removed the registry entries in question or B) did something else that causes Cmake to check the registry entries, but failed to create the registry entries. I would assume that most people who use VS 8.0 install service pack 1. It seems to fix a lot of problems. I'd welcome any suggestions on how to fix these errors if they are indeed a sign of a real problem with my system. Or, if anyone thinks this is a Cmake issue, I'm happy to do any tests/checks that might help the cause. As before, Cmake seems to configure the project fine, even with these error messages. Fred Wheeler ___ Powered by www.kitware.comVisit other Kitware open... ___ 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] Overwriting variables in cache.
You can use the CACHE FORCE options to the set() command. This will overwrite the variable every time you configure regardless of what the user enters, however. On Thu, Feb 18, 2010 at 10:40 AM, Benoit Thomas benoit.tho...@gameloft.com wrote: Hi, I am trying to overwrite some variables in the cache (without editing the cache); it works well for variables like CMAKE_CXX_FLAGS, but I cannot overwirte the CMAKE_CONFIGURATION_TYPES variable. Is there a way to do this without having to edit the cache ? (or modifying it the first time the cache is build, that would be correct also). (Sorry if this sound confusing, I just started using cmake) Thank you, Ben. ___ 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 -- Philip Lowman ___ 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/CDash and miscellaneous post-build steps (was Re: continuous integration with CMake)
I've been meaning to add something like that to our nightly builds just using shell/batch scripting. You should be able to set CMAKE_PREFIX_PATH in the initial cache and then just make install or use the vs command line app to run the INSTALL project after calling ctest -S. Not sure on how to detect build failure via ctest directly. For us if the build fails we're not going to care about the contents of the install directory. On Feb 17, 2010 4:58 PM, Tyler Roscoe ty...@cryptio.net wrote: Next question: - CDash and miscellaneous post-build steps Now that I've got Continuous Integration up and running with CDash, I'd like to publish my Continuous builds to a central build archive so developers and testers can use them. I can write post-build rules to copy my _results directory to the build archive (or mess with CMAKE_INSTALL_PREFIX and the INSTALL target), but then the build will be copied as soon as compiling/linking are finished. I would prefer to run the tests first and only copy the build if it passes all the tests. I thought of doing the copy from my continuous integration script itself. I could copy after a successful build by making use of the NUMBER_ERRORS and NUMBER_WARNINGS parameters to ctest_build(). I was hoping I could do the same after ctest_test(), but that command doesn't seem to have anything like NUMBER_ERRORS that would let me evaluate if the tests completed successfully before performing the copy. How do other people handle this? I'd like to do more than just publish the builds (run the setup.exe and make sure it works, compare what is installed by setup.exe against a known-good install manifest, kick off component tests on another machine with this newly-generated build, etc.) but figuring out a method for publishing builds would be a great start. Thanks, tyler On Fri, Dec 04, 2009 at 01:07:23PM -0500, Bill Hoffman wrote: Tyler Roscoe wrote: The build scripts for CMake can be found on CDash itself, for example: http://www.cdash.org/CDash/viewNotes.php?buildid=485762 For each dashboard on the CMake dashboard if you click on the notes for the build you can see the script that was used to drive the build. Here is the .bat file that is run for a scheduled task on that machine: $ cat dash2win64.bat setlocal rem Update clapack driver script from clapck pushd c:\Dashboards\clapack svn up clapack_build.cmake rem Run the clapack driver script c:\Program Files (x86)\CMake 2.8\bin\ctest.exe -C Release -S clapack_build.cmake -VV -O clapack.log popd endlocal call C:\cygwin\bin\bash.exe --login c:/Dashboards/DashboardScripts/dash2win64cygwin.sh c:\Program Files (x86)\CMake 2.8\bin\ctest.exe -C Release -S dash2Win64_cmake_vs10.cmake -O cmake_vs10.log c:\Program Files (x86)\CMake 2.8\bin\ctest.exe -C Release -S dash2Win64_cmake_vs10_x64.cmake -O cmake_vs10_x64.log setlocal call C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat c:\Program Files (x86)\CMake 2.8\bin\ctest.exe -C Release -S dash2Win64_cmake_nmake10.cmake -O cmake_nmake10.log endlocal setlocal call C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64\vcvars64.bat c:\Program Files (x86)\CMake 2.8\bin\ctest.exe -C Release -S dash2Win64_cmake_nmake10_x64.cmake -O cmake_nmake10_x64.log endlocal c:\Program Files (x86)\CMake 2.8\bin\ctest.exe -C Release -S dash2win64_libarchive_vs9.cmake -VV libarchive_vs9.log 21 c:\Program Files (x86)\CMake 2.9\bin\ctest.exe -C Release -S dash2win64_cmake_icl11_32.cmake -VV cmake_icl11_32.log 21 c:\Program Files (x86)\CMake 2.9\bin\ctest.exe -C Release -S dash2win64_cmake_icl11_64.cmake -VV cmake_icl11_64.log 21 ___ 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] FindBoost: trunk
Not that I know of. I think FindBoost expects only versioned releases. Please open a ticket with your requirements and preferably a patch. Http://public.kitware.com/Bug On Feb 14, 2010 5:34 PM, Hicham Mouline hic...@mouline.org wrote: Hello, Is there a way to find the boost trunk include directories and lib directories? Regards, ___ 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 avoid continuous download while using ExternalProjects
On Thu, Feb 11, 2010 at 12:00 PM, Luigi Calori l.cal...@cineca.it wrote: Also, for any that are interested, beta releases of zlib now have a CMakeLists.txt in them. It could use testing on Mac OSX and other unix systems. http://zlib.net/current/beta/ Did you tried that? I' did but seem to have a strange error on linking their examples: I got zlib.lib(gzlib.obj) : error LNK2019: unresolved external symbol _snprintf referenced in function _gzdopen that seem to get away by adding # define snprintf _snprintf to gzguts.h Anyone has ever tested it under MSVC? It would be nice to have helpers to build patches, as in CMakePorts... I was testing it on MSVC but it seems like they keep checking in code which breaks MSVC every 1.2.3.X and I haven't been checking X consistently. Your above comment is an example. If only they had a dashboard... sigh. -- Philip Lowman ___ 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] Bison extra headers
They could be if you want. Just open up a bug ticket with some info
on how to reproduce and your bison command line and I'll see what I
can do. I'm pretty sure all we would have to do is add position.hh,
location.hh and stack.hh as OUTPUTs for the custom command for them to
be automatically cleaned. All that would need to be known is how they
get generated (special flag to parse?).
On Thu, Feb 11, 2010 at 1:01 PM, Hilton Medeiros
medeiros.hil...@gmail.com wrote:
FYI, I won't put these in the issues tracker because I really don't
think these should be solved by the FindBISON module.
On Thu, 11 Feb 2010 10:57:44 -0200
Hilton Medeiros medeiros.hil...@gmail.com wrote:
Hello,
I'm using bison_target() from FindBISON with the C++ bison interface,
on CMake 2.8.0. When using this interface the following extra files
are generated by bison:
location.hh
position.hh
stack.hh
They do not get listed in BISON_target_OUTPUTS and do not get erased
in 'make clean'.
See here:
http://www.gnu.org/software/bison/manual/html_node/C_002b_002b-Bison-Interface.html
Note that this manual seems outdated, there is no 'lalr1.c' for me,
only 'lalr1.cc' on bison 2.4.1. Anyway, this is a very small issue,
this is the workaround I'm using:
set (BISON_EXTRA_HEADERS
${PROJECT_BINARY_DIR}/position.hh
${PROJECT_BINARY_DIR}/location.hh
${PROJECT_BINARY_DIR}/stack.hh
)
set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES
${BISON_EXTRA_HEADERS})
By the way, I saw that the main header file generated on
bison_target() is always terminated by '.hpp'. I tried to bypass this
with:
bison_target (PARSER ${PARSER_FILE} ${PROJECT_BINARY_DIR}/Parser.cpp
COMPILE_FLAGS
--defines=${PROJECT_BINARY_DIR}/Parser.h)
But then both Parser.hpp and Parser.h are generated. But this is also
a very small issue.
Finally, thanks a lot for supporting bison and flex in CMake.
Kind regards,
visibility guy
___
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
--
Philip Lowman
___
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 findXXX libraries with debug suffix
On Wed, Feb 10, 2010 at 10:49 AM, Will Dicharry
wdicha...@stellarscience.com wrote:
My only other comment is that some modules already use the following
form (usually due to someone adding DEBUG support later)
FOO_LIBRARY (cache variable)
FOO_LIBRARY_DEBUG (cache variable)
FOO_LIBRARIES (normal variable with debug/optimized keywords when
FOO_LIBRARY_DEBUG is available, else normal variable set to
FOO_LIBRARY)
It would be nice to see a second macro that supports this format.
I guess I'll have to think about that for a bit. But really, if other
modules are going to need to modify code to use the macro, shouldn't they
move to the more modern and descriptive form while they're at it? I know
they probably have to maintain backwards compatibility, but they can do that
by using the macro and setting FOO_LIBRARY to FOO_LIBRARY_RELEASE after the
macro is called.
So if I understand correctly the code would do this?
find_library(FOO_LIBRARY ...)
find_library(FOO_LIBRARY_DEBUG ...)
set(FOO_LIBRARY_RELEASE ${FOO_LIBRARY})
call_the_macro()
# macro creates FOO_LIBRARIES debug/optimized keywords
# macro also sets FOO_LIBRARY with debug/optimized keywords *
I guess that probably would be safe and maintain backwards
compatibility with the module with the exception possibly of setting
FOO_LIBRARY to have the debug/optimized keywords (see below).
I'm not sure I understand the situation you're describing here. Are you
referring to the older backwards compatibility case, or something about the
usual FOO_LIBRARY_DEBUG and FOO_LIBRARY_RELEASE case?
Sorry I wasn't very clear. This covers the older backwards
compatibility case. What I mean to say is that if the user was
relying on FOO_LIBRARY within existing target_link_libraries() calls
like below, they will get the warning below if FOO_LIBRARY is
redefined to contain debug/optimized keywords.
target_link_libraries(bar optimized ${FOO_LIBRARY})
# now FOO_LIBRARY contains
# optimized foo.so debug food.so
CMake Warning (dev) at CMakeLists.txt:8 (target_link_libraries):
Link library type specifier optimized is followed by specifier
optimized instead of a library name. The first specifier will be
ignored.
Removing the setting of FOO_LIBRARY to contain debug/optimized
keywords from your macro could break people. Leaving it in if
FOO_LIBRARY is used in the manor I illustrated causes warnings. You
might want to check with if(DEFINED FOO_LIBRARY) and if so not set it
maybe?
--
Philip Lowman
___
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 avoid continuous download while using ExternalProjects
On Wed, Feb 10, 2010 at 11:37 AM, David Cole david.c...@kitware.com wrote: If anybody has other ideas to share downloads between Release and Debug configurations, or other ways to avoid unnecessary downloads better, or other ideas for any ExternalProject improvement, I'm all ears. :-) Caching for source tarballs would be a nice feature so that when you clean the project you don't have to redownload them. I pulled this off with stamp files in CMakePorts I think with some suggestions from you. The problem of course is if you really want to remove the downloads you need yet another target. Also, for any that are interested, beta releases of zlib now have a CMakeLists.txt in them. It could use testing on Mac OSX and other unix systems. http://zlib.net/current/beta/ -- Philip Lowman ___ 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 findXXX libraries with debug suffix
On Tue, Feb 9, 2010 at 11:15 AM, Will Dicharry
wdicha...@stellarscience.com wrote:
Mike Jackson wrote:
Here is one I wrote for Expat:
--8
# - Find expat
# Find the native EXPAT headers and libraries.
#
# EXPAT_INCLUDE_DIRS - where to find expat.h, etc.
# EXPAT_LIBRARIES - List of libraries when using expat.
# EXPAT_LIBRARY_DEBUG - Debug version of Library
# EXPAT_LIBRARY_RELEASE - Release Version of Library
# EXPAT_FOUND - True if expat found.
The macro below has been generalized and placed in the standard set of CMake
modules with the 2.8 release. I saw it duplicated in enough places that I
added it for general use in the Modules directory. It's called
SelectLibraryConfigurations, you can get information about it by typing
cmake --help-module SelectLibraryConfigurations. You don't have to use the
standard one, but it's there if you need it. Let me know if you run into any
trouble with it.
Thank you for adding this and mentioning it! There are probably lots
of modules out there that need to be modified to take advantage of
this.
One minor thing I don't like about the module is this line (70) right here:
set( ${basename}_LIBRARY ${${basename}_LIBRARY} CACHE FILEPATH The
${basename} library)
Presumably users of this module have already called
find_library(${basename}_LIBRARY_RELEASE) and
find_library(${basename}_LIBRARY_DEBUG) since it's expecting these
names. Why then add a 3rd cache variable? If the user were to change
${basename}_LIBRARY_DEBUG after an initial configure, the cache
variable will not get fixed since set() does not operate on cache
variables that have already been initialized unless FORCE is used.
This isn't a major issue since you define a ${basename}_LIBRARY normal
variable which overrides the cache variable immediately above it. At
best, line 70 where you declare the CACHE variable is superfluous. It
could also be a little confusing to some users who change it in the
CACHE and see no effect.
===
My only other comment is that some modules already use the following
form (usually due to someone adding DEBUG support later)
FOO_LIBRARY (cache variable)
FOO_LIBRARY_DEBUG (cache variable)
FOO_LIBRARIES (normal variable with debug/optimized keywords when
FOO_LIBRARY_DEBUG is available, else normal variable set to
FOO_LIBRARY)
It would be nice to see a second macro that supports this format.
Also, the redefinition of FOO_LIBRARY to have optimized release
keywords in it may or may not be desired. The only harm I can see
this causing is if a user were to have done this already in his
CMakeLists.txt. In this case they might find themselves with a CMake
error or linking against liboptimized.so! :)
if(FOO_LIBRARY_DEBUG)
target_link_libraries(bar optimized ${FOO_LIBRARY} debug
${FOO_LIBRARY_DEBUG})
else()
target_link_libraries(bar ${FOO_LIBRARY})
endif()
--
Philip Lowman
___
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] set “Whole Program Optimization”to Y es in VS 2005
On Tue, Feb 9, 2010 at 9:51 PM, xiad...@sina.com wrote:
When I use the blow statement for MSVC:
SET (CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_RELEASE} /GL)
The corresponding statement in the .vcproj file generated by CMake is:
AdditionalOptions= /Zm1000 /GL
When I open the property pages in VS 2005，I can see /GL on the page on
command line, but the item of“Whole Program Optimization”on the page of
Optimization is still No.
Why does not CMake generate WholeProgramOptimization=1 in the .vcproj
file?
Not sure, probably an omission. /GL appears to be supported in
cmVS10CLFlagTable.h but not cmLocalVisualStudio7Generator.
Here's a patch
http://public.kitware.com/Bug/view.php?id=10263
P.S.
If it's not clear, CMake not supporting the WholeProgramOptimization
XML tag only affects what the Visual Studio GUI looks like and doesn't
affect the compiling of the code since the /GL shows up in the
additional options line and thus gets added to the command line when
the compiler is run.
--
Philip Lowman
___
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] Manual version vs CMake version
On Fri, Feb 5, 2010 at 4:31 PM, Mateusz Loskot mate...@loskot.net wrote: Bill Hoffman wrote: Eric Noulard wrote: That's true, may be the site could indicate that the doc is for latest 2.6.x serie. However the most trustfull way to check the doc of your current cmake version is the command line. cmake --help-command if should give you the doc for the cmake version you are using. if you want html you can use: cmake --help-html cmake-doc.html then browse the cmake-doc.html file. Or cmake --version. Yes, all this is true and I've managed to find a solution myself quite easily, but I've posted as from position of an average (read, rather lazy) user who preferes pretty website to read doc than dark console :-) Also, it might not be a bad idea to mention the version number within the documentation when features are added, especially if features are going to be added during a patch release. The same should probably be true of new find modules. -- Philip Lowman ___ 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] Warning D9025 : overriding '/W3' with '/W4'
On Mon, Jan 18, 2010 at 7:17 PM, Mateusz Loskot mate...@loskot.net wrote:
Hi,
In CMakeLists.txt I have something like this:
if(MSVC)
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} /W4)
endif()
I configure my build using command prompt of Visual Studio 2005 (8.0):
D:\dev\geos\_svn\build-nmakecmake -G NMake Makefiles ..\trunk
and the compiler flags look as follows:
CMAKE_CXX_FLAGS= /DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR /W4 /MP
I build and I'm getting D9025 warning:
D:\dev\geos\_svn\build-nmake nmake
Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
Copyright (C) Microsoft Corporation. All rights reserved.
[ 0%] Building CXX object src/CMakeFiles/geos.dir/algorithm/Angle.cpp.obj
cl : Command line warning D9025 : overriding '/W3' with '/W4'
Would it be possible to get rid of this warning with some CMake magic?
Yes, you can use a regular expression to search and replace the
contents of CMAKE_CXX_FLAGS /W3 (or /W[0-9]) with /W4... see
string(REGEX REPLACE...) in the docs.
Alternatively (and slightly better), you can create separate files
that will set the default MSVC compilation flags for you. You'd do
something like in the example below, but instead of
CMAKE_CXX_FLAGS_DEBUG, CMAKE_CXX_FLAGS_RELEASE, etc., you would only
need to specify CMAKE_C_FLAGS and CMAKE_CXX_FLAGS and make them
whatever they are in the CACHE by default but with /W4 instead of /W3.
http://www.itk.org/Wiki/CMake_FAQ#Make_Override_Files
--
Philip Lowman
___
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] FindGTest patch
On Sat, Jan 16, 2010 at 10:16 AM, Stephan Menzel stephan.men...@gmail.com wrote: please correct me if I'm wrong but in my impression the existing FindGTest module is rather ignorant about finding 64 bit builds on windows. It also doesn't handle Debug/Release linking very well. Also it appears not to be quite consistent with it's API description. Please find a patch attached that solves at least some of those problems for your consideration. Thanks for adding the 64-bit support. I will merge it in soon but before I do I just wanted to confirm that the path for the 64-bit libraries is msvc/x64/Debug msvc/x64/Release regardless of if the MD or MT project files are chosen? Also, not sure exactly what you mean by not handling debug/release linking very well. Where did you find that version of FindGTest and what was wrong with it? It looks different from the one that was released with CMake 2.8.0. Also, The latest version in CMake CVS (with some minor changes from 2.8.0) is here: http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindGTest.cmake?revision=1.4root=CMakeview=markup -- Philip Lowman ___ 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] Proposal for new generator options
On Fri, Jan 15, 2010 at 3:20 PM, Jochen Wilhelmy j.wilhe...@arcor.de wrote: Hi! This proposal addresses the following issue: currently there is no solution for creating Visual Studio project files for static runtime without editing the cmake files. As the goal of cmake is to define a project in an abstract way it should be possible to generate for static runtime only via the command line interface since someone who never uses Visual Studio will probably not account for this issue. A solution could look like this: split the -G option into three options, e.g. -G the generator -V the Version - T the Target platfrom some examples: old: -G Visual Studio 8 2005 Win64 new: -G Visual Studio -V 8 -T Win64 or equivalent -G Visual Studio -V 2005 -T Win64 old: -G Eclipse CDT4 - Unix Makefiles new: -G Eclipse CDT -V4 -T Unix Makefiles in this new system the static runtime is a target: -G Visual Studio -V 8 -T Win32 static of course the old generator names can continue to exist for backward compatibility. There are at least 3 ways to solve this problem without introducing any changes to CMake. See the CMake FAQ. http://www.itk.org/Wiki/CMake_FAQ#How_can_I_build_my_MSVC_application_with_a_static_runtime.3F If there is enough demand to add a feature to do this without requiring CMakeLists.txt modifications, at least do something simpler such as adding a variable like CMAKE_MSVC_COMPILE_WITH_MT or something like that. This way all that needs to be modified is Modules/Platform/Windows-cl.cmake to set the initial cache differently and perhaps adding a checkbox to the GUI when selecting the initial generator. -- Philip Lowman ___ 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] Visual Studio with static runtime
On Fri, Jan 15, 2010 at 1:21 PM, Dave Partyka dave.part...@kitware.com wrote: I think you just change the appropriate flag in CMAKE_CXX_FLAGS_Config_Type variable to control this. By Default It uses the Dll runtime via the MD/MDd flags. See this table for the other variations of this flag. http://msdn.microsoft.com/en-us/library/abx4dbyh(VS.71).aspx For tips on how to change your CMakeLists.txt, see also: http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_build_my_MSVC_application_with_a_static_runtime.3F -- Philip Lowman ___ 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] ANN: UseOcaml.cmake
On Thu, Jan 14, 2010 at 5:11 AM, Keyan m...@pulsschlag.net wrote: hi, ups ... i thought i replied to the list. thanks for the link. i will adapt my find-script to the requirements and maintain the package. You should work with Judicaël to combine the best of both of your works together into one FindOCaml and UseOCaml script. There is no sense having two of them out there. -- Philip Lowman ___ 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] ANN: UseOcaml.cmake
On Mon, Jan 11, 2010 at 3:39 AM, Keyan m...@pulsschlag.net wrote:
It looks like a couple of the macros don't have the OCAML_ name prefix
added to them. For example, COPY_FILE GET_DEPENDENCIES. You should
add the prefix to them as well to prevent name collision when other
people use your code.
thanks. wasnt aware of this coding standard, but it makes sense :)
For the INCLUDES feature, doesn't it just get turned into a list you
can iterate on? Couldn't you just use foreach() on it and add the
-I argument and path argument to a separate list that gets passed to
add_custom_command()?
foreach(path ${includelist})
list(APPEND myargs -I)
list(APPEND myargs ${path})
endforeach()
nice, it worked. my mistake was that i used:
set(myargs {$myargs} -I ${path})
instead.
i will try to write a FindOcaml.cmake script soon. when i am done, what is
the best practice to make it available?
Sorry, your email got accidently buried for 3 days. :) Also please
reply to all always so the list gets a copy of the thread.
I think the best way to get it available it to have it released as
part of CMake's Modules folder. To do this you have to volunteer to
maintain the module (basically to deal with patches and bugs) and
follow the process documented in Modules/README.txt to obtain CVS
commit access.
http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/readme.txt?root=CMakeview=markup
--
Philip Lowman
___
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] Can you add sources to a target library after add_library()?
I highly doubt it. Best practice is to just use conditionals to add the necessary source files to a list variable prior to the add_library() call. On Sat, Jan 9, 2010 at 5:48 PM, Marcel Loose lo...@astron.nl wrote: Hi all, I've been searching the manuals, but couldn't find a way to add sources to a target library *after* the add_library() command, e.g., using set_target_properties()? Is this possible at all? Best regards, Marcel Loose. ___ 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 -- Philip Lowman ___ 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] xxxxxSPAMxxxxx Simple Question Regarding Link Libraries on Linux
Whoever developed foo.a should call it libfoo.a instead so it meets
standards. All libraries on Linux are supposed to start with lib
with the possible exception of dynamically loaded shared libraries
(i.e. plugins).
If you still can't rename it, you can do target_link_libraries(bar
/full/path/to/foo.a).
To get the full path of your source tree you can use
${CMAKE_CURRENT_SOURCE_DIR}.
On Tue, Jan 5, 2010 at 5:57 PM, ed.j...@agileplanet.com wrote:
How do I link a *.a file that doesn't start with lib to an executable?
For example, if I have a library named foo.a with a function called getnum,
how do I link to foo.a in CMakeLists.txt?
If my executable file is
---main.cpp---
extern int getnum();
int main(int, char**) { cout getnum() endl;}
and my CMakeFile is
---CMakeLists.txt---
PROJECT(TESTPROJECT)
ADD_EXECUTABLE(test main.cpp foo.a)
---
I'll get an error about an undefined reference to getnum when I run the
makefile.
If I use TARGET_LINK_LIBRARIES(test foo), I'll get an error about not begin
able to find the library, since it's using the -l flag for the linker. I'd
rather not have to rename foo.a, because it will affect other existing
software.
Thanks,
-Ed
___
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
--
Philip Lowman
___
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 Module] FindGTK2.cmake call for testing
On Mon, Jan 4, 2010 at 10:48 AM, Michael Wild them...@gmail.com wrote: On 8. Jan, 2009, at 9:54 , Philip Lowman wrote: If you use GTK2 in any of your projects and have time, please test this CMake module and post any issues to this thread. I intend to check it into CMake and support it. Tested systems: Ubuntu 8.10 Windows/MSVC (official gtkmm installer) A year late to the party, but here my problems (using cmake-2.8-0): 1. FindGTK2.cmake doesn't find the GLib-2/GTK+-2 headers installed by fink on Mac OS X. Adding /sw/include and /sw/lib to the PATHS list of the find_path call solves this for me. 2. The second thing is, that on Mac you also need to explicitly link agains gobject, so adding the call _GTK2_FIND_LIBRARY (GTK2_GOBJECT_LIBRARY gobject false true) just after the one for glib solves that problem for me. Thanks for the email, I've checked in fixes for both of your issues into CMake CVS. Could you try the FindGTK2.cmake module there (see link below) and report back? http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindGTK2.cmake?root=CMakeview=log Here's the newly created bug report if the changes don't work. http://public.kitware.com/Bug/view.php?id=10092 -- Philip Lowman ___ 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 query
You're missing the mingw32-make program. If you used the installer there is a checkbox for it. Alternatively you can download and unzip it from here: http://sourceforge.net/projects/mingw/files/MinGW%20make/ 2010/1/3 sdfsdfs sdfsdfsd dhmoub...@hotmail.com: Hello, Im ttrying to install a program in windows using cmake gui. I get the folloeing errors when im trying to configure it: The C compiler identification is GNU The CXX compiler identification is GNU Check for working C compiler: C:/MinGW/bin/gcc.exe CMake Error: Generator: execution of make failed. Make command was: make cmTryCompileExec\fast Check for working C compiler: C:/MinGW/bin/gcc.exe -- broken CMake Error at ../../cmake-2.8.0-win32-x86/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:50 (MESSAGE): The C compiler C:/MinGW/bin/gcc.exe is not able to compile a simple test program. It fails with the following output: Change Dir: L:/.rsrc/CMakeFiles/CMakeTmp Run Build Command:make cmTryCompileExec\fast The system cannot find the file specified Generator: execution of make failed. Make command was: make cmTryCompileExec\fast CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:3 (project) Configuring incomplete, errors occurred! Anyone got any ideas what is going wrong and how to fix the problem? Windows Live: Keep your friends up to date with what you do online. ___ 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 -- Philip Lowman ___ 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] target_link_libraries: prefer static to dynamic
On Sun, Jan 3, 2010 at 2:26 PM, Alexander Neundorf a.neundorf-w...@gmx.net wrote: Isn't there some binutil which can tell what kind of library some .lib is ? Or maybe every dll (and that way the accompanying lib) has some functions which only dlls have ? Or maybe they references some special functions which maybe could be checked with something like nm ? If I recall correctly we discussed this a long time ago and there were some dll specific symbols present in the accompanying import library that weren't there in the static library. -- Philip Lowman ___ 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] EXECUTE_PROCESS and relative path
On Sun, Dec 20, 2009 at 10:53 AM, Steve Chu stv...@gmail.com wrote:
Does EXECUTE_PROCESS support relative path to CMakeLists.txt file?
Suppose we have this demo:
EXECUTE_PROCESS(
COMMAND /bin/cat ./xxx
# WORKING_DIRECTORY /some/absolute/path
)
If we do not set WORKING_DIRECTORY to absolute path, this command does not
work.
But I do not want to introduce a fixed absolute path(or ENV) that is
up to who builds the project.
So does cmake have a feature of relative path? Such as:
EXECUTE_PROCESS(
COMMAND /bin/cat RELATIVE{./xxx}
)
here RELATIVE means relative to CMakeLists.txt file.
You can use ${CMAKE_CURRENT_SOURCE_DIR} and the path relative to that.
http://www.cmake.org/Wiki/CMake_Useful_Variables
--
Philip Lowman
___
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.0, FindGTK2 on mac
Hi, I wrote FindGTK2. You might try removing the gtk/ from line 350? Line 345 where the include path is searched for may also need to be modified... I don't have a MAC so if anyone has any better ideas, help would be appreciated. On Dec 1, 2009 1:27 PM, Aleksander Demko ade...@gmail.com wrote: I can't seem to get FindGTK2 working under a Mac. I've installed the latest shipping library for mac from gtk.org, and even with a CMakeLists.txt file that has nothing but FIND_PACKAGE(GTK2), I get the following errors: CMake Error at /Applications/CMake 2.8-0.app/Contents/share/cmake-2.8/Modules/FindGTK2.cmake:93 (file): file Internal CMake error when trying to open file: /Library/Frameworks/Gtk.framework/Headers/gtk/gtk/gtkversion.h for reading. Call Stack (most recent call first): /Applications/CMake 2.8-0.app/Contents/share/cmake-2.8/Modules/FindGTK2.cmake:467 (_GTK2_GET_VERSION) CMakeLists.txt:2 (FIND_PACKAGE) -- Some or all of the gtk libraries were not found. (missing: GTK2_GTK_LIBRARY GTK2_GLIB_LIBRARY GTK2_GDK_LIBRARY) There seems to be one extra gtk/ in the above path. I'm new to mac development, but it seems there are some interesting path manipulations that are done when searching for header files in framework directories. I'm just not sure how to go about fixing this. Any ideas would be super. Thanks! ___ 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
