Re: [CMake] Compiling binaries with cmake -- help

I'll get the Python sipconfig module installed, then I hope we can continue with getting it compiled ? Nicholas Braden Thursday, June 23, 2016 1:15 AM Yes, many projects do not include their dependencies and require you to obtain them yourself. In this case

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-504-g622d3b3

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

Re: [CMake] Compiling binaries with cmake -- help

Yes, many projects do not include their dependencies and require you to obtain them yourself. In this case it looks like you need the Python sipconfig module installed. On Thu, Jun 23, 2016 at 12:10 AM, Crest Christopher wrote: > It can work, but it's missing

Re: [CMake] Compiling binaries with cmake -- help

It can work, but it's missing dependencies ? Nicholas Braden Thursday, June 23, 2016 1:08 AM It looks like the instructions are there in the README. I tried building on my system but I'm missing some dependencies (e.g. at some point it finds my Python 3

Re: [CMake] Compiling binaries with cmake -- help

It looks like the instructions are there in the README. I tried building on my system but I'm missing some dependencies (e.g. at some point it finds my Python 3 installation and tries to run some code but fails due to a missing sipconfig module, which I am not familiar with). Generally, to build

Re: [CMake] Compiling binaries with cmake -- help

Hi, here is the github URL; I hope it will help, to help me understand how to compile and use should I come across a cMaker compiler installation in the future. Martin Maurer Thursday, June 23, 2016 12:45 AM Hello, how

Re: [CMake] Compiling binaries with cmake -- help

Hello, how about to share the github URL, which file you have downloaded or project you want to compile? I think this would make it much easier for readers to help. Best regards, Martin -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] Compiling binaries with cmake -- help

Hi, I'm trying to use an existing CMakeList.txt file. Nicholas Braden Wednesday, June 22, 2016 8:50 PM Are you trying to use an existing CMakeLists.txt, or are you trying to create your own? CMake doesn't just work on source files alone. On Wed, Jun 22, 2016

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-228-g46f49c9

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

[cmake-developers] patch for FindProtobuf.cmake

Folks, I believe I found a bug in FindProtobuf.cmake. Using set with two parameters will insert an unwanted semicolon, the list separator. The changes I made are like this (several occurrences): -set(_protobuf_include_path -I ${CMAKE_CURRENT_SOURCE_DIR}) +set(_protobuf_include_path

Re: [CMake] Compiling binaries with cmake -- help

Are you trying to use an existing CMakeLists.txt, or are you trying to create your own? CMake doesn't just work on source files alone. On Wed, Jun 22, 2016 at 7:30 PM, Crest Christopher wrote: > Hi, I'm hoping I can get some help on how to compile a repository from >

Re: [CMake] Dependency on imported target with ninja-generator

If Project B depends on Project A, you should probably be using the ExternalProject module with a superproject structure that builds both projects in the proper order. https://cmake.org/cmake/help/latest/module/ExternalProject.html Trying to manually call CMake is not really a good idea IMO -

[CMake] Compiling binaries with cmake -- help

Hi, I'm hoping I can get some help on how to compile a repository from github which is local on my machine with a series of folders which contain CPP extension files. I have chosen the folders for which most likely contain the correct files to compile the binaries followed by the folder to

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-502-g6c354f7

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

Re: [cmake-developers] Using a custom DSL compiler in CMake

On Tue, Jun 21, 2016 at 16:05:47 -0400, Brad King wrote: > On 06/21/2016 02:18 PM, Chris Bieneman wrote: > > Our DSL compiler can generate .d files, but hooking that up to > > CMake is a harder problem. > > With some work it may be possible to teach our Ninja generator how > to consume .d files

Re: [cmake-developers] CMake 32 and 64 bit packages on Windows

Brad King wrote: > I logged out and logged back in and > then everything gets the proper PATH. > > Then I un-installed again and had to logout/login again to get the > PATH updated for programs launched through shortcuts. Hmm, I didn't do any logging out or in. Maybe that was the cause.

[CMake] [ANNOUNCE] CMake 3.6.0-rc3 now ready for testing!

I am proud to announce the third CMake 3.6 release candidate. Sources and binaries are available at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.6 Release notes appear below and are also published at

[cmake-developers] [ANNOUNCE] CMake 3.6.0-rc3 now ready for testing!

I am proud to announce the third CMake 3.6 release candidate. Sources and binaries are available at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.6 Release notes appear below and are also published at

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

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.6.0-rc3 has been created at 47ca01bf6e1a869b65be4895ebbe00973198c1f3 (tag) tagging

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-516-g224e195

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

[Cmake-commits] CMake branch, release, updated. v3.6.0-rc2-19-gd152ae1

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-246-g68bb74d

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

[CMake] Dependency on imported target with ninja-generator

Hi list, I'm finding myself in the following situation. - Project A generates libmain.a and export(TARGETS ... NAMESPACE ns) it to a file. The target is called ns::main - Project B includes this file and has some executables link with libmain.a (via target_link_libraries(exe ns::main). -

[CMake] [iOS] What is the correct way to add resources to an XCode project

Hello, I read the mailing list but did find a way which works. At the moment I use Xcode 7.3.1 and CMake 3.5.2 which creates a project for iOS 9.3. All I want is to add the directory "Images.xcassets" and a second directory structure to be copied to the Resource folder listed in XCode. When

[cmake-developers] [iOS] What is the correct way to add resources to an XCode project

Hello, I read the mailing list but did find a way which works. At the moment I use Xcode 7.3.1 and CMake 3.5.2 which creates a project for iOS 9.3. All I want is to add the directory "Images.xcassets" and a second directory structure to be copied to the Resource folder listed in XCode. When

Re: [CMake] CMake generator executable variable

Hi Petr, On Wed, 22 Jun 2016 16:52:17 +0200 Petr Kmoch wrote: > Hi Patrick. > > If the "subproject" is also CMake-generated, as you say, the best way > to build it would be: > > add_custom_target(build-app > COMMAND ${CMAKE_COMMAND} --build #... other options as >

Re: [CMake] CMake generator executable variable

Hi Patrick. If the "subproject" is also CMake-generated, as you say, the best way to build it would be: add_custom_target(build-app COMMAND ${CMAKE_COMMAND} --build #... other options as appropriate ) You might also have to set the WORKING_DIRECTORY. This should give you a

[CMake] CMake generator executable variable

Hi list, In my project some people use Ninja as a generator, some use GNU Make. In a part of my projects I have a add_custom_command() which runs, for convenience, the build of another cmake-generated project in another dir using a different set of compilers (which is the reason for not being a

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-514-ga01cf97

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

[Cmake-commits] CMake branch, release, updated. v3.6.0-rc2-18-gc41dfda

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-244-g4561816

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-511-g0bd64de

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-507-g6718a8f

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-239-ged59f4b

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-241-g54e293d

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-237-g110270f

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

Re: [cmake-developers] Patch: Add the ability to specify SDK_REFERENCES for Visual Studio

On 06/21/2016 09:25 PM, Gilles Khouzam wrote: > I've changed it to the Debug Universal C-Runtime > > This also leverages the version of the SDK to match the other > extensions reducing the risk of failures. Thanks, I've squashed that fixup in: VS: Add VS_SDK_REFERENCES target property to

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-502-g4bb7a7f

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-500-g8d5c192

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

[cmake-developers] handling components in Find****

Hi, I am trying to write a Find module with components and I am not sure of how it should be written. I attached the find module, Could someone tell me if I did it well? Thanks, -- Arnaud FARBOS FindILMBase.cmake Description: Binary data -- Powered by www.kitware.com Please keep messages

Re: [CMake] help with OBJECT libraries hierarchy

Ahoj Miro, object libraries are not intended for linking. The way it works is you expand the $ genex into the list of *sources* of the consuming target. In other words, the string '$' needs to go into the add_executable(foo) or add_library(foo) command, not into target_link_libraries(foo). Petr

[CMake] help with OBJECT libraries hierarchy

Dear experts, I am trying to introduce OBJECT libraries into our project, http://www.diracprogram.org. Into local src/functionality1/CMakeLists.txt I changed add_library(main ${local_sources}) to add_library(main OBJECT ${local_sources})