Re: [CMake] works when I build using XCode, but not with CMake makefile

- On Sep 7, 2016, at 12:52 PM, Cotton Candy wrote: > Here is the output from otool -L on skedmo-solver that you requested: > skedmo-solver: > libmysqlclient.18.dylib (compatibility version 18.0.0, current version 18.0.0) > /usr/lib/libSystem.B.dylib

[CMake] cmake source tree pollution ?

Hi, I have started to use CMake for my software. I build in a separate directory using : $> cmake -G "Unix Makefiles" Everything is built correctly and the software works fine. However all of my source code directories get polluted. Into each source directory, a new Makefile is created. All

Re: [CMake] cmake source tree pollution ?

This kinda’ sounds like you are doing an in-source build. Are you certain that your currrent/working directory is different from your source tree root when you run cmake? The typical way of doing this is just to make a subdirectory of your source root: mkdir my_build cd my_build cmake

Re: [CMake] cmake source tree pollution ?

On 09/09/2016 05:45 PM, Michael Ellery wrote: This kinda’ sounds like you are doing an in-source build. Are you certain that your currrent/working directory is different from your source tree root when you run cmake? The typical way of doing this is just to make a subdirectory of your source

Re: [CMake] cmake source tree pollution ?

Looks like https://github.com/redguardtoo/cpputils-cmake might be involved... On Fri, Sep 9, 2016 at 5:04 PM, Vania Joloboff wrote: > On 09/09/2016 05:45 PM, Michael Ellery wrote: >> >> This kinda’ sounds like you are doing an in-source build. Are you certain >> that

Re: [CMake] cmake source tree pollution ?

On Fri, Sep 9, 2016 at 4:45 PM, Michael Ellery wrote: > This kinda’ sounds like you are doing an in-source build. Are you certain > that your currrent/working directory is different from your source tree root > when you run cmake? The typical way of doing this is just to

[CMake] Problem with MSVC compiler flags

Hi there, I'm using CMake 3.6.2 to generate solution/project files for Visual Studio 14 (2015) Win64 on Windows 10. The problem is that "/Zc:inline" and "/Zc:rvalueCast" do not set properly (but all other compiler flags do); Both flags show up in the 'Additional Options' box in 'Configuration

Re: [CMake] Windows path too long

Hi Mike, Thanks, I didn’t know that. Well... gonna have to take the plunge some day, might aswell be now... :) Regards /R From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of mike lojkovic Sent: den 8 september 2016 15:58 To: Cmake@cmake.org Subject: Re: [CMake] Windows path too long

[CMake] Toolchain rpath libraries

Dear all, I created toolchain file: set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSROOT "/srv/chroots/centos6-amd64") set(CMAKE_C_FLAGS "-gcc-name=${CMAKE_SYSROOT}/usr/bin/gcc -L${CMAKE_SYSROOT}/usr/lib64") set(CMAKE_CXX_FLAGS "-gxx-name=${CMAKE_SYSROOT}/usr/bin/g++ -L${CMAKE_SYSROOT}/usr/lib64")

[CMake] Clang/C2 Visual Studio generator non-functional with cmake v3.6.1 and v3.6.2

Hi everyone. I've been working on this issue for almost 2 weeks now, originally with cmake v3.6.1 and now with cmake v3.6.2. I have looked far and wide for help, but with Clang/C2 support under Visual Studio being experimental, I haven't been able to find much. The problem is that when I

[Cmake-commits] CMake branch, next, updated. v3.6.2-1890-gfc294ee

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1892-g2d65227

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1905-g1ff6b5b

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1894-g4ca4ed5

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

Re: [cmake-developers] [patch] FreeBSD build fix

On 09/08/2016 05:06 PM, Roger Leigh wrote: > With FreeBSD 11, I was getting a link failure due to missing kvm symbols > in Utilities/cmlibuv. > > The fix is a trivial addition. It's added unconditionally; I checked > for its presence in FreeBSD 11, 10 and 9. Branch: freebsd-kvm-link Thanks.

Re: [cmake-developers] [patch] BZip2 imported targets

On 09/08/2016 05:03 PM, Roger Leigh wrote: > Adds BZip2::BZip2 imported target and documentation, along with unit > test which may be enabled with the CMake_TEST_FindBZip2 option. Derived > from the existing code in FindZLib. Looks good, thanks. I revised the topic with some minor tweaks.

[Cmake-commits] CMake branch, next, updated. v3.6.2-1896-gc0f6295

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1914-gafee770

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1898-ge238ac6

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-894-gc40cbcc

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-883-g188a42a

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-892-gc580227

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-900-gd5e4cdc

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1907-gccc35f7

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-889-g46cf415

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-898-g2572b82

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-887-g7c05f13

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1910-g80b043a

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1918-ge0aa392

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1916-g2758bf0

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

Re: [cmake-developers] Android Support

Currently nightly builds are tagged 3.6.2. Are there no nightly builds for 3.7 or am I missing something? On Fri, Aug 12, 2016 at 10:26 AM, Robert Goulet wrote: > That's super awesome Brad! > > Looking forward to try this out! > > -Original Message- > From:

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 09/06/2016 01:26 PM, Stuermer, Michael SP/HZA-ZSEP wrote: Here it is. The patch only seems to allow patching Features generated for components but not Features generated for component groups. Is that intentional or an oversight? I think we should allow patching for both. Nils --

Re: [cmake-developers] [Patch 5/5] Improved WIX support

> -Original Message- > From: Nils Gladitz [mailto:nilsglad...@gmail.com] > Sent: Friday, September 09, 2016 8:33 AM > To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers > Subject: Re: [cmake-developers] [Patch 5/5] Improved WIX support > > On 09/06/2016 01:26 PM, Stuermer, Michael

[Cmake-commits] CMake branch, next, updated. v3.6.2-1884-g740f009

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1886-g804588e

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1888-g9753c73

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

Re: [cmake-developers] [Patch 5/5] Improved WIX support

On 09/09/2016 10:54 AM, Stuermer, Michael SP/HZA-ZSEP wrote: The details you miss if you are not using the features ... thanks for the hint, here is corrected patch. Michael Thanks. I merged to "next" with small changes. Nils -- Powered by www.kitware.com Please keep messages on-topic

[Cmake-commits] CMake branch, next, updated. v3.6.2-1922-gf8fc47d

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-901-gd90432c

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