Re: [cmake-developers] cmake fails to identify C and CXX compiler when building universal

On 09/29/2015 04:38 AM, Ryan Schmidt wrote: Hello, I am a developer with the MacPorts package management system, and I want to report to you a bug in cmake 3.3.2 that affects OS X. I was going to file a bug report in your issue tracker, but the bright yellow box at the top of the "report

Re: [cmake-developers] CXX_STANDARD and linking

On Solaris, activating C++11 standard switch the compiler into a completely different mode: * Mangling is different * C++ runtime is the GNU one, delivered as part of SolarisStudio 12.4 (Sun C++ runtime is no longer supported) This is why the flag -std=c++11 must be passed to the link step to

Re: [CMake] Seemingly-unfixable warning about CMP0058 after upgrade to CMake 3.3

On Mon, 2015-09-28 at 11:51 -0400, Brad King wrote: > CMake is warning that it now prefers to generate the Ninja build file > for this case a different way than it did before but is doing it the > old way for compatibility just in case the project needs that to > build. > In this case we know we

[Cmake-commits] CMake branch, next, updated. v3.3.2-3375-g4cae0e8

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

[Cmake-commits] CMake branch, master, updated. v3.3.2-1338-g6a07256

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

[Cmake-commits] CMake branch, master, updated. v3.3.2-1333-gddd082f

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

[Cmake-commits] CMake branch, master, updated. v3.3.2-1357-g130f116

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

[Cmake-commits] CMake branch, master, updated. v3.3.2-1331-g1d11f3c

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

[Cmake-commits] CMake branch, master, updated. v3.3.2-1359-gf23ab1a

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

[Cmake-commits] CMake branch, next, updated. v3.3.2-3383-g6482383

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

[Cmake-commits] CMake branch, next, updated. v3.3.2-3386-g3542ea2

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

[CMake] Associating a single build step with multiple sub-projects in CDash

Dear All, After the suggestion from Bill Hoffman, I played with CDash for a while now. I was able to create a ctest script that would build the packages/subdirectories of my project one by one, and then upload the build/test results to a CDash server. With the results being quite user friendly

[CMake] Custom Module

Hello All, I'm trying to use a custom module, but I can't get cmake to see it. I am on FreeBSD 9.3 (amd64) using cmake-3.3.2. I have read and tried everything I can find on the topic. I have verified the module path via the "MESSAGE" command, but no joy. I have included all relevant

Re: [CMake] Custom Module

On 09/29/2015 12:25 PM, Gerry Weaver wrote: Hello All, I'm trying to use a custom module, but I can't get cmake to see it. I am on FreeBSD 9.3 (amd64) using cmake-3.3.2. I have read and tried everything I can find on the topic. I have verified the module path via the "MESSAGE" command, but no

[Cmake-commits] CMake branch, next, updated. v3.3.2-3388-g23d020c

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

Re: [cmake-developers] cmake fails to identify C and CXX compiler when building universal

On Sep 29, 2015, at 1:54 AM, Nils Gladitz wrote: > Is it possible that beyond setting CMAKE_OSX_ARCHITECTURES the project also > tries to manually add -arch flags to CFLAGS/CXXFLAGS? > > The test binary produced for compiler identification with just > CMAKE_OSX_ARCHITECTURES set is not a fat

[Cmake-commits] CMake branch, master, updated. v3.3.2-1360-g11733d2

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

Re: [CMake] Is the situation with CMake + Eclipse ever going to get any better?

Hi, also Doug, the CDT co-lead, is working on an integration of cmake into cdt. You can find information in the archive of cdt-...@eclipse.org. I think you can expect well integration, similar to clion or qt-developer, with the next major release next year. Roland On Mon, Sep 28, 2015 at 11:00

[cmake-developers] [CMake 0015761]: CMake should provide a variable to get arguments used to configure.

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

[Cmake-commits] CMake branch, next, updated. v3.3.2-3390-g847bd5e

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

[CMake] Is there a variable containing the C flags that would be used to compile something in a directory

There are various variables like CMAKE_C_FLAGS_ that can influence the final flags sent to the compiler. Is there a variable that exists or a function to call to get the final C flags. What I am trying to do is invoke a custom command to run make on an external source tree. This makefile has

Re: [cmake-developers] [PATCH] FindOpenSSL: Imported Targets Release Note

Hi, Brad! 29.09.2015, 22:56, "Brad King" : > On 9/29/2015 1:19 AM, Konstantin Podsvirov wrote: >> reflect this in the release notes. > > Good catch. Applied, thanks: > > Help: Add notes for topic 'FindOpenSSL-imported-targets' >

Re: [cmake-developers] [PATCH] FindOpenSSL: Imported Targets Release Note

On 9/29/2015 1:19 AM, Konstantin Podsvirov wrote: > reflect this in the release notes. Good catch. Applied, thanks: Help: Add notes for topic 'FindOpenSSL-imported-targets' https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0429c384 -Brad -- Powered by www.kitware.com Please keep