Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TIMOB-24057] Always build pods for all archs #123

Merged
merged 1 commit into from Mar 2, 2017

Conversation

janvennemann
Copy link
Contributor

JIRA: https://jira.appcelerator.org/browse/TIMOB-24057

Building the pods for a specific arch and the app for all available archs was causing issues during linking. The ONLY_ACTIVE_ARCH=NO flag is set in the app's Xcode project here so we need to do the same for pods.

@@ -540,13 +540,9 @@ function runCocoaPodsBuild (basedir, builder, callback) {
'-alltargets',
'IPHONEOS_DEPLOYMENT_TARGET=' + minSDKVersion,
'-sdk', sdk,
'SYMROOT=' + productsDirectory
'SYMROOT=' + productsDirectory,
'ONLY_ACTIVE_ARCH=NO'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the native behavior? I feel like this could cause problems in AppStore submissions having a fat binary.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This corresponds to the Xcode setting "Build Active Architecture Only" which is set to No by default for the Release configuration in Xcode. So this is the default behavior for AppStore builds. Also as mentioned in my PR descriptions we also do this for the App build anyway. Building only the active architecture speeds up the build process and is used by default in the Xcode Debug configuration. Not sure why we always have this setting to No thought.

@hansemannn
Copy link
Contributor

Approved!

@hansemannn hansemannn merged commit b0bce20 into tidev:master Mar 2, 2017
@janvennemann janvennemann deleted the TIMOB-24057-fix branch March 23, 2017 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants