unfortunately we don't have docs on this.
the current usage of the task in the lastest rules is:
<apkbuilder
outfolder="${out.absolute.dir}"
resourcefile="${resource.package.file.name}"
apkfilepath="@{output.filepath}"
debug="${build.debug}"
abifilter="${filter.abi}"
verbose="${verbose}"
hascode="${manifest.hasCode}">
<dex path="${intermediate.dex.file}"/>
<sourcefolder path="${source.absolute.dir}"/>
<sourcefolder refid="android.libraries.src"/>
<jarfolder path="${external.libs.absolute.dir}" />
<jarfolder refid="android.libraries.libs" />
<nativefolder path="${native.libs.absolute.dir}" />
<nativefolder refid="android.libraries.libs" />
<extra-jars/>
</apkbuilder>
please note:
resourcefile is the compiled resource file (generated with the .ap_
extension). This is file *name* *only*. *Must* be located in
${outfoler}
apkfilepath is the destination file. This is the full path to the apk
to generate. does not have to be in outfolder.
basename is deprecated in tools r7 I think and will not be present in
r8 (will trigger an error)
apkbuilder should be pretty stable now, so hopefully if we do changes
we can keep compatibility.
Xav
--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
Please do not send me questions directly. Thanks!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
