[cmake-developers] [CMake 0015362]: Target property INTERFACE_SYSTEM_INCLUDE_DIRECTORIES doesn't seem to work

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15362 == Reported By:Clinton Stimpson Assigned To:

Re: [CMake] Library include path question

How about something like (in the top-level directory for the projectlib sources): add_library(projectlib STATIC projectlib/foo.h projectlib/foo.cpp ...) target_include_directories(projectlib PUBLIC . PRIVATE projectlib) (Note that this will add the top-level directory as well as the projectlib

Re: [CMake] Library include path question

We use similar layout in a set of components, but in order to do that we just store library interface headers in lib-name/include/lib-name directory. And layout of library directory is the following: src/ - internal headers and implementation include/ - external headers CMakeLists.txt Then you

[CMake] Library include path question

A common and useful method for avoiding name conflicts and keeping files well-organized is to place them in a subdirectory unique to the library. For example, the libraries for Graphviz and Postgres often install their API header files in directories named install-prefix/include/graphviz and

[Cmake-commits] CMake branch, master, updated. v3.1.0-908-g70eb44b

20150119) +set(CMake_VERSION_PATCH 20150120) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake

Re: [CMake] detecting __attribute__((weak)) support

Pending (possible) built-in support in cmake, looks like I could use check_cxx_source_compiles( extern \C\ void cmkcheckweak() __attribute__((weak)); int main(int argc, char** argv) { return cmkcheckweak == nullptr; // works with (void*)0; } HAVE_WEAK_SYMBOLS) But that doesn't work because

[cmake-developers] [CMake 0015361]: CHECK_CXX_SOURCE_COMPILES doesn't use c++11 flags specified

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15361 == Reported By:Laurent Demailly Assigned To:

[cmake-developers] CPack RPM failing tests on dashboard

I've noticed CPack/RPM test fails on dashboard for two Fedora-19-x86_64 machines: https://open.cdash.org/buildSummary.php?buildid=3658687 https://open.cdash.org/buildSummary.php?buildid=3658677 Would it be possible to get generated rpm files from one of them for analysis?

Re: [CMake] CPack in CMake 3.1.0 doesn't install files

No one? Has something changed between 3.0.2 to 3.1.0 which prevents cpack to copy the generated *.exe file to the _CPack_Packages directory? Or did i need an additional variable to be set in 3.1.0? Thanks in advance Best Regards Am 16.01.2015 um 12:09 schrieb NoRulez noru...@me.com: If

[cmake-developers] [CMake 0015360]: XCode generated project yield Project 'X' overrides the Architectures setting warning

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15360 == Reported By:Laurent Demailly Assigned To:

[CMake] Xcode strip linked product

Hi all, Using CMake 3.0.1, when generating for Xcode, the setting Strip linked product is set to Yes for ALL targets (Debug/Release…), which of course disables any possibility to debug. How can I make CMake set this to NO for Debug ? TIA /Rob -- Powered by www.kitware.com Please keep

[Cmake-commits] CMake branch, next, updated. v3.1.0-2133-ged79818

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-2135-ga63d44a

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

Re: [CMake] Xcode strip linked product

Ok, my bad, I found the place where it is set, via: SET_TARGET_PROPERTIES(mytarget PROPERTIES XCODE_ATTRIBUTE_STRIP_INSTALLED_PRODUCT “YES”) However, I’d need to set it per, so something like SET_TARGET_PROPERTIES(mytarget PROPERTIES XCODE_ATTRIBUTE_STRIP_INSTALLED_PRODUCT_DEBUG NO”) It

[Cmake-commits] CMake branch, next, updated. v3.1.0-2148-g50c85f8

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 50c85f8df978c864170024492e19ec68b73e631b (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2172-g85f6c64

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 85f6c64358e1a1077d01b77b93c09d8d964375c9 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2150-gd703c9b

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-2152-g721cf69

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 721cf69c03495cbea80442561b354bfe5eca70b4 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2154-gd695130

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-2156-g5b5e673

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-2167-g4703cca

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 4703cca3e907970b2de37a75c7eac023cf40d61e (commit) via

Re: [cmake-developers] [PATCH] cmake-mode.el: Fix extracting keyword at point in cmake-help

On 01/17/2015 07:27 PM, ptrv wrote: With commit 30f14aebeee90bc1af6236888599db86b2bd8fae 'word-at-point' function does not extract the whole keyword anymore if it contains an '_', because 'forward-word' stops at '_'. Use 'symbol-at-point' to extract whole keyword even if there is an '_'.

[Cmake-commits] CMake branch, master, updated. v3.1.0-858-ga1fea84

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via a1fea841a92568c0bdc35e1c8c7a400b20459a96 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-867-ga6bbbd0

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via a6bbbd0f4a9ca9d683000f3302842bc25615e57a (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-888-g2e71d92

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 2e71d92ef270c4234368fd2e88259c0defbfb650 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2169-g9a96401

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 9a96401774c4afc6bc12cde06cf6d6306b2f5b22 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2137-gf1dfe06

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-878-g9de2ab7

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 9de2ab7fcefba2bc9ce7b483f1643b1d97d58e43 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-861-g95d4284

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 95d42840e88599ab1959f7531668e320a7c20fdf (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-848-g5803ae3

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 5803ae3e88e922c06ce835eb7bdcb5c584420453 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-850-ge320640

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via e320640bcf2323e54add8a7c920b406c4a652816 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-856-ga5be8e3

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via a5be8e3111ff0b6c656facd603c2e2d972d61671 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-852-g953272b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 953272b725ba98358f262588d89c75bdd3429367 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-846-g373199b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 373199b1c922c6897e007fc1c8fa684aa1a8f707 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-886-gfc9204e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via fc9204efcb7cd77562cf8cc76baa58df9841649f (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2165-g829bf43

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 829bf431cd87375ae774d550a7a1d784b65a24ed (commit) via

[Cmake-commits] CMake branch, release, updated. v3.1.0-74-gbc9cd21

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, release has been updated via bc9cd21bd46023f3f0f7be5be5386315a193af08 (commit) via

Re: [cmake-developers] CPack RPM failing tests on dashboard

May be you can make RunCPackVerifyResult.cmake more verbose when a failure occurs? (i.e. a bunch of extra rpm query on the culprit generated RPM) and/or more informations in the error message. You're right. Haven't thought about such cases when I don't have the output RPM files. I'll extend

[Cmake-commits] CMake branch, next, updated. v3.1.0-2182-g6351880

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 6351880c2aa815f389e0154ab41b7138a5cbf6b4 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2174-gd4c1925

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

[CMake] Specify 32-bit compilation to Clang

I'm running CMake 3.1 on Mint 64-bit OS. I need to generate an Eclipse project using Ninja that uses Clang to build a 32-bit application. When I do this: add_definitions(-m32) For some reason my code is not able to include STL headers (files not found). Any reason for this? Is there a more

Re: [CMake] VS2012 builds using v3.1.0 are a lot slower than v2.8.12

On 01/17/2015 12:20 PM, Yves Frederix wrote: I also tested with the build of an 'open' project (the crypto example was part of a work-related project). The results below are for the compilation of OpenCV (latest git from https://github.com/itseez/opencv), again with VS2012 Win64, Release only

[Cmake-commits] CMake branch, next, updated. v3.1.0-2202-g4426234

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 44262347099d0de4dd421a15e647a7fdb33f83ab (commit) via

Re: [cmake-developers] [PATCH] Setting default user, group and permissions for CPackRPM

On 01/16/2015 03:10 AM, Domen Vrankar wrote: That is why uid and gid in install command don't help much - if CPack/RPM would use uid and gid from install command it would be limited to users and groups listed in systems /etc/passwd file. I could write an initial patch for bug report 3602

Re: [CMake] Specify 32-bit compilation to Clang

Hello Robert, On 19/01/15 20:42, Robert Dailey wrote: I'm running CMake 3.1 on Mint 64-bit OS. I need to generate an Eclipse project using Ninja that uses Clang to build a 32-bit application. When I do this: add_definitions(-m32) For some reason my code is not able to include STL

Re: [cmake-developers] Introduce 'Unix Ninja' generator

On 01/16/2015 01:13 PM, Daniel Levin wrote: The CMake and Ninja were part of the bigger build script, which was running under the QNX SDK sh.exe. When running under this shell it overrides some environment variables (compare attached files). The main differences I see are: * The Windows

[Cmake-commits] CMake branch, next, updated. v3.1.0-2189-gecfb1d6

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

[CMake] FindGDAL.cmake

Dear all, There is a problem with the FindGDAL.cmake module. It will use the gdal-config binary to find the library name (lib) path, but not for the include path. Attached is a patch that will use gdal-config --cflags to find the correct location for the gdal.h file. I just moved the find_path

[Cmake-commits] CMake branch, next, updated. v3.1.0-2204-g9b7ab08

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 9b7ab08044e7d024e225efb44835153f53c6c1dd (commit) via

[cmake-developers] [PATCH] cmake-mode.el: Re-add explicit call to require thingatpt

Usually it is not needed to call '(require 'thingatpt')' explicitly because the function 'symbol-at-point' is in autoloaded but to be sure to have the function loaded in every case, require thingatpt. --- Auxiliary/cmake-mode.el | 1 + 1 file changed, 1 insertion(+) diff --git

[Cmake-commits] CMake branch, next, updated. v3.1.0-2191-g700ed02

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 700ed02cc88ff28d80330cea7543a7220c5f7409 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2193-g108f1c4

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 108f1c46e6ed1e0046dd6176e8a11a3ce582bbf8 (commit) via

Re: [cmake-developers] [PATCH] cmake-mode.el: Re-add explicit call to require thingatpt

On 01/19/2015 01:49 PM, Peter Vasil wrote: Usually it is not needed to call '(require 'thingatpt')' explicitly because the function 'symbol-at-point' is in autoloaded but to be sure to have the function loaded in every case, require thingatpt. Okay, thanks: cmake-mode.el: Re-add explicit

[Cmake-commits] CMake branch, master, updated. v3.1.0-907-g813ace9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 813ace90e4d02a782176ea13bcec15a3e9338210 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2197-g26883b2

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 26883b20debd5facab0eb9a2baa08b98a4df1eb0 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-893-g0898de9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 0898de99cc085fee8534369aea27e9333b53d694 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.1.0-899-g137a15b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 137a15bf1da72c795d8eeded4ad3848a5692dce6 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.1.0-2200-g41a41e6

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 41a41e60fdc05c31ce5fafb5b2242fabc207c4db (commit) via

[CMake] Using C++11 features and Cmake 3.1

This is a bit long but it should help those using C++11 features in CMake 3.1. This is an extract from my CMakeLists.txt file that uses C++11 in a cross-platform manner. It also lists the available C++11 features and shows you how to set up defines that can be used in your code. The ancillary

[Cmake-commits] CMake branch, next, updated. v3.1.0-2217-g7634fd7

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 7634fd7e72e85b5573fc33059fffaaa03da8fd37 (commit) via

[CMake] detecting __attribute__((weak)) support

I searched and didn't find yet ­ would it be reasonable to have built in support in cmake for knowing if the platform/compiler supports weak symbols ? I'm porting the following autconf fragment: AC_CACHE_CHECK( [for weak symbol support], [folly_cv_prog_cc_weak_symbols], [AC_LINK_IFELSE(

[Cmake-commits] CMake branch, next, updated. v3.1.0-2219-gda8512d

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

[cmake-developers] [CMake 0015359]: __attribute__((weak)) support/detection (weak symbols)

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15359 == Reported By:Laurent Demailly Assigned To:

Re: [CMake] Specify 32-bit compilation to Clang

On 19.01.2015 21:08, Robert Dailey wrote: I have done this and it fails while linking the test program during configuration: /usr/bin/ld: cannot find crtbegin.o: no such file or directory /usr/bin/ld: cannot find -lgcc /usr/bin/ld: cannot find -lgcc_s Any ideas? Try installing the

[Cmake-commits] CMake branch, next, updated. v3.1.0-2211-g53a30cb

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 53a30cbdf04d7f04097473c451d1a5a1bfbba506 (commit) from

Re: [CMake] CPack. Modifying the installation prefix when building relocateable RPMs. v3.0.1

2015-01-19 17:06 GMT+01:00 alan.thomp...@glasgow.ac.uk: I am trying to build rpms for projects so they can be installed together using a modified yum into a user defined area as new_prefix/project/platform/installed_binaries hence the rpms should look like

[Cmake-commits] CMake branch, next, updated. v3.1.0-2215-g7b307f3

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-2210-gb37304e

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-2212-g4bb9d1e

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 4bb9d1e3dfe398e2835387cf1dd0b9c753fbf7d1 (commit) from