Re: [cmake-developers] CMake aliasing system

On 15-Mar-16 02:42, Tamás Kenéz wrote: I also doubt this belongs to upstream. But you could write a single, generic script which forwards its arguments to cmake and also accepts and processes the additional parameters along the way. I don't think we'd lose anything: cmakeini -c ipad -H.

[cmake-developers] [CMake 0016020]: FindBoost "Automatically add missing component dependencies" fails with header-only libraries

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=16020 == Reported By:Tom Jakubowski Assigned To:

[cmake-developers] [PATCH] Ninja: Optionally skip library dependencies for object targets

Hi, this is a patch that we use since some time for a quite large in-house project. The idea behind is to increase build parallelism by omitting dependencies of object file targets to the libraries they will be linked with in a later step. As this is not always the desired behaviour the default

[cmake-developers] [CMake 0016019]: cmake-mode.el: cmake-help: one help item is missing for each 'type'

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=16019 == Reported By:Julian Schmidt Assigned To:

[cmake-developers] BUG: ALL_BUILD not added to the PREDEFINED_TARGETS_FOLDER

For the Visual Studio generator, the ALL_BUILD is not added to the PREDEFINED_TARGETS_FOLDER ("CMakePredefinedTargets"). Tested on Windows 10 with Visual Studio 2013 using the following minimal CMakeLists.txt: cmake_minimum_required(VERSION 3.5) project(foobar) set_property(GLOBAL PROPERTY

Re: [cmake-developers] CMake aliasing system

I also doubt this belongs to upstream. But you could write a single, generic script which forwards its arguments to cmake and also accepts and processes the additional parameters along the way. I don't think we'd lose anything: cmakeini -c ipad -H. -DTHIS_WILL_BE_FORWARDED=AS_IT_IS This is

[cmake-developers] [CMake 0016018]: macros CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS don't work

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=16018 == Reported By:abductor Assigned To:

Re: [cmake-developers] CTest custom HTML

Yeah, makes sense. Thanks so much for your time Le lun. 14 mars 2016 à 15:58, Brad King a écrit : > On 03/14/2016 05:13 AM, Charles Huet wrote: > > If the CTest parser parsed the output as XML and not simple text, it > should be > > able to recognize CDATA from actual

Re: [cmake-developers] CMake aliasing system

On 14-Mar-16 21:59, Brad King wrote: On 03/12/2016 08:04 AM, Ruslan Baratov via cmake-developers wrote: I guess it is a well known fact that cmake command is almost never executed alone and for non-trivial examples usually hold some extra arguments (home directory, build directory, verbosity

Re: [cmake-developers] CTest custom HTML

On 03/14/2016 05:13 AM, Charles Huet wrote: > If the CTest parser parsed the output as XML and not simple text, it should be > able to recognize CDATA from actual markup. [snip] > If you don't think this is doable (or you don't want to integrate this kind > of behavior into CTest) we'll customize

Re: [cmake-developers] FindGTest modification

On 03/11/2016 12:00 PM, Zak Eckert wrote: > + configure_file(${source} ${source}.out COPYONLY) Thanks. Please try using CMAKE_CONFIGURE_DEPENDS instead: https://cmake.org/cmake/help/v3.5/prop_dir/CMAKE_CONFIGURE_DEPENDS.html It should be something like: set_property(DIRECTORY APPEND

Re: [cmake-developers] CMake aliasing system

On 03/12/2016 08:04 AM, Ruslan Baratov via cmake-developers wrote: > I guess it is a well known fact that cmake command is almost never > executed alone and for non-trivial examples usually hold some extra > arguments (home directory, build directory, verbosity level, toolchains, > options,

Re: [cmake-developers] CPack includes WINTRUST.DLL

On 03/12/2016 05:19 PM, Roman Wüger wrote: > Yes, i use fixup_bundle. > Is there a better alternative? No, but you'll have to trace through its execution to see where it picks up the dependency on wintrust.dll. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the

Re: [cmake-developers] Duplicated linking flags are removed when linking final executable

On 03/14/2016 09:33 AM, Sergio Checa wrote: > target_link_libraries(L > -Wl,-whole-archive A -Wl,-no-whole-archive > -Wl,-whole-archive B -Wl,-no-whole-archive > ) > > add_executable(main main.cpp) > target_link_libraries(main L) Specifying flags anywhere except

Re: [cmake-developers] FindBoost.cmake Clang support

On 03/12/2016 12:42 PM, Manu Sánchez wrote: > I'm reaching you to ask about Clang support in the FindBoost.cmake script. [snip] > if(CMAKE_CXX_COMPILER_ID MATCHES "Clang") > execute_process(COMMAND ${CMAKE_CXX_COMPILER} --version > OUTPUT_VARIABLE out) Thanks. Rather than running

Re: [cmake-developers] [RFC] FindAndroidNDK and UseAndroidNDK

On 03/12/2016 04:05 AM, Xiaolei Yu wrote: > my team decided to ditch ndk-build and migrate to cmake. And I would > like to upstream these two modules, which are currently used in my hobby > projects. Thanks. Yes, code to search for the Android NDK or a standalone toolchain belongs in CMake

[cmake-developers] [CMake 0016017]: Setting OPTION to ON results in FALSE

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

[cmake-developers] Duplicated linking flags are removed when linking final executable

Hello, This is my first email to this list, so please tell me if I'm not following the contribution process properly. Here is the scenario that I am working on: .---> -flags A | main > L -| | '---> -flags B

[cmake-developers] Support CMAKE_IOS_INSTALL_COMBINED for single architecture targets

Hi, Though user can explicitly set CMAKE_IOS_INSTALL_COMBINED=OFF for targets with empty list of supported architectures for given SDK (say simulator) I think it make sense to handle this case correctly in CMake module too. Patch with fix and test attached. Thanks, Ruslo >From

Re: [cmake-developers] CTest custom HTML

>You could use DartMeasurementFile to upload arbitrary files with the CTest submission, and then teach CDash what to do with them. Hmm, this sounds to me like too much custom logic would be in CDash, which would never make it upstream, and we have bad experiences maintaining this kind of patch

Re: [cmake-developers] Ninja and add_subdirectory EXCLUDE_FROM_ALL

Hi, I modified my patch a bit to use C++98 only, and try to stick to the coding conventions. This now adds a target per folder, which contains all the targets in the folder and all its children folders. These targets are prefixed with "path/" in order to set them apart of normal CMake targets.