Extending mek_8q_car.mk file

[Grigoriy]

Hello!

I'm trying to extend mek_8q_car.mk file to customize nxp's AAOS. When I run building it fails with this error:

# Inherit from the base NXP MEK 8Q Automotive product configuration.
# This line is correct.
$(call inherit-product, $(LOCAL_PATH)/mek_8q_car.mk)
# If mek_8q_car.mk itself doesn't inherit from a more generic car.mk, you might need:
# $(call inherit-product, packages/services/Car/car_product/build/car.mk)
# However, usually the device-specific car makefile (mek_8q_car.mk) handles this.

# Set product identifiers
PRODUCT_NAME := rwth_mek_8q_car
PRODUCT_DEVICE := mek_8q # This seems correct given the error path

I placed it in /device/nxp/imx8q/mek_8q folder.  So, my question i how can I extend the mek_8q_car.mk file?

[Grigoriy]

Also, there are warnings:

WARNING '/home/grigoii/android_build/vendor/nxp-opensource/uboot-imx/ahab-container.img' not found, resulting binary is not-functional

[Zhiming_Liu]

Hi @Grigoriy 

Can you try to clean the build and rebuild it ?

Best Regards,
Zhiming

[Grigoriy]

I've added the changes and it throws this error:

[Grigoriy]

I mean what is the right way to extend it?

[Zhiming_Liu]

Hi @Grigoriy 

Please  also change the definition of product name in these files which for mek_8q_car.

imx8q/AndroidProducts.mk:  $(LOCAL_DIR)/mek_8q/mek_8q_car.mk \
imx8q/AndroidProducts.mk:  $(LOCAL_DIR)/mek_8q/mek_8q_car2.mk
imx8q/AndroidProducts.mk:  mek_8q_car-trunk_staging-user \
imx8q/AndroidProducts.mk:  mek_8q_car-trunk_staging-userdebug \
imx8q/AndroidProducts.mk:  mek_8q_car2-trunk_staging-user \
imx8q/AndroidProducts.mk:  mek_8q_car2-trunk_staging-userdebug
imx8q/mek_8q/mek_8q_car2.mk:include $(IMX_DEVICE_PATH)/mek_8q_car.mk
imx8q/mek_8q/mek_8q_car2.mk:PRODUCT_NAME := mek_8q_car2
imx8q/mek_8q/UbootKernelBoardConfig.mk:ifeq ($(TARGET_PRODUCT),mek_8q_car)
imx8q/mek_8q/mek_8q.mk:    else ifeq ($(TARGET_PRODUCT),mek_8q_car2)
imx8q/mek_8q/mek_8q.mk:    else ifeq ($(TARGET_PRODUCT),mek_8q_car2)
imx8q/mek_8q/mek_8q.mk:    else ifeq ($(TARGET_PRODUCT),mek_8q_car2)
imx8q/mek_8q/BoardConfig.mk:ifneq ($(TARGET_PRODUCT),mek_8q_car2)
imx8q/mek_8q/SharedBoardConfig.mk:ifeq ($(TARGET_PRODUCT),mek_8q_car)
imx8q/mek_8q/SharedBoardConfig.mk:ifeq ($(TARGET_PRODUCT),mek_8q_car2)
imx8q/mek_8q/SharedBoardConfig.mk:  # the env setting in mek_8q_car to make the build without M4 image
imx8q/mek_8q/SharedBoardConfig.mk:ifneq ($(TARGET_PRODUCT),mek_8q_car2)
imx8q/mek_8q/mek_8q_car.mk:PRODUCT_NAME := mek_8q_car
Binary file .git/index matches
Binary file .git/objects/pack/pack-b8b6a1435d99821cc2fc6ebb73ed298d4fc567a0.pack matches
common/build/encrypt_and_sign_firmware.mk:ifeq ($(TARGET_PRODUCT),$(filter $(TARGET_PRODUCT),mek_8q mek_8q_car mek_8q_car2))
common/build/encrypt_and_sign_firmware.mk:ifeq ($(TARGET_PRODUCT),$(filter $(TARGET_PRODUCT),mek_8q mek_8q_car mek_8q_car2))
common/tools/imx-make.sh:           [ ${TARGET_PRODUCT} = "mek_8q_car" ] || [ ${TARGET_PRODUCT} = "mek_8q_car2" ]; then
common/tools/imx-make.sh:        || [ ${TARGET_PRODUCT} = "mek_8q_car" ] || [ ${TARGET_PRODUCT} = "mek_8q_car2" ] \
common/tools/uuu_imx_android_flash.sh:currently suported platforms: evk_7ulp, evk_8mm, evk_8mq, evk_8mn, evk_8mp, mek_8q, mek_8q_car
common/tools/uuu_imx_android_flash.bat:echo currently suported platforms: evk_7ulp, evk_8mm, evk_8mq, evk_8mn, evk_8mp, mek_8q, mek_8q_car

Best Regards,
Zhiming

[Grigoriy]

Does it mean I have to use mek_8q_car2 everywhere? Or I can use my own name like my_mek_8q_car?

[Zhiming_Liu]

Hi @Grigoriy 

You can use your own configuration files, but you need to be aware of the dependencies between them.

Best Regards,
Zhiming