Re: [CMake] GCC: -std=g++14 vs -std=c++14

On Mon, 13 Jun 2016 20:05:23 +0200 Patrick Boettcher wrote: > > You also need to correctly set the CXX_EXTENSIONS properties to get > > a standard standard. > > Yep, > > set(CXX_EXTENSIONS OFF) > > seems to do the trick - thanks. Well, it is

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-128-g909d51b

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

[CMake] Finding libxml2 when building llvm/clang

Building llvm/clang from source involves using CMake. I am building llvm/clang from source on Windows using CMake 3.5.2. I am not a clang developer, just a clang user. Similarly I just use CMake rather than understand or write CMakeLists.txt files. I reported a problem to clang where building

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-312-gff2a74b

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

Re: [CMake] CMAKE - troubles finding executables/paths - Windows 7 / MinGW

Yes, I know this [1] thread is old, but it hurts me, too. This is what I found: The mingw32 installer (mingw32-get, IIRC) no longer places a key in the windows registry. So if anyone installed mingw32 in a directory other than c:/MinGW/, cmake will not find it. After adding the bin directory of

Re: [cmake-developers] codeblocks generator: Fix include directories being in unexpected order

On Di, 2016-06-14 at 15:21 +, Tobias Hunger wrote: > Hello, > > https://github.com/hunger/CMake/commit/a87e306fd03e7fae7409b16e4e586083822c6fe > 8 https://github.com/hunger/CMake/commit/f190b069db2e430fd94b25e6287cd7fbc28661e3 Is the same thing updated based on suggestions from Stephen.

Re: [cmake-developers] Questions about coding conventions

- On Jun 14, 2016, at 8:09 AM, Daniel Pfeifer dan...@pfeifer-mail.de wrote: > On Tue, Jun 14, 2016 at 3:14 PM, Brad King wrote: >> On 06/13/2016 10:16 AM, Brad King wrote: Can't `std::ifstream` and `std::ofstream` be used directly? It seams that kwsys does

[cmake-developers] codeblocks generator: Fix include directories being in unexpected order

Hello, https://github.com/hunger/CMake/commit/a87e306fd03e7fae7409b16e4e586083822c6fe8 has a fix to not put include directories into random order while trying to make them unique. Would that be applicable for the next release? All Tests pass, with or without the patch. Best Regards, Tobias

[cmake-developers] Toward a more deterministic ninja generator

Hi, While working on something else I wrote this patch: https://github.com/nicolasdespres/CMake/commit/59e4e62ba014c6fcd4519b57b621d9434f99ff19 It makes the ninja generator more deterministic by sorting the build edge's inputs/outputs. It does not introduce any regression on my macbookpro. This

Re: [CMake] Provide configuration settings for users

Cedric, I would highly recommend an auto-builder such as Spack as a good way to have a system that automatically downloads and installs dependencies for your software. My software requires about 50 dependencies (once recursive dependencies are counted), and I've successfully used Spack to have

Re: [cmake-developers] Questions about coding conventions

On Tue, Jun 14, 2016 at 3:14 PM, Brad King wrote: > On 06/13/2016 10:16 AM, Brad King wrote: >>> Can't `std::ifstream` and `std::ofstream` be used directly? It seams >>> that kwsys does some workarounds >> >> Yes, std::{o,f}stream can be used directly. > > On second

Re: [cmake-developers] Installation of imported targets

On 06/13/2016 06:12 PM, Elie Roudninski wrote: > Everything works fine except when you need to install the imported target. > You can't use the regular: > install(TARGETS myimportedlib LIBRARY DESTINATION lib) > It is not permitted for imported targets. At the moment, i usually use: >

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-306-g6efb921

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

Re: [CMake] Provide configuration settings for users

Hi Cedric, It sounds like creating a package config file is exactly what you need. When installed, a user will be able to consume your project with "find_package(Foo)". That will locate and read the package config file which will create an imported target Foo::Foo. This imported target will

Re: [cmake-developers] Questions about coding conventions

On 06/13/2016 10:16 AM, Brad King wrote: >> Can't `std::ifstream` and `std::ofstream` be used directly? It seams >> that kwsys does some workarounds > > Yes, std::{o,f}stream can be used directly. On second thought, std::{i,o}fstream should not be used to open files. The cmsys::{i,o}fstream

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-304-g68b0ed4

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

[CMake] Provide configuration settings for users

Hello, is there a native way to provide configuration settings for the users of a software? For example, I develop a software which depends on several 3rd party libraries which are automatically downloaded and installed with the ExternalProject module. My CMake configuration scripts are

Re: [cmake-developers] daemon-mode: Infrastructure

PS: I think it would make perfect sense to ship the first cmake version with included daemon-mode with a big, fat warning that the interfaces are not finalized yet and will change in incompatible ways during the first release cycle (or maybe two:-). In my experience you only get the full feedback

[cmake-developers] fixup! Remove redundant arguments from fstream constructors

This is a fixup for the std-fstream topic. From 1d52cfe88e98738a1f1172cd1723a07ac579d2eb Mon Sep 17 00:00:00 2001 From: Daniel Pfeifer Date: Tue, 14 Jun 2016 09:47:46 +0200 Subject: [PATCH] fixup! Remove redundant arguments from fstream constructors ---