[TIMOB-10366] iOS: add the ability to set IPHONEOS_DEPLOYMENT_TARGET from tiapp.xml
GitHub Issue | n/a |
---|---|
Type | New Feature |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2013-06-25T16:31:57.000+0000 |
Affected Version/s | Release 2.1.1, Release 3.0.0 |
Fix Version/s | n/a |
Components | iOS |
Labels | core |
Reporter | Paul Mietz Egli |
Assignee | Ingo Muschenetz |
Created | 2012-08-08T09:42:26.000+0000 |
Updated | 2017-03-22T20:43:07.000+0000 |
Description
The mobilesdk/osx/iphone/builder.py script has a hardcoded value for the minimum iOS deployment target (IPHONEOS_DEPLOYMENT_TARGET) set to "4.0". This is a reasonable default, but there are times when a developer needs to specify a higher version. For example, in my own case, I use a module that requires iOS 5.0 and above, so my application needs to be 5.0+ or I get linker errors.
The workaround is to open the app's project file in XCode and change the setting. This is not ideal for less-experienced developers, especially since it has to be done each time the build directory is removed. It would be better if we could specify the minimum OS version in tiapp.xml.
This would also help solve compiling issues when deploying to a device, since Titanium automatically compiles a new Xcode project when invoked. Currently, you have to modify the build.py file and manually force IPHONEOS_DEPLOYMENT_TARGET and armv6,armv7 settings.
@Terry - We recently improved this use case as part of TIMOB-2999 implementation. Please take a look at this ticket and see if the latest 2.1.2 or master build helps you with your application.
Hi, Same request for me. Because of this problem, I can't automatize easily my builds.
[~romain.salles] Have you looked at the fixes available in TIMOB-2999?
No, I hadn't seen this fix and indeed, it solve the issue. Thanks !
It appears that the linked issue addresses the need (for now) for this feature. Marking as a duplicate. If there are related edge cases not solved by TIMOB-2999, please let us know.
Closing ticket as duplicate of the ticket that is mentioned above and has since been closed.