i.MX Processorsのトピックandroid build fails for MX_O8.0.0_1 sabresd_6dq-userdebug

android build fails for MX_O8.0.0_1 sabresd_6dq-userdebug

nxp_com — Thu, 23 Aug 2018 10:05:05 GMT

I have a board with MCIMX6Q6AVT10AD, actually a Dave axel-lite board

It runs an old version of Android and I am tasked with having a newer one.

I have downloaded IMX_O8.0.0_1.0.0_ANDROID_SOURCE from NXP since it says that it applies to Imx 6Quad

I have followed the instructions on android_O8.0.0_1.0.0_docs , Android_User's_Guide.pdf and done

source ~/imx-o8.0.0_1.0.0_ga/imx_android_setup.sh with the associated download

(it would be GREAT if it was possible to use the -u option of repo to specify a LOCAL mirror for the standard android source)

Done source build/envsetup.sh and lunch sabresd_6dq-userdebug (for testing) and make -j 32 results in

build/core/base_rules.mk:238: error: vendor/nxp/fsl-codec: MODULE.TARGET.SHARED_LIBRARIES.lib_nb_amr_dec_v2_arm9_elinux already defined by vendor/fsl-codec

Suggestions ?

(Yes, I know that I have to adjust the devicetree and kernel, I am here asking for basic android build that fails on suggested example)

Build host is a linux amd64, devuan ascii

it builds successfully a vanilla version of android from the standard android repository

Re: android build fails for MX_O8.0.0_1 sabresd_6dq-userdebug

Yuri — Tue, 04 Sep 2018 07:22:13 GMT

Hello,

I managed to build the system, using instructions of the Android™ User's Guide.

After host computer setup, as recommended, the following commands were used:

$ cd ${MY_ANDROID}
$ source build/envsetup.sh
$ sabresd_6dq-userdebug
$ make 2>&1 | tee build-log.txt

Have a great day,

Yuri

------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer

button. Thank you!

Re: android build fails for MX_O8.0.0_1 sabresd_6dq-userdebug

nxp_com — Sat, 06 Oct 2018 10:31:49 GMT

Hello Yuri

It took me a while, but I finally managed to test your answer and it is wrong

You probably just copy pasted some instructions, without testing them.

So, what does actually work ?

The following will download the Oreo into the android_build

It takes ages, but eventually you get the build tree

$ cd /home/sipro/imx6q_o8

$ export WORKSPACE=/home/sipro/imx6q_o8

$ cp -rv /home/sipro/dev-android/DAMIANO/nxp/imx-o8.1.0_1.3.0_8m /home/sipro/imx6q_o8

$ source /home/sipro/imx6q_o8/imx-o8.1.0_1.3.0_8m/imx_android_setup.sh

Then, to actually build anything you can do

$ cd android_build

$ source build/envsetup.sh

$ lunch evk_8mq-userdebug

$ make

That is actually able to arrive at the end of the build (cannot test if it works since I have no such board)

The board I am working with is Category:AxelLite - DAVE Developer's Wiki

and currently has an old version of Android on it, I was hoping to build for a 6q CPU and tried

/home/sipro/imx6q_o8/android_build$ lunch sabreauto_6q-userdebug

this fails with the following

ninja: error: 'vendor/nxp/linux-firmware-imx/firmware/vpu/vpu_fw_imx6d.bin', needed by 'out/target/product/sabreauto_6q/system/lib/firmware/vpu/vpu_fw_imx6d.bin', missing and no known rule to make it
10:40:14 ninja failed with: exit status 1

Trying exactly what you suggested, with proper syntax

/home/sipro/imx6q_o8/android_build$ lunch sabresd_6dq-userdebug

still result in failure

ninja: error: 'vendor/nxp/linux-firmware-imx/firmware/vpu/vpu_fw_imx6d.bin', needed by 'out/target/product/sabresd_6dq/system/lib/firmware/vpu/vpu_fw_imx6d.bin', missing and no known rule to make it
12:25:35 ninja failed with: exit status 1

So, given that there is at least one build that "works" (it takes around 30 minutes on a 32threads + 32Gb ram machine) I would say that the linux environment should be reasonably correct.

I would say that if the other builds (beside the evk_8mq) are broken, better not have them around, so we know what to really expect from this Android build.

But surely it is not your fault