[Cmake-commits] CMake branch, master, updated. v3.5.2-748-gd5ccab3

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

Re: [CMake] Cross Compilation & Source file generators

Nope, sorry. We build android from mac and windows too. And again, I'm more concerned with how protobuf's config.cmake scripts should be set up to easily enable users to deal with this problem. I'm trying to get their build scripts up to date before 3.0.0 leaves beta. On Tue, May 24, 2016 at 6:05

Re: [CMake] Cross Compilation & Source file generators

Another "outside the box" solution that I have had success with is as follows (Note this solution will only work with Linux): You can use the Linux binfmt_misc driver to execute non-native executables through an interpreter. If you google for qemu binfmt wrapper, you'll find various suitable

[CMake] CMake "Core Guidelines"?

It occurs to me that, much like C++ itself, there are wide variety of ways to do things in CMake, many of which exist only for legacy compatibility, and the language had a lot of active develpment recently that allows much safer, easier to read programs. C++ now has the Core Guidelines and lots of

[Cmake-commits] CMake branch, next, updated. v3.5.2-1553-g0365580

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

[CMake] Mac OS X framework building

Hi All, I am trying to make a framework using a shared library. The docs say that the target property PUBLIC_HEADER should be a list of interface header files that install(TARGET ...) will populate .../.framework/Headers/ with but I cannot get that to happen. I have set the target property

[Cmake-commits] CMake branch, next, updated. v3.5.2-1548-ge35490d

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

Re: [CMake] Cross Compilation & Source file generators

@Hendrik - Yes, unfortunately it didn't help me too much. Superbuilds are not really an appropriate solution here - The project I'm working on is too heavily down an alternative path, and I'm trying to set up the exported .cmake files in the protobuf 3.0 beta to properly support any sort of

Re: [CMake] Recommended style for multiple CPack generator folder structures

I prefer one for both installing and creating packages. install(TARGETS bar COMPONENT bar DESTINATION "./" # This must be "./" not "/" as it has to be a relative path ) Then set CMAKE_PREFIX_PATH=/Applications/Foo when you do an install. CMAKE_PREFIX_PATH will be pre-pended to relative

[Cmake-commits] CMake branch, master, updated. v3.5.2-745-g384de98

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1546-g4abb02a

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-747-ga98a699

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-739-gf77a49f

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-743-g185be83

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-741-g7d5355a

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1540-g95d23d0

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1536-g489d882

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1533-geec9b0f

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

Re: [CMake] Recommended style for multiple CPack generator folder structures

In answer to my own question. One way to do it which seems quite neat is as follows. Using multiple installs: install(TARGETS bar COMPONENT bar DESTINATION "Applications/Foo" ) install(TARGETS bar COMPONENT bar-standalone DESTINATION "./" # This must be "./" not "/" as it has to

[CMake] Recommended style for multiple CPack generator folder structures

On OSX we install an .app to /Applications/Foo/Bar.app. So the install() is set like: add_executable(bar MACOSX_BUNDLE bar.cpp ) install(TARGETS bar COMPONENT bar DESTINATION "Applications/Foo" ) When making DMG (DragNDrop) installers I really want the DMG to contain just the

Re: [CMake] How to use 'CMAKE_EXE_LINKER_FLAGS' correctly

This CMake feature is interesting, the first step i plan is to make the project work first, then i will try to optimize it, and i think this feature would be used next step. Thanks. :-) Chuck Atkins wrote > If you know the full path to the library then I'd suggest using it as >

Re: [CMake] How to Determine If a Perl Module Is Installed?

On Tue, May 24, 2016 at 3:52 AM, Eric Eide wrote: > As a CMake newbie, I was afraid that I was overlooking some sort of > "prepackaged" version of this. Doesn't look like it, but I agree it's the kind of thing that might be usefully included with CMake. -- Powered by

[Cmake-commits] CMake branch, next, updated. v3.5.2-1531-g43d02bf

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