[TIMOB-17061] CLI needs to add the -dead_strip linker flag for i386
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-06-03T00:42:34.000+0000 |
| Affected Version/s | Release 3.2.3 |
| Fix Version/s | Release 3.3.0, Release 3.4.0 |
| Components | iOS |
| Labels | n/a |
| Reporter | Matt Langston |
| Assignee | Chris Barber |
| Created | 2014-06-02T20:40:47.000+0000 |
| Updated | 2014-09-15T15:24:47.000+0000 |
Description
The CLI's "ti build" command needs to add the -dead_strip linker flag for the i386 architecture (i.e. simulator builds) in order to allow ti.current to host multiple hyperloop modules. Without this flag the link will fail due to duplicate symbols.
The issues does not occur for device builds where the -dead_strip linker flag is already present.
This was the cause for the hyperloop bug #124: https://github.com/appcelerator/hyperloop/issues/124
Master pull request: https://github.com/appcelerator/titanium_mobile/pull/5753 3_3_X pull request: https://github.com/appcelerator/titanium_mobile/pull/5754
Tested that there are no more duplicate symbol errors from the linker when including two hyperloop modules into a ti.current app.
This appears resolved. We are continuing testing with a focus on trying to find any potential side-effects.
Mac OSX 10.9.3 Appcelerator Studio, build: 3.3.0.201406271159 Titanium SDK, build: 3.3.0.v20140701104113 Titanium CLI, build: 3.3.0-rc4 Alloy: 1.4.0-rc3 HyperLoop: 1.0.1 urlSession: 1.0.1 Tested a ti.current application with CoreMotion and urlSession hyperloop modules. Ran on device as well as packaged and installed the app. Ran into no errors during testing.
Closing