MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012451CMakeCMakepublic2011-09-09 09:322013-12-02 08:51
ReporterDruon 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOSOS Version
Product VersionCMake 2.8.5 
Target VersionFixed in Version 
Summary0012451: MACOSX_BUNDLE path problem when building for iOS with Xcode
DescriptionI'm not sure if building for iOS is officially supported, but here goes...

When building for iOS with MACOSX_BUNDLE specified on the target, this generates an XCODE_DEPEND_HELPER.make with Foo.app/Contents/MacOS/foo paths in it. However for iOS builds, Xcode places the executable 'foo' in Foo.app/foo.

I couldn't find an option to change this behaviour.

The result is that dependency checking does not work and a clean build is required every time the app is compiled.
Steps To ReproduceSet up an iOS project by setting CMAKE_OSX_SYSROOT, CMAKE_OSX_ARCHITECTURES and MACOSX_BUNDLE_GUI_IDENTIFIER. Specify MACOSX_BUNDLE for the target executable. Make a change in a dependency and rebuild the app. The app will not be updated.
Additional Information
TagsNo tags attached.
Relationships
duplicate of 0014258closed  MACOSX_BUNDLE path problem when building for iOS with Xcode 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-09-09 09:32DruonNew Issue
2011-09-12 10:43David ColeAssigned To => David Cole
2011-09-12 10:43David ColeStatusnew => assigned
2012-08-13 15:12David ColeStatusassigned => backlog
2012-08-13 15:12David ColeNote Added: 0030604
2012-08-13 15:18David ColeAssigned ToDavid Cole =>
2013-07-01 15:44Brad KingRelationship addedduplicate of 0014258
2013-07-01 15:45Brad KingNote Added: 0033442
2013-07-01 15:45Brad KingStatusbacklog => resolved
2013-07-01 15:45Brad KingResolutionopen => duplicate
2013-12-02 08:51Robert MaynardNote Added: 0034627
2013-12-02 08:51Robert MaynardStatusresolved => closed

Notes
(0030604)
David Cole   
2012-08-13 15:12   
Sending old, not-recently-updated issues to the backlog.

(The age of the bug alone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0033442)
Brad King   
2013-07-01 15:45   
Resolving as duplicate of 0014258. Even though this one came first, that one has a proposed patch.
(0034627)
Robert Maynard   
2013-12-02 08:51   
Closing resolved issues that have not been updated in more than 4 months.