Failure Building SDK for mek_8q

[tombo1]

Hello,

We have successfully built Android 11 for the iMX8 but receive the following errors when attempting to build the SDK using the command "make sdk". The complete build log is attached.

development/build/sdk-linux-x86.atree:34: couldn't locate source file: lib64/libclang_android.so
development/build/sdk-linux-x86.atree:36: couldn't locate source file: lib64/libaapt2_jni.so
development/build/sdk.atree:53: couldn't locate source file: bin/dmtracedump
development/build/sdk.atree:54: couldn't locate source file: bin/etc1tool
development/build/sdk.atree:80: couldn't locate source file: bin/aapt
development/build/sdk.atree:81: couldn't locate source file: bin/aapt2
development/build/sdk.atree:82: couldn't locate source file: bin/aidl
development/build/sdk.atree:83: couldn't locate source file: bin/split-select
development/build/sdk.atree:84: couldn't locate source file: bin/zipalign
development/build/sdk.atree:87: couldn't locate source file: bin/llvm-rs-cc
development/build/sdk.atree:88: couldn't locate source file: bin/bcc_compat
development/build/sdk.atree:133: couldn't locate source file: bin/apksigner
development/build/sdk.atree:134: couldn't locate source file: framework/apksigner.jar
development/build/sdk.atree:137: couldn't locate source file: bin/dx
development/build/sdk.atree:138: couldn't locate source file: framework/dx.jar
development/build/sdk.atree:237: couldn't locate source file: system-qemu.img
development/build/sdk.atree:238: couldn't locate source file: vendor-qemu.img
development/build/sdk.atree:239: couldn't locate source file: ramdisk-qemu.img
development/build/sdk.atree:241: couldn't locate source file: data/misc
development/build/sdk.atree:243: couldn't locate source file: VerifiedBootParams.textproto
ninja: build stopped: subcommand failed.
20:51:00 ninja failed with: exit status 1

#### failed to build some targets (01:02 (mm:ss)) ####

We would appreciate any help in this matter.

Thanks,
Tom

[Zhiming_Liu]

Hi

Did you source the env and lunch before make?

BR

Zhiming

[tombo1]

Hello Zhiming,

Sorry for the delay in my response. Yes, I ran the following commands...

source build/envsetup.sh
lunch mek_8q-userdebug

Then I attempted to build sdk using the commands both the same results...

make sdk
make win_sdk

Thanks,
Tom

[Zhiming_Liu]

Hi tombo1

Can you try to lunch eng mode?

BR

Zhiming

[tombo1]

Hello Zhiming,

I rebuilt the environment and achieved the same errors from my original post. The commands I used for this attempt...

lunch mek_8q-eng
./imx-make.sh -j16 2>&1 | tee build-log.txt

#### build completed successfully (02:08:17 (hh:mm:ss)) ####

make sdk

Received same error as original post

Thanks for your continued help,
Tom

[Zhiming_Liu]

I think the full steps are:

1. Do the standard build

lunch mek_8q-eng

make

2. Build the missing tools

make dmtracedump
make etc1tool
make split-select
make bcc_compat
make apksigner
make dx

make libaapt2_jni

make layoutlib-legacy

3. a) Edit the file development/build/sdk.atree to comment out the reference to userdata.img

##############################################################################
# System image Component
##############################################################################

# System images + Kernel
system.img                                 system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/system.img
ramdisk.img                                system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/ramdisk.img
#userdata.img                               system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/userdata.img
system/build.prop                          system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/build.prop

# Note: the kernel image is handled by sdk-android-<abi>.atree now.

3. b) Alternatively, it appears that you can enable the creation of userdata.img (I have not tried this): https://community.nxp.com/docs/DOC-105198

4. Edit the file development/build/sdk.atree (again) to comment out the reference to EmulatorSmokeTests.apk

##############################################################################
# Tests Component
##############################################################################
#system/app/EmulatorSmokeTests/EmulatorSmokeTests.apk tests/emulator-test-apps/EmulatorSmokeTests.apk

5. Build the sdk

make sdk

[tombo1]

Hello,

Thanks for your response. I attempted to follow these steps but...

There are no build rules for layoutlib-legacy

and there is no mention of EmulatorSmokeTests.apk  in the sdk.atree file.

Are you sure these build rules will work for building imx-automotive-11.0.0_1.1.0 SDK?

Your continued help in this matter would be appreciated.

Thanks,
Tom

PS I believe I saw these build suggestions in a nearly three year old post from‎ July of 2018 as well. I did attempt them previously.

Is anyone able to build the SDK?

[Zhiming_Liu]

Hi

I have fixed this issue

make dmtracedump -j8

make etc1tool -j8

make libaapt2_jni -j8

make aapt -j8

make aapt2 -j8

make aidl -j8

make split-select -j8

make zipalign -j8

make llvm-rs-cc -j8

make bcc_compat -j8

make apksigner -j8

make dx -j8

Then comment codes in /android_build/development/build/sdk.tree

# System images + Kernel
#system-qemu.img                                 system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/system.img
#vendor-qemu.img                                 system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/vendor.img
#ramdisk-qemu.img                                system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/ramdisk.img
device/generic/goldfish/data/etc/userdata.img    system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/userdata.img
#data/misc                                        system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/data/misc
system/build.prop                          system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/build.prop
#VerifiedBootParams.textproto   system-images/${PLATFORM_NAME}/${TARGET_CPU_ABI}/VerifiedBootParams.textproto

These doesn't affect sdk.

BR

Zhiming

[tombo1]

Awesome! These instructions appear to work. I am able to build the SDK. Trying out the SDK now.

Thanks for your help!

Tom