Documentation for aapt element in Ant script

后端 未结 3 1601
时光说笑
时光说笑 2020-12-15 00:38

I\'m working on some Ant scripts for an Android build system and have come across an element to call aapt. I have seen lots of examples with

exec executable=\"${aa

相关标签:
3条回答
  • 2020-12-15 01:00

    I couldn't find anything and ended up using the following which seems to work

        <exec executable="${aapt}" failonerror="true">
          <arg value="package" />
          <arg value="-f" />
          <arg value="-v" />
          <arg value="-M" />
          <arg path="AndroidManifest.xml" />
          <arg value="-A" />
          <arg path="assets" />
          <arg value="-I" />
          <arg path="${android.jar}" />
          <arg value="-m" />
          <arg value="-J" />
          <arg path="${out.absolute.dir}" />
          <arg value="-F" />
          <arg path="${out.absolute.dir}/${resource.package.file.name}" />
          <arg value="-S" />
          <arg path="res" />
          <arg value="--rename-manifest-package" />
          <arg value="my.new.package.name" />
        </exec>
    
    0 讨论(0)
  • 2020-12-15 01:03

    I highly doubt there is any documentation beyond the source code.

    0 讨论(0)
  • 2020-12-15 01:09

    In the new(er) version of the Android SDK, the ant build script works in a different way. It does not directly invoke the aapt command via an exec element but rather defines an aapt task. The latter one is implemented by the java class com.android.ant.AaptExecTask. This class only provides a subset of the aapt command line options.

    You can find a brief description of the mapping between aapt command line options and the ant parameters below as found in the source java doc:

    Aapt Option             Ant Name        Type
    ---------------------------------------------------------------------------------
    path to aapt            executable      attribute (Path)
    command                 command         attribute (String)
    -v                      verbose         attribute (boolean)
    -f                      force           attribute (boolean)
    -M AndroidManifest.xml  manifest        attribute (Path)
    -I base-package         androidjar      attribute (Path)
    -A asset-source-dir     assets          attribute (Path
    -S resource-sources     <res path="">   nested element(s)
                                            with attribute (Path)
    -0 extension            <nocompress extension="">  nested element(s)
                            <nocompress>               with attribute (String)
    -F apk-file             apkfolder                  attribute (Path)  
                            outfolder                  attribute (Path) deprecated
                            apkbasename                attribute (String)
                            basename                   attribute (String) deprecated
    
    -J R-file-dir       rfolder         attribute (Path)
                                        -m always enabled
    

    As far as I found out, there is no way to provide the generic aapt options through this new build task. This seems to be possible only by taking a modified copy of the SDK's build.xml with replacements for the aapt invocations.

    If anyone knows a better solution, I'd be glad to read about, too ;-)

    EDIT: In even newer versions of the SDK the introduced renaming packages again:

    Aapt Option   --rename-manifest-package package-name 
    Ant Name      manifestpackage
    Type          attribute (String)
    
    0 讨论(0)
提交回复
热议问题