Re: [CMake] Does Makefile generated by CMake support make -jN?

> > Thanks for your analysis for me Andrew. I can't use "-j" options, i think > the reason is the project i dealed with is not parallel. Thus when i use "make > -jN", it couldn't work correctly every time. Obviously it caused by the > Makefile generated by CMake, so i wonder if there are some

[CMake] excluded from build in Visual Studio project

I have a use case that I haven't had much luck googling. I have a project that needs to have files visible in the Visual Studio IDE but marked with the red "Excluded from build" symbol. The source files are not needed in any way for the visual studio project, but for example, they use functions

Re: [CMake] excluded from build in Visual Studio project

Somewhat related, the following thread from a few days ago may be helpful: http://public.kitware.com/pipermail/cmake/2016-July/063897.html In short, you probably want to use add_custom_target() without the ALL keyword. On Thu, Jul 14, 2016 at 8:35 AM, Michael Legleux

Re: [CMake] excluded from build in Visual Studio project

Hi, I think you can add any files to a library/executable target and they will show up in the IDE. If the files are actual source code files such as .cpp/.c/.cxx you can set HEADER_FILE_ONLY property on them so that they do no get compiled when the target is built the

Re: [CMake] Does Makefile generated by CMake support make -jN?

Thanks for your references Decker, the condition is it cost close to three times time after i use CMake than already exist makefile to build project. And i found the CPU didn't use effectively than exist make flow, so i wonder if CMake provide some options to use CPU more effectively. Thanks,

Re: [CMake] Does Makefile generated by CMake support make -jN?

Thanks for your analysis for me Andrew. I can't use "-j" options, i think the reason is the project i dealed with is not parallel. Thus when i use "make -jN", it couldn't work correctly every time. Obviously it caused by the Makefile generated by CMake, so i wonder if there are some CMake options

Re: [CMake] Splitting in multiple directories

On Tuesday 12 July 2016 09:00:43 portolan wrote: > Hello, > > I am new to Cmake and I have a pretty strange behaviour: I set my c+++ > project to work with a single CMakefile.txt, and now I am trying to have > a more proper version with a .txt for each subdirectory > > Pretty normal stuff, my

Re: [CMake] CMake Reports Incorrect HDF5 Libraries on OS X after 3.6.0 Upgrade

Rad, I can verify that the issue is resolved in the git repo if anyone else is running into the bug. Thanks! On Tue, Jul 12, 2016 at 5:12 AM, Robert Maynard wrote: > Hi Breannan, > > You can track the status of the fix at >

[CMake] ANN: CMake Course - October 10 in Lyon, France

Kitware will be holding a CMake training course on October 10, 2016 at Kitware's office in Lyon, France. This one-day course will cover CMake, CTest, CPack and CDash. Visit our website for more information and registration details (early registration and student discounts available):

[Cmake-commits] CMake branch, next, updated. v3.6.0-830-gd74b003

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-834-gea24f62

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

Re: [cmake-developers] [PATCH] Improve FindGIF version detection (fix for issue #16196)

On 14/07/16 01:52, Brad King wrote: On 07/12/2016 11:16 PM, Ben Campbell wrote: A fix for https://gitlab.kitware.com/cmake/cmake/issues/16196 Thanks! Here are some comments. [snip] Cool - very helpful! I've revised my patch to: - only scan the headerfile once - update the docs in the

[cmake-developers] [CMake 0015749]: Make the URL option of ExternalProject_Add to accept lists

Hello there, I try to continue the work from André. With the attached patch it is possible to use a list of URLs but it is still limited to a single path. I think for a mix of pathes/URLs we need to move a lot of code from ExternalProject.cmake into ExternalProject-download.cmake. Maybe it is

[cmake-developers] [PATCH v5] SystemTools: Teach GetEnv to use correct encoding on Windows

From: Dāvis Mosāns On Windows getenv (and putenv) uses ANSI codepage so it needs to be encoded to internally used encoding (eg. UTF-8). Here we use _wgetenv (and _wputenv) instead and encode that. Change-Id: I8cb91f2386eb0efe3ef0a3132d1603217d710b60 --- SystemTools.cxx|

[Cmake-commits] CMake branch, master, updated. v3.6.0-389-g59f2319

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

Re: [cmake-developers] [CMake 0015749]: Make the URL option of ExternalProject_Add to accept lists

Looks like you could also use a list of paths if you express them in "file://..." form. Local files can also be expressed as URLs. David C. On Wed, Jul 13, 2016 at 4:18 AM, Schmertmann, Lars wrote: > Hello there, > > I try to continue the work from André. >

Re: [cmake-developers] [CMake 0015749]: Make the URL option of ExternalProject_Add to accept lists

Thanks for the hint. I removed the ^ to replace all occurrences and not only the first one. ExternalProject.cmake, Line 1670: string(REGEX REPLACE "^file://" "" url "${url}") Lars S. Am 13.07.2016 um 11:14 schrieb David Cole: > Looks like you could also use a list of paths if you express

[Cmake-commits] CMake branch, next, updated. v3.6.0-817-g7650a13

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

[Cmake-commits] CMake branch, release, updated. v3.6.0-8-g9c9ac04

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-386-g41c3c9a

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-823-g7ed0ced

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-388-g53df6d5

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-812-g1f35c2a

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-819-g33aaf51

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-821-g3068a61

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

Re: [cmake-developers] [PATCH] Improve FindGIF version detection (fix for issue #16196)

On 07/12/2016 11:16 PM, Ben Campbell wrote: > A fix for https://gitlab.kitware.com/cmake/cmake/issues/16196 Thanks! Here are some comments. > the pairs of file()/string() > commands seem a bit convoluted for extracting strings out of the header > file - is there a more idiomatic approach?

Re: [cmake-developers] [CMake 0015749]: Make the URL option of ExternalProject_Add to accept lists

On 07/13/2016 05:35 AM, Schmertmann, Lars wrote: > Thanks for the hint. I've merged to `next` for testing: ExternalProject: Add support for multiple alternative URLs https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2eec433f >>> I think for a mix of pathes/URLs we need to move a lot of code

[Cmake-commits] CMake branch, next, updated. v3.6.0-791-g342c1cd

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-796-g1b9b42e

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-808-g8e80c68

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-382-g291e418

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-810-gfb6b92b

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-794-g347ab9b

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-366-g602d95d

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-364-g40f24f0

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-379-g7a31a27

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-368-g4b726a3

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-373-g7f36d89

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-361-g43875ca

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-370-g64095e3

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-375-gde1f409

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

Re: [cmake-developers] cmake -E capabilities

Ping? On Mo, 2016-07-11 at 14:13 +, Tobias Hunger wrote: > https://github.com/hunger/CMake/commits/cmake-capabilities > > is in a state now that could use another review. -- Tobias Hunger, Senior Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin

Re: [cmake-developers] [PATCH v4] Add MinGW support for FStream

On 07/12/2016 10:05 PM, Dāvis Mosāns wrote: > std::basic_filebuf::open(const wchar_t *) isn't part of C++ standard > and it's only present for MSVC but it isn't present in libstdc++ (MinGW) > so we implement this functionality using GNU libstdc++ stdio_filebuf > extension and _wfopen function.