./gradlew assembleFenixRelease produces broken apks for architectures without libxul.so
Categories
(Fenix :: Tooling, defect)
Tracking
(Not tracked)
People
(Reporter: jrmuizel, Unassigned)
Details
After running ./gradlew assembleFenixRelease
I get:
-rw-rw-r-- 1 jrmuizel jrmuizel 38547968 May 8 14:06 app-fenix-armeabi-v7a-release-unsigned.apk
-rw-rw-r-- 1 jrmuizel jrmuizel 39329823 May 8 14:06 app-fenix-x86_64-release-unsigned.apk
-rw-rw-r-- 1 jrmuizel jrmuizel 39498492 May 8 14:06 app-fenix-x86-release-unsigned.apk
-rw-rw-r-- 1 jrmuizel jrmuizel 98740863 May 8 14:06 app-fenix-arm64-v8a-release-unsigned.apk
The non-arm65-v8a apks are all missing libxul.so and presumably don't work. I'd rather not build them at all.
Comment 1•8 months ago
|
||
The severity field is not set for this bug.
:007, could you have a look please?
For more information, please visit BugBot documentation.
Comment 2•8 months ago
|
||
Hey Jeff,
This bug reminds me another one that was related to some configuration in the mozconfig
file.
What do you have in your mozconfig
?
Reporter | ||
Comment 3•8 months ago
|
||
mk_add_options AUTOCLOBBER=1
ac_add_options --enable-project=mobile/android
ac_add_options --target=aarch64
ac_add_options --enable-release
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-fenix
Comment 4•8 months ago
|
||
Ok, it's not related to what I had in mind (not having ac_add_options --target=aarch64
for non-artifact builds).
I guess we have two possible ways here, making sure the other architecture contain libxul.so
and the other one being avoid generating the other architecture's apks.
Is there a reason why you suggested the latter?
Reporter | ||
Comment 5•8 months ago
|
||
Because my mozconfig is only asking aarch64 so I don't want to create the other apks. Also, my libxul.so is only for aarch64 so there's no way the other apks can work without building libxul 4 times.
Updated•7 months ago
|
Description
•