Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-26944

Inconsistent Android SDK/NDK and JDK detection logic

    Details

    • Type: Story
    • Status: Open
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: Release 8.0.0
    • Fix Version/s: None
    • Component/s: Android, CLI, Tooling

      Description

      This is an internal development and architecture issue.

      We have 3 separate "codebases" around detecting the Android SDK/NDK and the JDK/JAVA_HOME.

      For developers building our SDK, we have some logic I wrote up in our "scons" scripts: https://github.com/appcelerator/titanium_mobile/tree/master/build/lib/android

      For SDK users (Titanium/Appc CLI) we delegate to node-titanium-sdk: https://github.com/appcelerator/node-titanium-sdk/blob/master/lib/android.js
      Which also delegates the jdk/Java stuff to node-apps: https://github.com/appcelerator/node-appc/blob/master/lib/jdk.js

      And for the Daemon, it uses androidlib and jdklib:

      We should not keep re-inventing the wheel repeatedly here. We should be re-using the same logic to detect these pieces regardless of whether we are building the SDK, using the SDK or using the daemon.

        Attachments

          Activity

            People

            • Assignee:
              cbarber Chris Barber
              Reporter:
              cwilliams Christopher Williams
            • Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:

                Backbone Issue Sync

                • Titanium SDK/CLI <> Titanium Mobile
                  Synced with:
                  TIMOB-21130
                  Sync status:
                  ERROR
                  Last received:
                  Last sent:

                  Git Source Code