webrtc/build/ios/SDK/README - Issue 1829783003: Build dynamic framework with podspec for Objective-C API.

Side by Side Diff: webrtc/build/ios/SDK/README

Issue 1829783003: Build dynamic framework with podspec for Objective-C API. (Closed) Base URL: https://chromium.googlesource.com/external/webrtc.git@master

Patch Set: Add basic README; address other comments Created 4 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 We want to generate a dynamic framework for a CocoaPod. Unfortunately, using gyp -xcode generation for a framework currently presents some issues. To get around those issues, we chose to create a project with Xcode for building the framework directly.
	tkchin_webrtc 2016/03/25 17:46:07 Do we need to say anything about stripping simulat Do we need to say anything about stripping simulator slices before app store submission, or do pods do that now? tkchin_webrtc 2016/03/25 17:46:07 100 char? Thanks :) 100 char? Thanks :) hjon_webrtc 2016/03/25 21:17:44 As far as I can tell, CocoaPods takes care of that Show quoted text On 2016/03/25 17:46:07, tkchin_webrtc wrote: > Do we need to say anything about stripping simulator slices before app store > submission, or do pods do that now? As far as I can tell, CocoaPods takes care of that for us.
	2

	3 The Framework directory contains the Xcode project used to build the framework. The PodTest directory contains a project used to confirm that the built framewor k installs correctly with CocoaPods. The build_ios_framework.sh script needs to be run first, then `pod install` should be run in the same directory as the Xcod e project. After installing, the PodTest.xcworkspace should be used instead of P odTest.xcodeproj.

	4

	5 USAGE

	6 To build the framework, run the build_ios_framework.sh script. This will build s tatic libraries for iOS (via the build_ios_libs.sh script), collect header files and adjust import/include statements for use inside the framework, build the fr amework using the Xcode project, merge multiple architectures together, and coll ect the framework files (the .framework itself and the .dSYM) with the Podspec i nto a common directory.

	7

	8 DETAILS OF THE XCODE PROJECT

	9 The Xcode project contains relative references to the built static libraries (fr om build_ios_libs.sh) as well as the iOS source files in webrtc/api/objc and web rtc/base/objc. NOTE: This will require updating if/when the built static librari es change.

	10

	11 The flattened header files for webrtc/api/objc and webrtc/base/objc were also ad ded to the Public Headers of the framework target. NOTE: This will require updat ing as the Obj-C API changes.

	12

	13 Preprocessor definitions were copied from a gyp-xcode generated project.

	14

	15 RTTI was disabled due to compiler errors and based on the setting in build/commo n.gypi (https://code.google.com/p/chromium/codesearch#chromium/src/build/common. gypi&q=rtti&sq=package:chromium&type=cs&l=5069).

	16

	17 Bitcode is disabled for the time being.

	18

	19 The minimum number of system frameworks were linked against based on build error s (currently AVFoundation, AudioToolbox, CoreMedia, VideoToolbox).
	tkchin_webrtc 2016/03/25 17:46:07 I think we may need these as well: CFNetwork, Core I think we may need these as well: CFNetwork, CoreGraphics, CoreVideo, GLKit, OpenGLES, QuartzCore Unless they are covered by CoreMedia? hjon_webrtc 2016/03/25 21:17:44 They don't appear to be covered by CoreMedia, but Show quoted text On 2016/03/25 17:46:07, tkchin_webrtc wrote: > I think we may need these as well: > CFNetwork, CoreGraphics, CoreVideo, GLKit, OpenGLES, QuartzCore > > Unless they are covered by CoreMedia? They don't appear to be covered by CoreMedia, but the four I listed were the only ones I received linker errors for. I didn't try yet, but it's possible it has something to do with the default for CLANG_MODULES_AUTOLINK (default being "Yes").
	20

	21 The Build Products Path (SYMROOT) was changed to $SRCROOT/build so the build pro ducts are in a known location.

	22

	23 The created WebRTC scheme was shared so the build_ios_framework.sh script will w ork on any machine that runs it.

	24

	25 DEPLOYMENT_POSTPROCESSING is set to "Yes" so debug symbols will be stripped (the iOS Default for STRIP_INSTALLED_PRODUCT is already set to "Yes").
	tkchin_webrtc 2016/03/25 17:46:07 Can you mention something about dSYM generation? Can you mention something about dSYM generation? hjon_webrtc 2016/03/25 21:17:44 Done. Show quoted text On 2016/03/25 17:46:07, tkchin_webrtc wrote: > Can you mention something about dSYM generation? Done.
OLD	NEW

« webrtc/build/ios/SDK/PodTest/PodTest/main.m ('K') | « webrtc/build/ios/SDK/PodTest/Podfile ('k') | webrtc/build/ios/SDK/WebRTC.podspec » ('j') | webrtc/build/ios/SDK/WebRTC.podspec » ('J')