Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-9031] Android: Tooling Need to update new ndk to r8 for our sdk

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2012-05-16T16:41:22.000+0000
Affected Version/sRelease 2.0.2
Fix Version/sRelease 2.0.2, Release 2.1.0, Sprint 2012-10 Core
ComponentsAndroid
Labelscore
ReporterNatalie Huynh
AssigneeBill Dawson
Created2012-05-07T17:16:06.000+0000
Updated2012-05-17T14:52:45.000+0000

Description

Need to update our build to use ndk r8

Comments

  1. Bill Dawson 2012-05-14

    Just an update: no changes required in the code. I have a request in (since Friday) to IT and to Cloud Engineering (e-mail to each of the Tonys) re what I need to do to get CI on ndk 8. As of yet, no response.
  2. Bill Dawson 2012-05-15

    Update: in communication with Nikolai and access is being granted to me. CLOUDENG-2558
  3. Bill Dawson 2012-05-15

    NDK 8 is now successfully being used on the jenkins master server for titanium_mobile_master and titanium_mobile_2.0.x. Was unable so far to update the "Mac slave" for titanium_mobile_modules build because that machine is offline. I alerted Nikolai.
  4. Bill Dawson 2012-05-16

    Mac slave also updated, and a test run o the titanium_mobile_modules build was successful.
  5. Bill Dawson 2012-05-17

    A test you can run to see if NDK8 was used on the build (run it from inside the version folder, i.e., /Library/Application Support/Titanium/mobilesdk/osx/2.1.0) 
       $ strings android/native/libs/armeabi/libkroll-v8.so | grep udivsi3
    If it returns nothing, then it was built with NDK8. If it returns anything else, then it wasn't built with NDK8.
  6. Natalie Huynh 2012-05-17

    Tested with 2.0.2.v20120516181650 ran strings android/native/libs/armeabi/libkroll-v8.so | grep udivsi3 did not return any values

JSON Source