[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

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

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

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-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-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-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-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-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 >

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-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