[Cmake-commits] CMake branch, next, updated. v3.4.1-1688-g68f9dcb

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1692-g65b3b57

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1684-g64cfea7

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

Re: [cmake-developers] [PATCH] Add Clang support to FindOpenMP

On 12/10/2015 10:49 AM, Chris Pavlina wrote: > Attached is a patch to add the correct option for building OpenMP > code using Clang. Thanks, applied: FindOpenMP: Add Clang support https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1549927d -Brad -- Powered by www.kitware.com Please keep

Re: [CMake] Problem when using variable_watch with Visual Studio generator in 3.4.1

I've got a Debug build of current 'master' on Windows, and the problem is also evident with my build: C:\dev\dcole\tmp\variable_watch_problem\b1> "C:\dev\repos\My Tests\cmake Win32-ninja-cl12-Debug\bin\ cmake.exe" -G Ninja .. -- The CXX compiler identification is MSVC 18.0.31101.0 -- Check for

Re: [cmake-developers] set(CACHE) and the local scope

On Wednesday, December 09, 2015 17:35:28 Ben Boeckel wrote: > Hi, > > So some behavior I was unaware of until today came up: > > set(var ON) > option(var "description" OFF) > message("var: ${var}") Assuming I wouldn't know about the subtle characteristics of normal vs. cache

Re: [CMake] CMake target_link_libraries items should be quoted or not? Linux/Ubuntu 14.04 cmake 3.4.1

On Thu, Dec 10, 2015 at 12:15 AM, Petr Kmoch wrote: > Hi, > > Side note: you probably shouldn't be using the -l prefix with arguments to > target_link_libraries(). The arguments are normally supposed to be either > CMake target names, or full paths to the libraries you want

Re: [cmake-developers] [CMake][PATCH] AIX RPATH handling

Hi, I identify the root of the problem: if I specify version 3.4 in cmake_minimum_required, generated link command (stored in file link.txt) for an executable does not contains value specified in variable CMAKE_SHARED_LIBRARY_LINK_${lang}_FLAGS. Specifying 3.3 fix the problem. So this is a

Re: [CMake] organizing includes statements

oh cool adding target_include_directories(lib1 PUBLIC ${CMAKE_CURRENT_SOURCE_DIR}/headers) and then I can just use #include "lib1" where needed. No more of those very static paths! Thank you very much! On Thu, Dec 10, 2015 at 4:08 PM, iosif neitzke < iosif.neitzke+cm...@gmail.com> wrote: > I

Re: [CMake] organizing includes statements

that's actually a good point. Currently as I am developing this i am doing an out of source build and just testing it from there but eventually what I want is a shared library that can be used by other programs. currently though my other programs is just a simple main.c that includes the main

Re: [CMake] organizing includes statements

I would think add_library( lib1 SHARED lib1/lib1.c ) target_include_directories( lib1 PUBLIC lib1/headers ) is simpler. Are the generator expressions needed for target export install commands, and is exporting targets at install preferred to add_subdirectory() ? On Thu, Dec 10, 2015 at 1:48

Re: [CMake] CMake target_link_libraries items should be quoted or not? Linux/Ubuntu 14.04 cmake 3.4.1

Hi, yes, that is indeed expected behaviour. target_link_libraries() takes a CMake list of arguments - one library per argument. When you surround the thing with quotes, it's a single argument (containing some spaces). So for this call: target_link_libraries(Debug "${VTK_LIBRARIES}

Re: [CMake] organizing includes statements

Hi Owen, Sorry to jump into the discussion, but what you're talking is something I was thinking of just recently... I think the choice between this: On Thu, Dec 10, 2015 at 3:48 PM, Owen Alanzo Hogarth wrote: > set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib) >

[Cmake-commits] CMake branch, next, updated. v3.4.1-1695-gcaa83f4

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

Re: [CMake] Parallel jobs failed for cmake

On 12/10/2015 12:19 AM, Igor Sobinov wrote: igor 5460 0.0 0.0 101152 972 pts/3 S+ 08:10 0:00 | \_ make build_release -j5 igor 5466 0.0 0.0 106096 1164 pts/3 S+ 08:10 0:00 | \_ /bin/sh -c cd /home/igor/build_root/release_target; make release igor 5467 0.0 0.0 101184 1060 pts/3 S+ 08:10 0:00 | \_

Re: [cmake-developers] set(CACHE) and the local scope

On Thursday, December 10, 2015 15:26:54 Brad King wrote: > On 12/10/2015 03:20 PM, Alexander Neundorf wrote: > >> set(var ON) > >> option(var "description" OFF) > >> message("var: ${var}") > > > > I.e. on the first run it would be OFF (since that's the default value > > of the option), and all

Re: [cmake-developers] set(CACHE) and the local scope

On Thu, Dec 10, 2015 at 21:20:21 +0100, Alexander Neundorf wrote: > On Wednesday, December 09, 2015 17:35:28 Ben Boeckel wrote: > > So some behavior I was unaware of until today came up: > > > > set(var ON) > > option(var "description" OFF) > > message("var: ${var}") > > Assuming I

Re: [cmake-developers] set(CACHE) and the local scope

On 12/10/2015 03:20 PM, Alexander Neundorf wrote: >> set(var ON) >> option(var "description" OFF) >> message("var: ${var}") > > I.e. on the first run it would be OFF (since that's the default value > of the option), and all later runs it would have the value which is in the > cache. This is

[CMake] Forcing CMake to rerun

Hi all, I'm working on using CMake to create a build system that targets an incredibly hard-to-deal-with IDE/build system, used for doing some embedded programming (Xilinx's Vivado suite). One of the pieces I need to get working is a conditional dependency between two files (a project-file

Re: [cmake-developers] [PATCH] Imported targets for FindGTest

> - Add unit test to test imported targets and existing variables I should mention that to run the unit test, you must define the GTEST_ROOT environment variable to point to the gtest build, due to gtest being annoyingly crippled to be uninstallable for dubious reasons. You can pass

Re: [cmake-developers] [PATCH] Imported targets for FindGTest

> - Adds GTest::GTest and GTest::Main imported targets (including > Thread::Thread dependency for GTest::GTest and GTest::GTest for > GTest::Main; the latter might not be appropriate and could be removed if > needed--but I'm unaware of any situation where you would want to use > GTest::Main

[Cmake-commits] CMake branch, next, updated. v3.4.1-1698-gd3ccdd3

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

[cmake-developers] [PATCH] Imported targets for FindGTest

Pushed to https://cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/gtest- imported-targets and merged into next for review and testing. - Adds GTest::GTest and GTest::Main imported targets (including Thread::Thread dependency for GTest::GTest and GTest::GTest for GTest::Main; the

Re: [CMake] Problem when using variable_watch with Visual Studio generator in 3.4.1

Out of curiosity, what output do you get (with 3.4.1) when you comment out your call to variable_watch? Do you still get error output, but without strange symbols in it? Or is there no error output in that case? On Thursday, December 10, 2015, Yves Frederix wrote:

Re: [cmake-developers] Please comment on ios-universal topic

On 10-Dec-15 13:55, Gregor Jasny wrote: Hello, On 09/12/15 10:21, Ruslan Baratov wrote: IOS_INSTALL_COMBINED_BINARY Just to clarify you want to leave only one variable IOS_INSTALL_COMBINED_BINARY for the device + simulator on iOS platforms. Other platforms (in future) will be controlled by

Re: [CMake] Problem when using variable_watch with Visual Studio generator in 3.4.1

After commenting out the call there is no error output: -- The CXX compiler identification is MSVC 17.0.61030.0 -- Check for working CXX compiler using: Visual Studio 11 2012 Win64 -- Check for working CXX compiler using: Visual Studio 11 2012 Win64 -- works -- Detecting CXX compiler ABI

[CMake] Problem when using variable_watch with Visual Studio generator in 3.4.1

Hi all, I am experiencing problems during the CMake configure step when using the function variable_watch. Consider the following minimal CMakeLists file: cmake_minimum_required(VERSION 3.4) project(test CXX) function(myhook _variable _access _value _current_list_file _stack)

[CMake] ExternalProject_Add and inheritance

Hello, I use the ExternalProject_Add command to manage third-party libraries. In the same time, I need to overcome some compatibility problems between GCC 4 and GCC 5 (strings are not defined in the same way in the STL). The solution I use is the one given here:

Re: [CMake] How to set environment variables with spaces in commands

On 10-Dec-15 12:52, Attila Krasznahorkay wrote: Hi QP, Probably not the intended solution, but what I’m doing in such cases is that in a patch step I create a shell script that does the configuration for me. With all the environment settings and everything. Like: PATCH_COMMAND

[Cmake-commits] CMake branch, next, updated. v3.4.1-1663-gf447ad4

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

Re: [cmake-developers] [PATCH] Support multiple directories by "cmake -E make_directory" command

On 12/09/2015 03:01 PM, Bartosz Kosiorek wrote: > support for multiple directories for make_directory command. Thanks. Applied with minor documentation tweak: cmake: Teach -E make_directory to support multiple input directories https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7984ac5e

[CMake] error while loading shared libraries: libLLAPI.so: cannot open shared object file: No such file or directory

Hi, getting following error when trying to run LLAPI_TestApp ./LLAPI_TestApp: error while loading shared libraries: libLLAPI.so: cannot open shared object file: No such file or directory Both LLAPI_TestApp and libLLAPI.so are present in same directory Bin/Wind. CMakeLists.txt for

Re: [CMake] How to set environment variables with spaces in commands

Hi Ruslan, Thanks, this is good to know. I absolutely agree that one needs to avoid using "&&" in the commands themselves. As it also causes problems when you try to use CTEST_USE_LAUNCHERS=1. (I myself ran into that issue...) But I did not have any issues so far with putting "whatever" into

Re: [cmake-developers] [CMake][PATCH] AIX RPATH handling

On 12/10/2015 04:03 AM, CHEVRIER, Marc wrote: > I identify the root of the problem: if I specify version 3.4 in > cmake_minimum_required, generated link command (stored in file link.txt) > for an executable does not contains value specified in variable > CMAKE_SHARED_LIBRARY_LINK_${lang}_FLAGS.

Re: [cmake-developers] [CMake][PATCH] AIX RPATH handling

Ok. I see the problem. Thanks for your investigation. I will work on that and submit a patch to solve this problem. Marc On 10/12/15 14:42, "Brad King" wrote: >On 12/10/2015 04:03 AM, CHEVRIER, Marc wrote: >> I identify the root of the problem: if I specify version

Re: [cmake-developers] set(CACHE) and the local scope

On 12/09/2015 05:35 PM, Ben Boeckel wrote: > So some behavior I was unaware of until today came up: > > set(var ON) > option(var "description" OFF) > message("var: ${var}") > > outputs "OFF" for the first configure and "ON" for subsequent > configures. This is because set(var CACHE)

Re: [CMake] ExternalProject_Add and inheritance

With CMake, you can control compilation and link flags with the following environment variables: * CC: specify C compiler * CFLAGS: C compiler flags * CXX: specify C++ compiler * CXXFLAGS: C++ compiler flags * LDFLAGS: linker flags And to finish you can overload make command

[cmake-developers] [PATCH] Add Clang support to FindOpenMP

Hi, Attached is a patch to add the correct option for building OpenMP code using Clang. Per the llvm release notes it is necessary to give -fopenmp=libomp to build properly, not just -fopenmp. Tested on 64-bit Linux using

[cmake-developers] [CMake 0015877]: Performance regression in file generation

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15877 == Reported By:Jim King Assigned To:

[Cmake-commits] CMake branch, master, updated. v3.4.1-669-g693abba

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20151210) +set(CMake_VERSION_PATCH 20151211) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, next, updated. v3.4.1-1675-gd9556ec

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1667-g91798eb

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-668-gfc6c507

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

[cmake-developers] [Apple/iOS/OS X] Create subdirectories in Resource directory for Frameworks and Application bundle.

Hello. With CMake 3.5 it is possible to put Resources into the Bundle (Frameworks and Applications) More information: https://cmake.org/gitweb?p=cmake.git;a=blob;f=Help/prop_tgt/RESOURCE.rst So with code: add_executable(ExecutableTarget addDemo.c resourcefile.txt

[Cmake-commits] CMake branch, next, updated. v3.4.1-1672-gb40c3f7

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

Re: [cmake-developers] set(CACHE) and the local scope

On Thu, Dec 10, 2015 at 08:50:10 -0500, Brad King wrote: > That is a long-standing subtlety introduced without discussion, review, > or tests here: > > BUG: change in how set cache overrides local definitions. Should mainly be a > NOP change for most cases >

Re: [CMake] error while loading shared libraries: libLLAPI.so: cannot open shared object file: No such file or directory

Am Donnerstag, 10. Dezember 2015 um 12:38:11, schrieb Nikita Barawade > > Hi, > > getting following error when trying to run LLAPI_TestApp > > ./LLAPI_TestApp: error while loading shared libraries: libLLAPI.so: cannot > open shared object file: No such file or

[Cmake-commits] CMake branch, next, updated. v3.4.1-1680-g3c09aff

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1678-gd94e61a

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

[CMake] Visual Studio 10 and wxWidgets

Hi all. I'm in trouble with wxWidgets 3 and Visual Studio 10 express. I need to change the type of libraries depending on the configuration compiler If I compile in debug mode I need wxbase30ud.lib, while in release mode wxbase30u But if I generate the project for VS2010Express the

[Cmake-commits] CMake branch, next, updated. v3.4.1-1682-g987c2cf

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

Re: [CMake] error while loading shared libraries: libLLAPI.so: cannot open shared object file: No such file or directory

is '.' in your LD_LIBRARY_PATH and/or /etc/ld.config? otherwise 'LD_LIBRARY_PATH=. ./LLAPI_TestApp' should work... or export LD_LIBRARY_PATH=. for a more semi-permanent solution? On Thu, Dec 10, 2015 at 4:38 AM, Nikita Barawade wrote: > > > Hi, > > getting