[cmake-developers] [CMake][PATCH] Fix support of policy 0065 on AIX

Hi, Attached is a patch to handle correctly policy 0065 and avoid lost of some required link flags (I.e. -bnoipath) Marc 0001-Fix-support-of-policy-0065-on-AIX.patch Description: 0001-Fix-support-of-policy-0065-on-AIX.patch -- Powered by www.kitware.com Please keep messages on-topic and

[CMake] Figuring out in a generator expression whether a name is a target

Dear All, I'm trying to do something a bit more complicated, so please bear with me... In our project we use a special kind of source code generator. Called a "dictionary generator". (https://root.cern.ch/how/how-use-reflex) To simplify the life of our users a bit, we provide a helper function

Re: [CMake] Parallel jobs failed for cmake

Hello Bill, yes, make release is a custom command but that's not important. I do the following: # cd  /home/igor/build_root/release_target #  make release -j5 and again got an error make[4]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule. All Makefiles in 

Re: [cmake-developers] [CMake][PATCH] Fix support of policy 0065 on AIX

On 12/11/2015 05:14 AM, CHEVRIER, Marc wrote: > Attached is a patch to handle correctly policy 0065 Thanks. I found that the same problem exists on HP-UX so I squashed in some changes for that too and applied: AIX,HP-UX: Fix RPATH handling when CMP0065 is set to NEW

[Cmake-commits] CMake branch, master, updated. v3.4.1-684-gc634b5d

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-679-g05d8aed

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-674-g67afa4e

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-686-g198e7df

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-692-g5393087

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-682-g63f2737

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-676-ge240a48

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1703-gff1e328

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-690-g57d5628

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1714-ga2aebd1

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

Re: [CMake] Figuring out in a generator expression whether a name is a target

Hi, Just to let people know how I solved it in the end... After wondering for a little while, I realised that the following should actually work more robustly: # Get the interface directories of the linked libraries: if( ARG_LINK_LIBRARIES ) # First declare an interface library

Re: [cmake-developers] Clarify on the ways to contribute

On 12/11/2015 04:33 AM, Sebastian Schuberth wrote: > while [1] clearly says that "The preferred entry point for new > contributors is the mailing list", obviously also PRs at GitHub are > merged [2]. Also, internally Kitware seems to use Gerrit [3], which > for me would be the preferred place to

Re: [cmake-developers] [Apple/iOS/OS X] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 12/10/2015 09:52 AM, Bartosz Kosiorek wrote: > How it is officialy supported to tell CMake to create subdirectories > inside "Resources" directory? I'm not particularly familiar with this infrastructure myself, but I do not know of any way to define such a layout now. A new interface may have

[Cmake-commits] CMake branch, next, updated. v3.4.1-1718-ga41efac

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

[CMake] Build-time override? (was Re: ExternalProject_Add and inheritance)

On Dec 11, 2015, at 2:44 AM, CHEVRIER, Marc wrote: > With CMake, you can control compilation and link flags with the following > environment variables: > CC: specify C compiler > CFLAGS: C compiler flags > CXX: specify C++ compiler > CXXFLAGS: C++ compiler flags >

Re: [CMake] CPack and PackageMaker

Really ? No one ? :) So it's ok to go ahead and start create a new one ? ;) Rgds, /R Den 2015-12-09 kl. 16:56, skrev Robert Bielik: Mac OSX: Since PackageMaker has been deprecated by Apple, the new tools to use are pkgbuild [1] and productbuild [2]. Simple question: Is there any work

Re: [CMake] CPack and PackageMaker

Hi Robert, I'm afraid that the sad situation is that nobody has done this yet, or is working on it at the moment. I'm absolutely sure that if you can help with this by any amount, that will be most welcome by the CMake developers. It will certainly be most welcome by me, as I've been

Re: [CMake] CPack and PackageMaker

Dear Attila, Ok, been struggling getting an installation package to work with the pkgbuild/productbild tools, so I think I got the gist of what needs to be done, at least to get something going :) Regards /R Den 2015-12-11 kl. 17:47, skrev Attila Krasznahorkay: Hi Robert, I'm afraid that

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

Thanks Clint Unfortunately MACOSX_PACKAGE_LOCATION is not working correctly with RESOURCE property. For every resource which is marked as RESOURCE, will be placed in root "Resources" directory. The CMake code below create following directory structure for OS X: ── mul.framework ├──

Re: [cmake-developers] [PATCH] Imported targets for FindGTest

On 12/10/2015 07:22 PM, rle...@codelibre.net wrote: >> - Add unit test to test imported targets and existing variables > > I should mention that to run the unit test, you must define the GTEST_ROOT > environment variable to point to the gtest build, due to gtest being > annoyingly crippled to be

Re: [cmake-developers] Clarify on the ways to contribute

On Fri, Dec 11, 2015 at 2:35 PM, Brad King wrote: > The mailing list is still the preferred method, but GitHub does not > allow us to turn off PRs so we accept them for one-off simple changes. > For larger changes we usually close the PR with a request to come here.

[cmake-developers] [CMake 0015879]: Wrong configuration name emitted by generator expression

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15879 == Reported By:Javier Martinez Assigned To:

Re: [cmake-developers] set(CACHE) and the local scope

On Fri, Dec 11, 2015 at 22:13:46 +0100, Alexander Neundorf wrote: > On Friday, December 11, 2015 14:44:39 Ben Boeckel wrote: > ... > > Option 3: > > > > set(CACHE) (and any other cache-touching behavior) does *nothing* > > with the cache if a local variable by that name is defined > >

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On Friday, December 11, 2015 08:46:56 PM Bartosz Kosiorek wrote: > Hi > > To enable iOS build, I'm using following settings in CMakeLists.txt: > > > set(APPLE_PLATFORM "iphonesimulator") > set(CMAKE_OSX_SYSROOT > "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platf >

Re: [cmake-developers] set(CACHE) and the local scope

On Friday, December 11, 2015 14:44:39 Ben Boeckel wrote: ... > Option 3: > > set(CACHE) (and any other cache-touching behavior) does *nothing* > with the cache if a local variable by that name is defined just to clarify: and also does nothing to the local variable ? Alex -- Powered

[cmake-developers] parallel install of different cmake versions

For Fedora EPEL we often end up packaging newer versions of cmake as cmakeXY (e.g. cmake34) that can be installed in parallel with the system cmake. This is a fairly invasive process. I'm attaching the current patch I'm working on for this. Is there any interest in cmake itself for supporting

Re: [cmake-developers] [PATCH] Re: Create subdirectories in Resource directory for Frameworks and Application bundle.

Thanks Ruslan. I will update documentation with information about such option (for Xcode generator) Is it possible to mix arm and x86 architectures also for Make generator? I'm very interesting in that bit :-) Best Regards Bartosz From: Ruslan Baratov

Re: [cmake-developers] [PATCH] Re: Create subdirectories in Resource directory for Frameworks and Application bundle.

On 12-Dec-15 07:26, Bartosz Kosiorek wrote: Hi I have updated current documentation with examples, to reflect current status of CMake in OSX/iOS support. Such information is very useful for novice CMake developers, and it saves an hours of digging through mailing list and websites. This is

[Cmake-commits] CMake branch, master, updated. v3.4.1-696-g8ed8c29

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

[cmake-developers] [PATCH] Re: Create subdirectories in Resource directory for Frameworks and Application bundle.

Hi I have updated current documentation with examples, to reflect current status of CMake in OSX/iOS support. Such information is very useful for novice CMake developers, and it saves an hours of digging through mailing list and websites. Best Regards Bartosz

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 12-Dec-15 10:08, Bartosz Kosiorek wrote: Thanks Ruslan. I would like to create instruction which is universal for all generators. I think it's not possible. E.g. IOS_INSTALL_COMBINED will work only for Xcode. Currently we would like to support both Make/Ninja and Xcode generators,

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 12-Dec-15 03:46, Bartosz Kosiorek wrote: Hi To enable iOS build, I'm using following settings in CMakeLists.txt: set(APPLE_PLATFORM "iphonesimulator") I think this one not needed. Can't find any place where it parsed. set(CMAKE_OSX_SYSROOT

Re: [CMake] error while loading shared libraries: libLLAPI.so: cannot open shared object file: No such file or directory

Hi Decker, Thank you for reply ! export LD_LIBRARY_PATH works but how to achieve by cmake or what are proper settings for RPATH? I tried settings from "Always full RPATH" at https://cmake.org/Wiki/CMake_RPATH_handling , but got same error. >From this link , if RPATH is not set then linker

Re: [CMake] ExternalProject_Add and inheritance

Hello Marc, thank you very much for your answer! I am not sure to understand how to overcome my problem with these variables. I can explain my problem further. I have a toy example of the problem which contains: - a call to ExternalProject_Add to install boost and yaml-ccp (the latter

Re: [CMake] Adding all object files as target

On 11.12.2015 20:27, Sachin Gaikwad wrote: In GNU make, I can easily do this: "make foo.o" if I have foo.cc file to build and this will only compile foo.cc and create foo.o. This behavior is default one i.e. all object files are added as targets in Makefile. How do I get same behavior with

Re: [cmake-developers] set(CACHE) and the local scope

On Thu, Dec 10, 2015 at 08:50:10 -0500, Brad King wrote: > BUG: change in how set cache overrides local definitions. Should mainly be a > NOP change for most cases > https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f52d37c2 So Brad and I discussed today the reasons behind this change. Here

Re: [CMake] CPack and PackageMaker

If you are interested, attached is some code I started a couple years ago but never finished, nor did I do much testing. Perhaps that'll help, or maybe you'll find a better way. Clint - On Dec 11, 2015, at 9:50 AM, Robert Bielik robert.bie...@dirac.se wrote: > Dear Attila, > > Ok, been

Re: [CMake] Visual Studio 10 and wxWidgets

Hi all. I solved my problem with a custom script. I attach it to this message. The script is very very poor, but for my purpouse it works. The script should be simply included MZ On Thu, Dec 10, 2015 at 4:23 PM, Mauro Ziliani wrote: > Hi all. > I'm in trouble

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On Friday, December 11, 2015 05:01:41 PM Bartosz Kosiorek wrote: > Thanks Clint > > Unfortunately MACOSX_PACKAGE_LOCATION is not working correctly with RESOURCE > property. For every resource which is marked as RESOURCE, will be placed in > root "Resources" directory. > > The CMake code below

[Cmake-commits] CMake branch, next, updated. v3.4.1-1701-g2e739f3

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

[Cmake-commits] CMake branch, master, updated. v3.4.1-695-ga680211

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

[Cmake-commits] CMake branch, next, updated. v3.4.1-1716-gf970a8a

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

[cmake-developers] [CMake 0015878]: CMake 3.4.1 can not find standalone Windows SDK 8.1

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15878 == Reported By:Dmitry Sokolov Assigned To:

Re: [CMake] Parallel jobs failed for cmake

On 12/11/2015 7:24 AM, Igor Sobinov wrote: Hello Bill, yes, make release is a custom command but that's not important. I do the following: # cd /home/igor/build_root/release_target # make release -j5 Yes, it is important, it is the reason it is not working. The custom command needs to use

Re: [CMake] CPack and PackageMaker

Dear Clint, Thank you! Will certainly start with that as a base :) Regards /R -- Ursprungligt meddelande-- Från: Datum: fre, 11 dec 2015 20:12 Till: Robert Bielik; Kopia: Attila Krasznahorkay;cmake; Ämne:Re: [CMake] CPack and PackageMaker If you are interested, attached is some code I

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

- On Dec 11, 2015, at 11:44 AM, Bartosz Kosiorek wrote: > Hi > Because there is difference between OS X and iOS Bundles directory structure > (see: Apple specification >

[CMake] Adding all object files as target

Hi all, In GNU make, I can easily do this: "make foo.o" if I have foo.cc file to build and this will only compile foo.cc and create foo.o. This behavior is default one i.e. all object files are added as targets in Makefile. How do I get same behavior with cmake? Sachin -- Powered by

Re: [cmake-developers] set(CACHE) and the local scope

I like the sounds of both Option 1, and Option 2. I feel Option 3 is really bad. We should remember that people understand/are taught the current CMake behavior of local variables being preferred over cache variables. If we move to Option 3, that rule becomes "local variables are preferred over

Re: [CMake] Visual Studio 10 and wxWidgets

I miss some lines. This is that works On Fri, Dec 11, 2015 at 7:06 PM, Mauro Ziliani wrote: > Hi all. > I solved my problem with a custom script. > > I attach it to this message. > The script is very very poor, but for my purpouse it works. > > The script should be

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

Hi Because there is difference between OS X and iOS Bundles directory structure (see: Apple specification https://developer.apple.com/library/mac/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html), in trunk (In CMake 3.5) RESOURCE property create corresponding