| commit | d74517c52a6cd4172b1f3fdc4e624b6145ff5a0f | [log] [tgz] |
|---|---|---|
| author | VladimirTechMan <VladimirTechMan@gmail.com> | Sat Feb 25 02:08:27 2017 -0800 |
| committer | Commit bot <commit-bot@chromium.org> | Sat Feb 25 10:08:27 2017 +0000 |
| tree | 8baec4ad3a5e280dbcf20e0fdc22f0a27a79834b | |
| parent | 633f6fe0046131ed815098298b9a3120bac1d7a0 [diff] |
Do not produce dSYM file for the iOS Frameworks with bitcode Though dSYM files can be generated when building applications or libraries with bitcode. They cannot be used to symbolicate crash reports from applications. Instead, developers need to grab the real dSYM files, which are generated for each specific device type after uploading an iOS / tvOS application to App Store (or to a device using Xcode). Apple clearly warns about it in its documentation: https://developer.apple.com/library/content/technotes/tn2151/_index.html#//apple_ref/doc/uid/DTS40008184-CH1-SYMBOLICATION-BITCODE With that in mind, I believe that it would be better to not confuse developers by giving them dSYM files that are not very helpful with the bitcode-enabled framework. Thus, proposing the following modification to the building script, to generate dSYM by default only without the bitcode option. However, if some developers still want to get the dSYM files as a build-process artifact, when enabling bitcode, they can explicitly add --extra-gn-args enable_dsyms=true to the script. Let me know if it lgty. NOTRY=True BUG=None Review-Url: https://codereview.webrtc.org/2705163007 Cr-Commit-Position: refs/heads/master@{#16836}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.