Closed Bug 960640 Opened 10 years ago Closed 10 years ago

configure errors when building with latest android SDK bundle, cannot find dx

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 31

People

(Reporter: kats, Assigned: nalexander)

References

Details

Attachments

(3 files)

+++ This bug was initially created as a clone of Bug #941889 +++

If I download the latest SDK ADT Bundle for Mac from http://developer.android.com/sdk/index.html and use it to build, dx is not found. In this version (adt-bundle-mac-x86_64-20131030.zip) dx resides at adt-bundle-mac-x86_64-20131030/sdk/build-tools/android-4.4/dx and our autoconf files only look for android-4.3 and some other folders. Rather than having to change this every time google updates their SDK (see the bug I cloned this from, for example) we should figure out some wildcard pattern that lets us find dx properly.
Attached patch bug-960640.patchSplinter Review
This fixes the issue in the interim.
Attached patch bug-960640.patchSplinter Review
Patch is the same as the other attached one - but also includes the build-tools version 19.0.1...for those that don't use the eclipse adt.
There's got to be a better way to figure this out...rather than having to patch the configure file every time :)
This lists the directories in build-tools/*, sorts them by
version (favouring new-style 'android-*' directories), and then takes
the newest version in which aapt exists.
Attachment #8405062 - Flags: review?(mh+mozilla)
Blocks: 941889
Attachment #8405062 - Flags: review?(mh+mozilla) → review+
https://hg.mozilla.org/integration/fx-team/rev/c2c8796a9212
Assignee: nobody → nalexander
Status: NEW → ASSIGNED
OS: Mac OS X → Android
Hardware: x86 → All
https://hg.mozilla.org/mozilla-central/rev/c2c8796a9212
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 31
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.