[Cmake-commits] CMake branch, master, updated. v3.5.2-813-g34d07d7

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

[cmake-developers] [CMake 0016134]: CMake crashes at generation stage

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=16134 == Reported By:Daniel Levin Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.2-819-gddd74ff

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

[CMake] CMake searching for shared libraries in invalid paths

Hi cmake users,     Reposting question from stackoverflow (http://stackoverflow.com/questions/37449511/cmake-searching-for-shared-libraries-in-invalid-paths) since I didn't get a good answer there: I noticed that the cmake generation step in my project was taking a long time and so I ran cmake

Re: [CMake] add_custom_command, POST_BUILD

Vladimir Chebotarev writes: > Hi there. > > At the moment one can add a command executing after a build of a target > using: > add_custom_command(... POST_BUILD...) > > However if the command have a dependencies which build after the target, > there is practically

Re: [cmake-developers] Topic "add-opencl-imported-target" good to merge?

Hi Brad, done - I had to squash and force push once more, because I used the wrong author in the first commit. Everything is now in one commit here: https://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=e95b62110715c06fb76b57fdfb13ea493a94c0c4 Thanks for the timely feedback! Cheers,

Re: [cmake-developers] Topic "add-opencl-imported-target" good to merge?

On 06/01/2016 02:15 PM, Matthäus G. Chajdas wrote: > Hopefully done The revised history looks good. The change itself looks good. Please also add a `Help/release/dev/FindOpenCL-imported-target.rst` file with a release note for the feature. Look at other files in that directory for a sample.

Re: [cmake-developers] Topic "add-opencl-imported-target" good to merge?

Hopefully done - I'm not the biggest git expert but the history looks like I'd expect it to look like :) Cheers, Matthäus Am 01.06.2016 um 19:57 schrieb Brad King: > On 06/01/2016 01:53 PM, Matthäus G. Chajdas wrote: >> updated to latest master and pushed again (I merged latest master into >>

Re: [cmake-developers] [PATCH] fix issue #0016076 Add a --bindir option to bootstrap and use it to install cmake in custom directory

On 05/30/2016 10:50 AM, BUNEL Nicolas wrote: > Here, the new patch Thanks. I've applied the patches, squashed, and made some minor tweaks. It has been merged to 'next' for testing: Add option to control 'bin' directory of CMake's own installation (#16076)

Re: [CMake] No debugging symbols found when using -DCMAKE_BUILD_TYPE=Debug

I tried it out just now. I pulled and installed a couple 5.x packages from the Arch archive: https://archive.archlinux.org/packages/l/ The packages: gcc-libs-multilib-5.3.0-4-x86_64.pkg.tar.xz gcc-multilib-5.3.0-4-x86_64.pkg.tar.xz lib32-gcc-libs-5.3.0-4-x86_64.p The downgrade didn't change

Re: [cmake-developers] Topic "add-opencl-imported-target" good to merge?

On 06/01/2016 01:53 PM, Matthäus G. Chajdas wrote: > updated to latest master and pushed again (I merged latest master into > this - is that fine or does it have to be a rebase? In that case I'll redo.) Please rebase and force push. Thanks, -Brad -- Powered by www.kitware.com Please keep

Re: [cmake-developers] Topic "add-opencl-imported-target" good to merge?

Hi Brad, updated to latest master and pushed again (I merged latest master into this - is that fine or does it have to be a rebase? In that case I'll redo.) Cheers, Matthäus Am 01.06.2016 um 17:18 schrieb Brad King: > On 05/31/2016 03:17 PM, Matthäus G. Chajdas wrote: >> I've just pushed

[Cmake-commits] CMake branch, next, updated. v3.5.2-817-g9f6fe2f

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

Re: [CMake] How to use CMAKE_MFC_FLAG for only one on executables?

Or just isolate it into its own CMakeLists.txt file in a sub-directory? On Wed, Jun 1, 2016 at 8:34 AM, Nicholas Braden wrote: > Have you tried unsetting it after adding the executable in question? > If that doesn't work, is it possible to make the MFX executable be

[CMake] RPATH of imported targets

Hi Folks, I'm linking a target against libraries from an imported package. The resulting linker invocation then will link against the libs using the full path, but it will not set the RPATH accordingly. How to I enable RPATH? I suspect the reason is, that, in the package's Exports.cmake, it sets

Re: [CMake] No debugging symbols found when using -DCMAKE_BUILD_TYPE=Debug

Interesting. It seems CMake is having trouble identifying GCC in 6.1.1. Do you have a 5.x compiler available? If so does it work with that? That would help narrow it down to a gcc6 issue vs something about how Manjaro packages compilers. - Chuck On Wed, Jun 1, 2016 at 10:49 AM, Esch Nigma

[CMake] add_custom_command, POST_BUILD

Hi there. At the moment one can add a command executing after a build of a target using: add_custom_command(... POST_BUILD...) However if the command have a dependencies which build after the target, there is practically no way to specify it. Simple case: we have a library and tests for it.

[CMake] Running OSX Bundle via open after creation with CMake/CPack

Dear all, I have generated a bundle for MacOS as follows: if(APPLE) set(OS_BUNDLE MACOSX_BUNDLE) elseif(WIN32) set(OS_BUNDLE WIN32) endif() include_directories(${CMAKE_CURRENT_BINARY_DIR}) add_executable(FADTTSter ${OS_BUNDLE} ${FADTTS_src} )

Re: [cmake-developers] Some trivial patches

On 06/01/2016 05:04 AM, Tobias Hunger wrote: > Attached you will find a couple of really small changes that add const to a > method and fix a couple of typos in comments. Trivial stuff. Thanks. I've applied the changes: cmSearchPath: Fix typo in comment

Re: [cmake-developers] CMake execute_process/signal_handler on Unix

On 06/01/2016 09:04 AM, Yordanov, Dimitar wrote: > I'm looking into an issue with a CMake build on Linux hanging in a > select syscall, when using EXECUTE_PROCESS without any additional > arguments. The subprocess executed is "chmod". The child finishes and > is marked as a zombie, but CMake did

Re: [cmake-developers] Topic "add-opencl-imported-target" good to merge?

On 05/31/2016 03:17 PM, Matthäus G. Chajdas wrote: > I've just pushed "add-opencl-imported-target" which adds an imported > target to FindOpenCL. The whole change is rather small: > > https://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=6c53137a19e482140db3dc97b626af38348f2c71 > > Good to

Re: [cmake-developers] CMake 3.6 feature freeze on 2016-06-01

On 05/27/2016 09:02 AM, Brad King wrote: > I'll announce when post-3.6 development in 'next' is open. I've branched 'release' for 3.6. The repository is now open for post-3.6 development. Please rebase any open topics on 'master' before merging to 'next'. > * Documentation updates > *

[Cmake-commits] CMake branch, next, updated. v3.5.2-815-g36ec325

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-813-ge3d868a

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 discards afce47035ef92e0b9b97f6bd2ac3ac395669201c (commit) discards

Re: [CMake] C header file cross dependency

> > Could you provide a working, stripped down example to show the problem > provided via github (in an example repo). > I've added a simple test project to https://github.com/martinwag/test_cmake/tree/master Note that this example does not need cross gcc for ARM. It doesn't implement any

[Cmake-commits] CMake branch, next, updated. v3.5.2-1643-gafce470

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-808-g9d81f1b

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

Re: [CMake] No debugging symbols found when using -DCMAKE_BUILD_TYPE=Debug

The standard choice is c++ [eschnigma@manjaro ~]$ c++ --version c++ (GCC) 6.1.1 20160501 Copyright (C) 2016 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR

[Cmake-commits] CMake branch, next, updated. v3.5.2-1641-gf258626

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

Re: [CMake] No debugging symbols found when using -DCMAKE_BUILD_TYPE=Debug

> >[eschnigma@manjaro build]$ cmake .. -DCMAKE_BUILD_TYPE:STRING="Debug" > -- The C compiler identification is unknown > -- The CXX compiler identification is unknown > This is definitely the reason for no debug symbols. If the compiler is unknown then CMake won't know the right flags to

[cmake-developers] CMake execute_process/signal_handler on Unix

Hey, I'm looking into an issue with a CMake build on Linux hanging in a select syscall, when using EXECUTE_PROCESS without any additional arguments. The subprocess executed is "chmod". The child finishes and is marked as a zombie, but CMake did not realize that. The only descriptors left open

[Cmake-commits] CMake branch, next, updated. v3.5.2-1638-g5e4ac45

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-805-g62adedb

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1636-g067dd85

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-803-g4062d6d

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-800-g7642dde

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1632-ga4e984d

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1629-gb8560be

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

[CMake] No debugging symbols found when using -DCMAKE_BUILD_TYPE=Debug

Hello all, I just registered to this mailing list, my apologies if this was already discussed. I'm experiencing an issue where I'm unable to debug my code when the project is configured with CMake. When running gdb on the final binary, it mentions that no debugging symbols are found. I tried

Re: [CMake] CMake+QT always failed for the first build, and succeeded for second build or later.

01.06.2016, 14:09, "Jakob van Bethlehem" : >> Hey, that was the LTS release until 1 or 2 month ago! > > Oops, you're right, my mistake. Somewhere in the back of my head was that the > 4-series was in the 4.12.x or so version, not sure where that came from. KDE 4 I

Re: [CMake] CMake+QT always failed for the first build, and succeeded for second build or later.

> Hey, that was the LTS release until 1 or 2 month ago! Oops, you're right, my mistake. Somewhere in the back of my head was that the 4-series was in the 4.12.x or so version, not sure where that came from. I haven't worked with Qt4 ever, but have become extremely experienced with Qt5 from Qt 5.4

[CMake] Unit Testing for CMake Scripts

I was about to ask the list, but some googling lead me to this: https://github.com/polysquare/cmake-unit I am not the developer, but he doesn't appear to be on here so I thought I should share. This looks incredibly useful -- Powered by www.kitware.com Please keep messages on-topic and check

[CMake] How to use CMAKE_MFC_FLAG for only one on executables?

Hello All, I want to use CMake to manage my MFC projects, and I added the following code: set( CMAKE_MFC_FLAG 2) add_executable(MFCDemo WIN32 ${MFC_RESOURCE_FILES} ${MFC_HEADER_FILES} ${MFC_SOURCE_FILES} ) target_compile_definitions(MFCDemo

[CMake] CMake error output and .vcxproj.filters files.

Hi, We've recently switched to using cmake and I've got some 'issues'. We use Windows with Visual Studio and MSVC (Visual Studio 10 2010 Win64 generator). 1. In cmake error output the output format is not compatible with VS so when the VS console displays it, you cannot click on the

[cmake-developers] Some trivial patches

Hi CMake Developers! Attached you will find a couple of really small changes that add const to a method and fix a couple of typos in comments. Trivial stuff. This is mostly to figure out how to contribute code:-) Is this the preferred way you want your patches? Or do I need to inline them

Re: [CMake] CMake+QT always failed for the first build, and succeeded for second build or later.

Am 1. Juni 2016 09:26:18 MESZ, schrieb Jakob van Bethlehem : >That is what he said, but it seems to be a typo, because the >CMakeLists.txt >file clearly states 'set(QT_DIR >${CMAKE_CURRENT_SOURCE_DIR}/ThirdParty/Qt/4.8.6)' Ok, I overlooked that one... >- still a

Re: [CMake] CMake+QT always failed for the first build, and succeeded for second build or later.

That is what he said, but it seems to be a typo, because the CMakeLists.txt file clearly states 'set(QT_DIR ${CMAKE_CURRENT_SOURCE_DIR}/ThirdParty/Qt/4.8.6)' - still a stone-age version of Qt actually :( Sincerely, Jakob van Bethlehem On Wed, Jun 1, 2016 at 9:09 AM, Hendrik Sattler

Re: [CMake] CMake+QT always failed for the first build, and succeeded for second build or later.

Am 1. Juni 2016 09:02:41 MESZ, schrieb Jakob van Bethlehem : >Hej, > >Some things that come to mind: >* You're generating files *inside* the source tree - you're not >supposed to >do that >* Why do you want to have a special Qt_tmp directory? I don't see the >benefit,

Re: [CMake] CMake+QT always failed for the first build, and succeeded for second build or later.

Hej, Some things that come to mind: * You're generating files *inside* the source tree - you're not supposed to do that * Why do you want to have a special Qt_tmp directory? I don't see the benefit, and without that requirement you can simply use the qt4_wrap_cpp macro explicitly and you still