PPC Mac problems with android SDK - unparsed aapt file

Common bugs/problems with the Android SDK the Emulator and the ADT-Plugin.

PPC Mac problems with android SDK - unparsed aapt file

Postby tijames » Sun Dec 23, 2007 2:21 pm

Im using a PPC (PowerPC) and I can't start the emulator within Eclipse - Europa because of an error, unparsed aapt. I located it within the android SDK and got info on it. The aapt file was an intel unix executable file only, so yeah, intel macs only.

Is there anyway to get around this or will i have to wait for google to update it for PPC mac support?

One thing I read on google was that the aapt wasnt something neccesary to make an android app so yeah... hmm...
tijames
Freshman
Freshman
 
Posts: 9
Joined: Thu Dec 20, 2007 3:25 am

Top

Postby plusminus » Sun Dec 23, 2007 2:49 pm

Hello tijames,

yes it is not necessary, but you will have awful times doing the workarounds :D
The aapt.exe compiles the Resources to your project every Compile and generates the R.java to make your resources 'safe' accessible in Java-Code.

I do not know if there is a aapt.exe for PPC ... :(

Regards,
plusminus
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Postby tijames » Mon Dec 24, 2007 2:52 am

Hmm, well do you know the process I'd have to take to make an R.java to add to my project?
If not could you send me a tutorial or something that you know that could help me out?
Much appreciated. ^__^
tijames
Freshman
Freshman
 
Posts: 9
Joined: Thu Dec 20, 2007 3:25 am

Postby plusminus » Mon Dec 24, 2007 2:53 pm

Hello tijames,

there are like 10[sup]10[/sup] Parameters you can pass to the aapt.exe . Without the actual problem (owning a PPC) I won't be able to help.
This is the help-output of the aapt.exe:
Android Asset Packaging Tool

Usage:
aapt l[ist] [-v] file.{zip,jar,apk}
List contents of Zip-compatible archive.

aapt p[ackage] [-c][-f][-g][-s][-u][-m][-v][-x][-M AndroidManifest.xml]
[-l locale1[,locale2,...]] [-d device1[,device2,...]]
[-I base-package [-I base-package ...]]
[-A asset-source-dir] [-P public-definitions-file]
[-S resource-source-dir]
file.{zip,jar,apk} [raw-files-dir [raw-files-dir] ...]

Create or update the named Zip-compatible archive. All files in raw-files-dir will be added to the archive, as will selected directories in asset-root-dir (which should contain a 'default' directory and some locale-specific directories). The named locales and vendors will be added, all others will be excluded.

aapt c[ompile] [-m][-v][-x] [-M AndroidManifest.xml] [-J R-file-dir]
[-A asset-source-dir] [-S resource-source-dir]
[-I base-package [-I base-package ...]]
[-P public-definitions-file] [-R resource-intermediates-dir]
[raw-files-dir [raw-files-dir] ...]

Compile binary resources from assets. Scans through asset-root-dir for all sources that need to be compiled to binary assets.
If the -J option is specified, the "R.java" files will be generated in the indicated directory. A class "R" will be generated in the package specified by AndroidManifest.xml.

aapt d[elete] [-v] file.{zip,jar,apk} file1 [file2 ...]
Delete specified files from Zip-compatible archive.

aapt a[dd] [-v] file.{zip,jar,apk} file1 [file2 ...]
Add specified files to Zip-compatible archive.

aapt v[ersion]
Print program version.

Modifiers:
-d one or more device assets to include, separated by commas
-c compile resources from assets
-f force overwrite of existing files
-g only write generated assets; do not package source assets
-j specify a jar or zip file containing classes to include
-l one or more locale assets to include, separated by commas
-m make package directories under location specified by -J
-s sync existing packages (update + remove deleted files)
-u update existing packages (add new, replace older)
-v verbose output
-x create extending (non-application) resource IDs
-z require localization of resource attributes marked with localization="suggested"
-A additional directory in which to find raw asset files
-I add an existing package to base include set
-J specify where to output R.java resource constant definitions
-M specify full path to AndroidManifest.xml to include in zip
-P specify where to output public resource definitions
-R specify directory containing generated resource files (in or output)
-S additional directory in which to find resource source assets
-0 don't compress files we're adding


Merry Christmas,
plusminus :xmas:
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Postby tijames » Tue Dec 25, 2007 3:42 am

I'm sorry but I understand none of this.... is there like a step by step tutorial or what? Sorry for asking so much of you. @_@
tijames
Freshman
Freshman
 
Posts: 9
Joined: Thu Dec 20, 2007 3:25 am

Postby plusminus » Wed Dec 26, 2007 7:07 pm

Hello tijames,

I also do not know what parameters to use with the aapt.exe to achieve what Eclipse would do for you.
But I forgot that the aapt.exe was not working with you (because of PowerPC) :(

Perhaps use a VirtualMachine ... :?:

Regards,
plusminus
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Top

Postby tijames » Thu Dec 27, 2007 5:46 am

Alright, thanks anyway. ^__^

And virtual machines don't work on PPC macs, unless it's Virtual PC, but it's not that great... at all...

~TI-James
tijames
Freshman
Freshman
 
Posts: 9
Joined: Thu Dec 20, 2007 3:25 am

Top

Return to SDK/ADT/Emulator Problems

Who is online

Users browsing this forum: No registered users and 4 guests