在開發(fā)過程中遇到這樣一個需求,我們對外提供的一個Library以aar的形式提供給外部使用,Library內(nèi)部依賴了內(nèi)網(wǎng)上的一些aar,導(dǎo)致別人使用Library時需要下載我們內(nèi)網(wǎng)的aar文件,造成導(dǎo)入失敗
fat-aar提供了這樣一個解決方案,詳細(xì)使用請參考fat-aar使用說明文檔
在生成依賴aar的R.class文件時,aar中R.txt文件還包括了Android系統(tǒng)內(nèi)部資源id
task generateRJava << {
println "Running FAT-AAR Task :generateRJava"
// Now generate the R.java file for each embedded dependency
def mainManifestFile = android.sourceSets.main.manifest.srcFile;
def libPackageName = "";
if(mainManifestFile.exists()) {
libPackageName = new XmlParser().parse(mainManifestFile).@package
}
embeddedAarDirs.each { aarPath ->
def manifestFile = file("$aarPath/AndroidManifest.xml");
if(!manifestFile.exists()) {
manifestFile = file("./src/main/AndroidManifest.xml");
}
if(manifestFile.exists()) {
def aarManifest = new XmlParser().parse(manifestFile);
def aarPackageName = aarManifest.@package
String packagePath = aarPackageName.replace('.', '/')
// Generate the R.java file and map to current project's R.java
// This will recreate the class file
def rTxt = file("$aarPath/R.txt")
def rMap = new ConfigObject()
if (rTxt.exists()) {
rTxt.eachLine {
line ->
//noinspection GroovyUnusedAssignment
def (type, subclass, name, value) = line.tokenize(' ')
rMap[subclass].putAt(name, type)
}
}
def sb = "package $aarPackageName;" << '\n' << '\n'
sb << 'public final class R {' << '\n'
rMap.each {
subclass, values ->
sb << " public static final class $subclass {" << '\n'
values.each {
name, type ->
sb << " public static $type $name = ${libPackageName}.R.${subclass}.${name};" << '\n'
}
sb << " }" << '\n'
}
sb << '}' << '\n'
mkdir("$generated_rsrc_dir/$packagePath")
file("$generated_rsrc_dir/$packagePath/R.java").write(sb.toString())
embeddedRClasses += "$packagePath/R.class"
embeddedRClasses += "$packagePath/R\$*.class"
}
}
}
這個生成規(guī)則會將aar中Android系統(tǒng)的資源id指向當(dāng)前Library,導(dǎo)致查找資源失?。╢at-aar合并時只會將res文件夾下的資源合并到當(dāng)前Library)
def rTxt = file("$aarPath/R.txt")
def rMap = new ConfigObject()
if (rTxt.exists()) {
rTxt.eachLine {
line ->
//noinspection GroovyUnusedAssignment
def (type, subclass, name, value) = line.tokenize(' ')
rMap[subclass].putAt(name, type)
}
}
def sb = "package $aarPackageName;" << '\n' << '\n'
sb << 'public final class R {' << '\n'
rMap.each {
subclass, values ->
sb << " public static final class $subclass {" << '\n'
values.each {
name, type ->
sb << " public static $type $name = ${libPackageName}.R.${subclass}.${name};" << '\n'
}
sb << " }" << '\n'
}
sb << '}' << '\n'
這個問題思考了好幾天都沒有想到解決方案,有一天突然靈感乍現(xiàn),想到AAPT生成R.id過程,好像R.id都是8位十六進(jìn)制表示,而且有一定的規(guī)則

image.png
中間 02 所在位置值代表資源ID對應(yīng)的資源的類型,分別是:
02:drawable
03:layout
04:values
05:xml
06:raw
07:color
08:menu
PS:分配resource id的主要邏輯實(shí)現(xiàn)是在framework/base/tools/aapt/Resource.cpp 和 ResourceTable.cp
Android系統(tǒng)資源id中間為都是01,只要我們修改fat-aar腳本,將Android資源id全部過濾掉,build過程就不會有問題了
最終腳本代碼如下:
def rTxt = file("$aarPath/R.txt")
def rMap = new ConfigObject()
if (rTxt.exists()) {
rTxt.eachLine {
line ->
//noinspection GroovyUnusedAssignment
def (type, subclass, name, value) = line.tokenize(' ')
if (value.startsWith("0x7f") && !value.startsWith("0x7f01")) {
rMap[subclass].putAt(name, type)
}
}
}
def sb = "package $aarPackageName;" << '\n' << '\n'
sb << 'public final class R {' << '\n'
rMap.each {
subclass, values ->
sb << " public static final class $subclass {" << '\n'
values.each {
name, type ->
sb << " public static $type $name = ${libPackageName}.R.${subclass}.${name};" << '\n'
}
sb << " }" << '\n'
}
sb << '}' << '\n'