Re: [cmake-developers] GCC HPPA linker errors

While the dashboard may be red today from the curl update, it looks like this branch has cleared the linker issue and now pioneer and voyager are happily green together. On Nov 6, 2014 7:24 PM, David Cole via cmake-developers cmake-developers@cmake.org wrote: These are the earliest CDash results

Re: [cmake-developers] CMake 3.1 regression with incremental builds ?

I just looked at the diff, not the surrounding code, so forgive the question if it's obvious when inspecting the code.. but here's a question about your change before we push it into RC 2: Is objectSources guaranteed to contain the same set of objects as mapping? If so, I wonder why the code

Re: [cmake-developers] CMake 3.1 regression with incremental builds ?

On Thu, Nov 6, 2014 at 11:09 PM, Clinton Stimpson wrote: I've put in a fix for this. 580b668d genex: Preserve order while evaluating TARGET_OBJECTS Thanks. I bisected it down to cmTarget: Allow any generator expression in SOURCES property.

[cmake-developers] pause on new topics, please

Hi Folks, Please refrain from adding new topics to 'next' until the current dashboard trouble has been resolved. Of course any dashboard fixes to current topics are still welcome, or new topics specifically fixing a 3.1 regression. I need to resolve the issues with the curl update and also get

[cmake-developers] [CMake 0015236]: CPACK_COMPONENT_GROUP can de-select required children

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15236 == Reported By:Richard Ulrich Assigned To:

Re: [cmake-developers] CMake 3.1 regression with incremental builds ?

On Fri, Nov 07, 2014 at 09:51:39 -0500, Brad King wrote: On Thu, Nov 6, 2014 at 11:09 PM, Clinton Stimpson wrote: isn't the GetOrCreateSourceFile call superfluous if you have a pointer to the source file object in the iterator...? IIUC that is to create a cmSourceFile entry for the object

Re: [cmake-developers] CMake 3.1 regression with incremental builds ?

On 11/07/2014 11:43 AM, Ben Boeckel wrote: IIUC that is to create a cmSourceFile entry for the object file corresponding to the source file. They are different entries. Do we know the source file doesn't exist at this point? If so, CreateSourceFile would be better. My take: Normally it

Re: [cmake-developers] CMake 3.1 regression with incremental builds ?

On Fri, Nov 07, 2014 at 11:52:45 -0500, Brad King wrote: OTOH, it is possible that application code tries to set a property on an object file ahead of time. AFAIK, CMake doesn't expose where it stores these files and has always treated it as an internal detail. Is this something we promise

Re: [cmake-developers] CMake 3.1 regression with incremental builds ?

On 11/07/2014 12:19 PM, Ben Boeckel wrote: On Fri, Nov 07, 2014 at 11:52:45 -0500, Brad King wrote: OTOH, it is possible that application code tries to set a property on an object file ahead of time. AFAIK, CMake doesn't expose where it stores these files and has always treated it as an

[cmake-developers] [CMake 0015237]: No CMAKE_C_COMPILER could be found (3.1.0-rc1 regression)

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15237 == Reported By:Ruslan Baratov Assigned To:

[CMake] CMAKE_ROOT env variable not honored anymore

Hi all, we used CMake 2.8 so far and had used the environment variable CMAKE_ROOT to tell the cmake binary, where to find its Modules etc. directories. We used this in a multiplatform context to store the architecture-independent files of CMake only once. It seems, that CMake 3.0 does not

[CMake] Calling of find_package from function

Hello! I'm writing a wrapper around find_package so I call find_package from my own function. I found it's near impossible because all the variables set by finders remain in the scope of my wrapper function, rather than in the caller's scope. Is there any way to force find_package to set all

Re: [CMake] Calling of find_package from function

Hi Andrey. As a workaround, you could make the calling context a macro instead of a function. Macros don't introduce variable scope. Petr On Fri, Nov 7, 2014 at 4:23 PM, Andrey Upadyshev oli...@gmail.com wrote: Hello! I'm writing a wrapper around find_package so I call find_package from my

Re: [CMake] Calling of find_package from function

Thank you for advice Petr! I will go with this solution if can't find another one. CMake macroses are slightly weird so I'm trying to avoid them :) On Fri, Nov 7, 2014 at 4:39 PM, Petr Kmoch petr.km...@gmail.com wrote: Hi Andrey. As a workaround, you could make the calling context a macro

Re: [CMake] Calling of find_package from function

I've solved my problem with special macroses. First saves all non-cache variables (have to be called at the beginning of the function) and second one propagates all the changed/added variables to the parent scope (have to be called of at end of the function). If someone interested in code, it's

[CMake] CPack: .desktop files with tar.gz maker?

I have a build and packaging system where I can distribute (mostly) standalone apps for Linux desktop. I am using the default CPack installer which creates .tar.gz, .Z, and .sh files. I like this opposed to the .deb/.rpm package systems because users don't need root access to install/use my stuff

Re: [CMake] CPack: .desktop files with tar.gz maker?

On Friday, November 07, 2014 03:50:32 PM Eric Wing wrote: I have a build and packaging system where I can distribute (mostly) standalone apps for Linux desktop. I am using the default CPack installer which creates .tar.gz, .Z, and .sh files. I like this opposed to the .deb/.rpm package

Re: [CMake] Using CMake to build an Emscripten output?

Hi Eric, While I don't have yet an example dealing with assets, here is an example of project using emscripten. See https://github.com/commontk/dcmjs May be you could re-use the macro em_add_tracked_link_flag like it is done for --pre-js, etc See [1] Hth Jc [1]

Re: [CMake] Support OpenBLAS in FindBLAS module

Hi Xianyi, By updating FindBlas.cmake, did you mean that the module should try to find OpenBlas if it could not find any other implementation ? Or do you want to provide an easy for developer to import the OpenBlas library in their project ? Either way, as described by Eike, the first step would

Re: [CMake] ExternalProjectDependency (artichoke) and ctest

Hi Jameson, Good to know you are using Artichoke. As you described Artichoke provides ExternalProjectDependency, a CMake module extending the capabilities of ExternalProject. It could eventually by integrated into CMake once the API is stable, the documentation is complete it is more widely

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-409-g015bbfb

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-407-g137dc18

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-411-g578948e

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-159-gbd0bc87

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-414-gad8accd

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-163-gf49e4c6

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-419-g0950408

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

[Cmake-commits] CMake branch, release, updated. v3.1.0-rc1-24-gb71399a

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-421-g79e64b7

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-423-gc935e3e

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-425-gb6fbe7e

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-167-g70105fa

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-165-g0ef2d5f

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-428-g624f2a4

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

[Cmake-commits] CMake branch, release, updated. v3.1.0-rc1-28-g3dfc856

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-170-g8b14b4e

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-432-g019c552

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-434-gd835b5c

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-172-g0f836cb

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

[Cmake-commits] CMake branch, release, updated. v3.1.0-rc1-30-g06c3b7a

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-174-gac4bb00

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

[Cmake-commits] CMake branch, next, updated. v3.1.0-rc1-438-ge0f9c5a

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

[Cmake-commits] CMake branch, master, updated. v3.1.0-rc1-175-g5bdb9b6

20141107) +set(CMake_VERSION_PATCH 20141108) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake