[Cmake-commits] CMake branch, master, updated. v3.5.0-180-g6b9dc80

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

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Makes sense, thank you so much Nicholas! I will give this a try. On Tue, Mar 8, 2016 at 5:19 PM, Nicholas Braden wrote: > Yep, just make each project act independently with no knowledge of the > superproject, and have the superproject glue it all together as a >

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Yep, just make each project act independently with no knowledge of the superproject, and have the superproject glue it all together as a convenience for the user if they don't want to manually build things separately or if they don't have existing installs. That's what I am doing with my projects.

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Wow, this is powerful! Question; Will I be able to compile the sub-project individually? Because as I see this is what we will use in the root/CMakeLists.txt, but what about the sub-dirs which I really want to be "independent" if the user wants. On Tue, Mar 8, 2016 at 5:13 PM, Nicholas Braden

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Example simple usages from my personal projects: https://github.com/LB--/events/blob/499ba78b923b40f77cc832b6a5d414240209ac96/CMakeLists.txt https://github.com/LB--/simple-platformer/blob/1bba3dd2d8ed1cdae74ce1b77c4ab99878fa59a6/CMakeLists.txt More complex usage in hunter:

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Thank you for your suggestion Nicholas, I have never used ExternalProject_Add before and can't find a related example to my project. Would you know an example that uses it? On Tue, Mar 8, 2016 at 10:38 AM, Nicholas Braden wrote: > Have you looked into

Re: [cmake-developers] set_test_properties ignoring multiple properties

On Tue, Mar 08, 2016 at 14:36:38 -0700, Kael Dai wrote: > I have a test that outputs multiple lines and want to use > set_tests_properties with the PASS_REGULAR_EXPRESSION property to check > different lines in the output. I've tried doing > > set_tests_properties(test1 PROPERTIES

Re: [cmake-developers] set_test_properties ignoring multiple properties

On 08.03.2016 22:36, Kael Dai wrote: Hi, I have a test that outputs multiple lines and want to use set_tests_properties with the PASS_REGULAR_EXPRESSION property to check different lines in the output. I've tried doing set_tests_properties(test1 PROPERTIES PASS_REGULAR_EXPRESSION "value1"

[cmake-developers] set_test_properties ignoring multiple properties

Hi, I have a test that outputs multiple lines and want to use set_tests_properties with the PASS_REGULAR_EXPRESSION property to check different lines in the output. I've tried doing set_tests_properties(test1 PROPERTIES PASS_REGULAR_EXPRESSION "value1" PASS_REGULAR_EXPRESSION "value2") I've

Re: [CMake] how to keep rpath from build to install

Srinath, You should better ask the list than me. It would help if you describe precisely what you tried, and what result you get. Best regards, Xavier On Tue, Mar 8, 2016 at 4:31 PM, Srinath Vadlamani < srinath.vadlam...@gmail.com> wrote: > Hello Xavier, > I have implemented all of what is

Re: [CMake] Best way to show/include CMake files in IDE

On 3/8/2016 2:25 PM, David Doria wrote: add_custom_target(MyProject_HDRS SOURCES MyHeader.h MyImplementation.hpp) It sounds like David says you can do the same for your .cmake files. This is pretty awkward though - it seems like there should be more of an explicit function for this, something

Re: [CMake] Best way to show/include CMake files in IDE

On Mon, Mar 7, 2016 at 9:19 PM, Eric Wing wrote: > On 3/7/16, Eric Wing wrote: > > On 3/7/16, David Cole wrote: > >> If you include those files in the source list for a library, executable, > >> or > >> custom target, they should show

[CMake] [ANNOUNCE] CMake 3.5.0 available for download

I am proud to announce that CMake 3.5.0 is now available for download at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.5 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.5/release/3.5.html Some of the more

[cmake-developers] [ANNOUNCE] CMake 3.5.0 available for download

I am proud to announce that CMake 3.5.0 is now available for download at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.5 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.5/release/3.5.html Some of the more

[Cmake-commits] CMake annotated tag, v3.5.0, created. v3.5.0

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 annotated tag, v3.5.0 has been created at 7d39803575a7b233e1780820d19b42aecad92cfe (tag) tagging

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Have you looked into ExternalProject_Add? It allows just using a local path instead of downloading a remote repository: https://cmake.org/cmake/help/latest/module/ExternalProject.html On Tue, Mar 8, 2016 at 12:12 PM, Muhammad Osama wrote: > Hi Jan, > > Thank you for your

Re: [cmake-developers] CTest custom HTML

On 03/08/2016 11:09 AM, Charles Huet wrote: > mostly useful to display images, since some of our tests compare > images with ImageMagick CTest/CDash already supports sending images for display. It was developed for the same purpose for VTK testing. The test output can contain

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Hi Jan, Thank you for your reply, I am in the similar situation, have a very similar implementation using *target_*** *but since I don't do that for ALL the dependencies, I am unable to cmake or compile individual projects in the sub directories. So, few questions; 1. This still requires me to

Re: [CMake] CTest usage

I hate to state the obvious, but set_property (TEST test2 PROPERTY LABELS LABEL1 LABEL2 LABEL1andLABEL2) I know it isn’t what you asked for, but I don’t want cmake to change, but I don’t think it is worthwhile to add more complex set algebra to the -L command so that we can support complex

Re: [CMake] Some Visual Studio/CMake questions

IIRC, the project() command can be called once per directory. So you can have each directory be a separate project via add_subdirectory(). I just tried it out and it seems to create a solution (*.sln) for each project(). I can't answer the other questions, sorry. On Tue, Mar 8, 2016 at 10:03

[cmake-developers] CTest custom HTML

Hi, to customize our test results, we developped a small test wrapper that outputs some HTML markup (mostly useful to display images, since some of our tests compare images with ImageMagick). However, this does not work since CMake 3.3 because of the refactoring of ctest to use cmXMLWriter,

[CMake] Some Visual Studio/CMake questions

Dear users, Since about a year I work on a project that uses CMake in combination with Visual Studio. This works kind of oke, but over time some questions have emerged. Hopefully I can get an answer on this list: * Our build infrastructure creates a Release and a Debug configuration by setting

Re: [CMake] find_package REQUIRED ignores OPTIONAL_COMPONENTS

Jakob, I don't think there is any confusion about what REQUIRED means. Whether or not REQUIRED is provided, the list of OPTIONAL_COMPONENTS should not be required under any circumstances. The example error message seems pretty clear to me that the expected behavior and actual behavior are

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-380-gde5a90b

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-188-geb094da

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

[Cmake-commits] CMake branch, release, updated. v3.5.0-rc3-9-gb369959

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-378-g9d65113

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

Re: [CMake] find_package REQUIRED ignores OPTIONAL_COMPONENTS

Hej Alexander, Yes, you're missing a subtle detail. You assume that the 'REQUIRED' keyword reflects the fact that COMPONENTS are required. This is not the case. The REQUIRED keyword reflects that the entire package Qt4 is required, see https://cmake.org/cmake/help/v3.0/command/find_package.html

Re: [CMake] Compile shared library and call it's functions

Hej, A short side-question - you mentioned you are compiling a DLL, yet you mention also you are on OSX. I'd expect a .dylib on OSX? Anywaysz, I think Andreas already answered your question quite clearly: you probably misinterpret the output of nm, since your CMakeLists.txt file looks exactly as

Re: [cmake-developers] C++11 only for a specified subdirectory

Hi Roman, If you only set set( CMAKE_CXX_STANDARD 11 ) in that subdirectory, then this should happen automatically. (Since the variable will not be visible as soon as you go out of the scope of this "subdirectory".) Otherwise you could just set the CXX_STANDARD property on the targets that

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-376-g6d0ea81

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-374-ge5720d2

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-371-g4cf2470

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

Re: [cmake-developers] patch for module GetPrerequisites

On 03/07/2016 05:41 PM, Benjamin Ballet wrote: > We have to call : > fixup_bundle("${CMAKE_INSTALL_PREFIX}/../test"... > to fix an optional test folder installed near the app. Thanks. I've made a slightly different fix that should resolve that: GetPrerequisites: Fix gp_resolved_file_type on

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-368-g4c7858b

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-366-g2a32a87

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-186-g4aaa8ad

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-363-gdf7151f

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

[Cmake-commits] CMake branch, release, updated. v3.5.0-rc3-8-g0e02c69

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-183-g6e7cfe7

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-359-g72e086b

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-357-g19cba30

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

[Cmake-commits] CMake branch, master, updated. v3.5.0-rc3-181-g7f1c9fa

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

[Cmake-commits] CMake branch, next, updated. v3.5.0-rc3-349-gd4c34c3

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

[CMake] cross-compilation: add dependency to all linked targets

Hi list, I'm building applications for an bare-metal sytem. There are no standard libraries. In my toolchain-file I specify set(CMAKE_SYSTEM_NAME "Generic") and I'm telling gcc to not include std-libraries with -nostdlib . In my toolchain-file I changed CMAKE_EXE_LINKER_FLAGS in order

[cmake-developers] [CMake 0016009]: FILES_MATCHING does not exclude empty directories

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

Re: [cmake-developers] Using CMake generated ninja file as a subninja file

Ben, Did you have a chance to review my patches? Cheers, Nicolas On Sunday, February 14, 2016, Nicolas Desprès wrote: > Ben, > > I have pushed a complete version of the patch here: > https://github.com/nicolasdespres/CMake/commits/ninja-output-path-prefix > > Since

[CMake] CTest usage

Hi, Is there someone able to help me regarding ctest usage with labels? Here is the problem: I have various tests which have labels attached to them: set_property (TEST test1 PROPERTY LABELS LABEL1) set_property (TEST test2 PROPERTY LABELS LABEL1 LABEL2) set_property (TEST test3 PROPERTY LABELS

Re: [CMake] Create main and sub-projects; be able to compile them together and individually.

Hi Muhammad, > On 08.03.2016, at 06:17, Muhammad Osama wrote: > > Hi, I am new to cmake and really hope am doing this correctly. I asked > stackoverflow but didn't get a good enough answer for my specific problem > here; > > If I want root/sub-directories/ as separate