yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Guides, News, & Discussion] Technical:
Thanks. I've moved the source command and also will try Dakkar.

Overnight went until 99%...

Which Java version are you using to compile? I'm using 8 but seems I need to upgrade.

2 errors
[ 99% 76482/76981] Docs droiddoc: /home/technical/crdroid/out/target/common/docs/test-api-stubs
javadoc: warning - The old Doclet and Taglet APIs in the packages
com.sun.javadoc, com.sun.tools.doclets and their implementations
are planned to be removed in a future JDK release. These
components have been superseded by the new APIs in jdk.javadoc.doclet.
Users are strongly recommended to migrate to the new APIs.
DroidDoc took 22 sec. to write docs to /home/technical/crdroid/out/target/common/docs/test-api-stubs
[ 99% 76483/76981] Docs droiddoc: /home/technical/crdroid/out/target/common/docs/system-api-stubs
javadoc: warning - The old Doclet and Taglet APIs in the packages
com.sun.javadoc, com.sun.tools.doclets and their implementations
are planned to be removed in a future JDK release. These
components have been superseded by the new APIs in jdk.javadoc.doclet.
Users are strongly recommended to migrate to the new APIs.
DroidDoc took 23 sec. to write docs to /home/technical/crdroid/out/target/common/docs/system-api-stubs
[ 99% 76484/76981] Docs droiddoc: /home/technical/crdroid/out/target/common/docs/api-stubs
javadoc: warning - The old Doclet and Taglet APIs in the packages
com.sun.javadoc, com.sun.tools.doclets and their implementations
are planned to be removed in a future JDK release. These
components have been superseded by the new APIs in jdk.javadoc.doclet.
Users are strongly recommended to migrate to the new APIs.
DroidDoc took 25 sec. to write docs to /home/technical/crdroid/out/target/common/docs/api-stubs
ninja: build stopped: subcommand failed.
23:34:18 ninja failed with: exit status 1
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
Define it manually in device/phh/treble/rr.mk

make sure you're building with WITHOUT_CHECK_API=true
[Treble-Enabled Device Guides, News, & Discussion] srgrusso:
Thanks. Worked perfectly.
[Treble-Enabled Device Guides, News, & Discussion] Technical:
I tried Dakkar's script and could never build again...

technical@Mint:~/crdroid$ yes | bash ~/crdroid/treble_experimentations/build-dakkar.sh -j 4 crdroid arm64-ab-vanilla-nosu

Python 2.7.15rc1

.repo/manifests/: discarding 40 commits

fatal: manifest 'default.xml' not available

fatal: duplicate path external/exfat in /home/technical/crdroid/.repo/manifests/default.xml

Tried everything from deleting default.xml (that it says it's not available) and could not find the duplication of the path mentioned.

My script right now:

clear
cd ~/crdroid
source ~/.profile
git config --global user.email "..."
git config --global user.name "..."
export USE_CCACHE=1
export CCACHE_COMPRESS=1
export WIDELANDS_NINJA_THREADS=2
export WITHOUT_CHECK_API=true
repo init -u https://github.com/crdroidandroid/android.git -b 9.0
git clone https://github.com/phhusson/treble_experimentations
git clone https://github.com/phhusson/treble_patches -b android-9.0
git clone https://github.com/phhusson/treble_manifest .repo/local_manifests -b android-9.0
rm ~/crdroid/.repo/local_manifests/replace.xml

cp ~/crdroid/device/phh/treble/lineage.mk ~/crdroid/device/phh/treble/crdroid.mk
repo sync -c -f -j12 --force-sync --no-clone-bundle --no-tags
source ~/crdroid/device/phh/treble/generate.sh
yes | bash ~/crdroid/treble_experimentations/build-dakkar.sh -j 4 crdroid arm64-ab-vanilla-nosu
[Treble-Enabled Device Guides, News, & Discussion] srgrusso:
When I try and build roms with gapps I end up with the "Device is not Certified by Google" error when I boot my device. Is there a fix for this?

Thanks.
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
https://www.google.com/android/uncertified/
[Treble-Enabled Device Guides, News, & Discussion] Guido83:
Whenever I try to call "lunch treble_arm64_bvN-userdebug" its ending up showing this error:

build/make/core/config.mk:63: error: Cannot call KATI_obsolete_var on already obsolete variable: PATH.
[Treble-Enabled Device Guides, News, & Discussion] sasanqua:
Hey sir, I build the rom on unbntu on win10.

It always error likes this:

01:54:41 Could not create module-finder: finder encountered 84 errors: [/mnt/c/Windows/System32/havoc/packages/apps/Contacts/res/values-ko: lstat /mnt/c/Windows/System32/havoc/packages/apps/Contacts/res/values-ko: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Contacts/res/values-kn: lstat /mnt/c/Windows/System32/havoc/packages/apps/Contacts/res/values-kn: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-land: lstat /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-land: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-large: lstat /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-large: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-large-hdpi: lstat /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-large-hdpi: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-lo: lstat /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-lo: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-lt: lstat /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-lt: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-lv: lstat /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-lv: no such file or directory /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-mk: lstat /mnt/c/Windows/System32/havoc/packages/apps/Camera2/res/values-mk: no such file or directory /mnt/c/Windows/System32/havoc/external/tensorflow/tensorflow/contrib/feature_column: lstat /mnt/c/Windows/System32/havoc/external/tensorflow/tensorflow/contrib/feature_column: no such file or directory]...

I do not know what to do, please tell me.
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
Use any real Linux instead.

WSL will give you too many problems
[Treble-Enabled Device Guides, News, & Discussion] sasanqua:
Okay, I will try.

Thanks.:)
[Treble-Enabled Device Guides, News, & Discussion] grumpycoder100:
Hey there, thanks for the guide. Really handy. Anyways, I'd like to know if there's a way to use this guide to build a generic AOSP system image, instead of LineageOS, RR, etc.? Again, thanks for this.
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
Of course you can. Use phhusson's build script as I explained.
[Treble-Enabled Device Guides, News, & Discussion] grumpycoder100:
So what would I need to type in into romname argument? Or do i just leave it empty? Looking at build-rom.sh, it shows that it only has support for rr, los, and carbon.

Edit: Sorry, I wasn't clear enough. I do have another question though..

1) If I'm syncing an AOSP source instead of Lineage, where do I get the source from? Is it from android.googlesource.com?
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
You need to type android-9.0

mkdir romname; cd romname
bash ../treble_experimentations/build-rom.sh android-9.0 romname

The script will automatically initialize the repository, sync the source, apply patches and start building.
[Treble-Enabled Device Guides, News, & Discussion] grumpycoder100:
Noted, thanks! Am starting build process now :D
[Treble-Enabled Device Guides, News, & Discussion] reynard1:
i have this issuse with syncing repo:

can anyone help me?
[Treble-Enabled Device Guides, News, & Discussion] DevX_i0n:
Thanks for such a great guide. But I have a question, can I build it by Windows too? Or virtual machine?
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
I don't recommend Windows, never tried. Linux is the best for building.
[Treble-Enabled Device Guides, News, & Discussion] DevX_i0n:
Is it too slow for virtual machine then? thanks for responding
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
I'll depend on your device specifications and how much resources you will give to the vm. If I were you I would dual boot instead of using vm.
[Treble-Enabled Device Guides, News, & Discussion] DevX_i0n:
I tried to dual boot, but i failed...
[Treble-Enabled Device Guides, News, & Discussion] Technical:
I could only build with success via dual boot. VM and Windows bash can't perform well or be effective. You'll have +5Gb of RAM dedicated to compilation, and not counting the needed to operational system (in both guest and host).

Why did you fail to get dual boot is what I can't understand...
[Treble-Enabled Device Guides, News, & Discussion] DevX_i0n:
Cause my notebook doesn't recon my usb...i dunno why
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
How it looks if i want to bulid a Omnirom Pie? [MENTION=6084385]yshalsager[/MENTION]
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
The guide can be used for whatever rom.
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
Can i PM you?
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
I prefer asking here, so others can benefit from the discussion :D
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
Ok. So I've done a test carbon rom bulid using phhusson script with good result. However, I don't know how to bulid omnirom pie using dakkar's script. At "how to make GSI" wiki i have seen some roms mentioned like aex, aosp, lineage but no omni. Is it possible with dakkar's script or i have to do it manually? :silly:
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
You need to edit dakkar's script like https://github.com/phhusson/treble_...les#diff-d3ae52bd947c2a31d636d4f727911d18R150
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
../treble_experimentations/build-dakkar.sh: line 324: cd: device/phh/treble: No such file or directory

:eek:
[Treble-Enabled Device Guides, News, & Discussion] reynard1:
any help?
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
Yep i want help too but probably too much questions :D
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
Thank You very much Master! I will try and report! :)
[Treble-Enabled Device Guides, News, & Discussion] MiniatureTheGod:
How come it takes so long just to build a single system image? My computer has been going for 3 hours now. Currently it's "checking out files"

Edit:

Nooo it just failed because there is a space bar in the name of the hard drive that I was building it on ;(((

Is there some way I can resume it without having to do it all over again???
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
Mine is on syncing work tree :p
[Treble-Enabled Device Guides, News, & Discussion] filjusz:
Every time i try to build a rom (no matter if aex, omni or carbon) i've got error like this:

vendor/hardware_overlay/overlay.mk:1: error: _nic.PRODUCTS.[[device/phh/treble/treble_arm64_avN.mk]]: "device/phh/treble/omni.mk" does not exist.

19:44:26 dumpvars failed with: exit status 1
[Treble-Enabled Device Guides, News, & Discussion] Preet_:
I synced exactly how the OP said using dakkar.sh script and AEX ROM. But it synced the 8.1 branch instead of 9.0

How do I change this?
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
You need to edit the script, it's explained here before. Please use the search.
[Treble-Enabled Device Guides, News, & Discussion] Preet_:
Alright, thank you!
[Treble-Enabled Device Guides, News, & Discussion] Preet_:
A lot of patches failed for me, do I need to manually add those lines at the exact spot? I'm using Dakkar's script and building AEX 9.0.
[Treble-Enabled Device Guides, News, & Discussion] borksek:
Give the lines of error here so we know what problem we are dealing with.
[Treble-Enabled Device Guides, News, & Discussion] Preet_:
I'm currently ignoring the patch errors for now, I'm getting this which is breaking the build: https://del.dog/aoscp1.makefile

I'm building AOSCP Pie and they have merged the changes required for kernel headers, still getting this.
[Treble-Enabled Device Guides, News, & Discussion] newbie cyborg:
While trying to build Lineage 16.0 GSI for ARM-AONLY,the below message pops up in the terminal.

build/make/core/config.mk:971: error: Should not define BOARD_SYSTEMIMAGE_PARTITION_SIZE and BOARD_SYSTEMIMAGE_PARTITION_RESERVED_SIZE together.

11:49:11 dumpvars failed with: exit status 1

What can i do?
[Treble-Enabled Device Guides, News, & Discussion] Uclydde:
I'm trying to use phhusson's script to build an aosp GSI, but when I enter:

"bash ../treble_experimentations/build-rom.sh android-9.0 aosp"

I get an error:

"error: command 'sync' requires repo to be installed first.

Use "repo init" to install it here."
[Treble-Enabled Device Guides, News, & Discussion] I1V1A1N:
Amlogic has released a repository android_9.0 for amlogic s905x , s805x , s905x2 .But l can not download the code for box X96 amlogic s905x .I can not download via ssh connection .

http://openlinux.amlogic.com/Android/Mbox/9.0_Releaseinfo/way_for_get_code
[Treble-Enabled Device Guides, News, & Discussion] Dvalin21:
Asking the question, how do i integrate my source code for my device into the project?
[Treble-Enabled Device Guides, News, & Discussion] Beackman:
Well, i give up, i'm trying to build a GSI following the Guide, but always have a exited due fetch error or they run the process but build nothing.....
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
Try removing sap-api-java-static from Packages/apps/Bluetooth/Android.mk
[Treble-Enabled Device Guides, News, & Discussion] tmvkrpxl0:
now i have another problem.

log:

tmvkrpxl0@tmvkrpxl0-System-Product-Name:~/rom$ WITHOUT_CHECK_API=true make -j8 systemimage

============================================

▄▄▄ ▓█████ ▒██ ██▒

▒████▄ ▓█ ▀ ▒▒ █ █ ▒░

▒██ ▀█▄ ▒███ ░░ █ ░

░██▄▄▄▄██ ▒▓█ ▄ ░ █ █ ▒

▓█ ▓██▒░▒████▒▒██▒ ▒██▒

▒▒ ▓▒█░░░ ▒░ ░▒▒ ░ ░▓ ░

▒ ▒▒ ░ ░ ░ ░░░ ░▒ ░

░ ▒ ░ ░ ░

░ ░ ░ ░ ░ ░

AospExtended- 9

============================================

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=9

TARGET_PRODUCT=treble_a64_aoS

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=generic

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-4.15.0-43-generic-x86_64-Linux-Mint-19

HOST_CROSS_OS=windows

HOST_CROSS_ARCH=x86

HOST_CROSS_2ND_ARCH=x86_64

HOST_BUILD_TYPE=release

BUILD_ID=PQ1A.181205.006

OUT_DIR=/home/tmvkrpxl0/rom/out

============================================

[1/1] /home/tmvkrpxl0/rom/out/soong/.m...0/rom/out/soong/.bootstrap/build.ninja

[55/56] glob prebuilts/ndk/stl.bp

[79/79] /home/tmvkrpxl0/rom/out/soong/...me/tmvkrpxl0/rom/out/soong/build.ninja

/home/tmvkrpxl0/rom/out/build-treble_a64_aoS-cleanspec.ninja is missing, regenerating...

/home/tmvkrpxl0/rom/out/build-treble_a64_aoS.ninja is missing, regenerating...

[25/1218] including development/build/Android.mk ...

development/build/build_android_stubs.mk:43: warning: android_stubs_current

development/build/build_android_stubs.mk:43: warning: metalava_android_stubs_current metalava_android_stubs_current

development/build/build_android_stubs.mk:43: warning: android_system_stubs_current

development/build/build_android_stubs.mk:43: warning: android_test_stubs_current

development/build/build_android_stubs.mk:43: warning: metalava_android_system_stubs_current metalava_android_system_stubs_current

development/build/build_android_stubs.mk:43: warning: metalava_android_test_stubs_current metalava_android_test_stubs_current

[600/1218] including system/sepolicy/Android.mk ...

system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version

system/sepolicy/Android.mk:89: warning: Be careful when using the SELINUX_IGNORE_NEVERALLOWS flag. It does not work in user builds and using it will not stop you from failing CTS.

[1218/1218] including vendor/vndk-tests/Android.mk ...

[ 99% 1210/1211] glob vendor/qcom/open...rce/interfaces/wifi/supplicant/2.0/src

ninja: error: 'device/sample/etc/apns-full-conf.xml', needed by '/home/tmvkrpxl0/rom/out/target/product/phhgsi_a64_a/system/etc/apns-conf.xml', missing and no known rule to make it

21:12:43 ninja failed with: exit status 1

#### failed to build some targets (51 seconds) ####

i typed same commands. and both of apns-full.conf.xml files are missing
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
You need to clone https://android.googlesource.com/device/sample/ the same pie tag you're building.

Btw next time just paste the error lines or if you want to paste it all use something like del.dog please.
[Treble-Enabled Device Guides, News, & Discussion] tmvkrpxl0:
Thanks for the help. but on this time, log is too long so i'll just post end part of log.

if you need more, then i'll post ENTIRE LOG on del.dog

log: https://del.dog/avubaxagup.cs

error message: failed linking file resources.

it is too long and abstruse so i can't figure out what is problem.

I REALLY WANT TO USE AEX TREBLE. I HAVE ASKED ABOUT THIS PROBLEM ON TELEGRAM, but some people said i should try other roms, but aex is the best rom for me.

---------- Post added at 05:38 PM ---------- Previous post was at 05:28 PM ----------

i edited status_bar_items.xml and waiting for build

there would be another error?
[Treble-Enabled Device Guides, News, & Discussion] Technical:
So close, so far...

I've managed to build the A version of PixelDust (https://xdaforums.com/project-treble/trebleenabled-device-development/9-0-pixel-dust-pie-t3862484), but it fails on A/B, probably due to patches, although I'm not being able to figure out how to solve. If any dev could help, it's much appreciated.

The log is too big to fit in just one, so:

1. https://hastebin.com/eqaloxoziw.bash

2. https://hastebin.com/cehajorula.pl

Thanks.
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
You have to fix every single "Failed applying" patch, whether using cherry-picking or manually.
[Treble-Enabled Device Guides, News, & Discussion] tmvkrpxl0:
there is more error, log is this: https://del.dog/ojamobarut

but log is so abstruse, i post there ENTIRE log
[Treble-Enabled Device Guides, News, & Discussion] tmvkrpxl0:
that error appears at 90% this error might be the last error.

i need your help. i can't figure out what is problem. is there any information do you need more?

i turned off ALLOW_MISSING_DEPENDENCIES

and still no problem with that

i tried rebuilding few times, but same result

i know asked you about build error lots of times

and you helped me. thanks.

i don't want to border you, but i can't solve it myself. sorry
[Treble-Enabled Device Guides, News, & Discussion] Technical:
I was afraid of that... Each time I try to learn and use cherry-picking I fail... Man, how building Treble could be difficult! It's not a coincidence that only a few (very few) brave continue trying.

Manually, I could never understand the command "patch -p1 < patch" we have in the guide...

And trying to learn about cherry-picking seems rocket science, I've tried hard, but got nothing, a lot of different errors. So I was trying the phh script and solving the errors one by one. However, the major issue is always related to patches.
[Treble-Enabled Device Guides, News, & Discussion] yshalsager:
Cherry-picking was never hard :D the hard part might be solving merge conflicts :p

Watch a tutorial for that and test fixing it bravely :good:
[Treble-Enabled Device Guides, News, & Discussion] CATUVA21:
good day [MENTION=6084385]yshalsager[/MENTION] and everyone, I am compiling CarbonRom oreo 8.1 with trebl of phhusson for huawei with the device tree and vendor de huawei, the compilation gave me error when I was in 99% I leave a copy I hope you can help me

clarifies that you already compile lineage and crDroid oreo 8.1 running without problem

https://del.dog/ayesapilig.cs

:confused::D
[Treble-Enabled Device Guides, News, & Discussion] KRiST0F:
outdated scirpts?

hmmm i did not manage to build aex or rr (pie)

I think that for rr pie the dakar scripts are outdated.

and for both it seems that arm32_binder64 is missing.

the used commands are:

mkdir aex; cd aex

git clone https://github.com/phhusson/treble_experimentations

bash treble_experimentations/build-dakkar.sh aex arm32_binder64-aonly-vanilla-nosu

a log is in the attachments
[Treble-Enabled Device Guides, News, & Discussion] mcc2005:
I had the same problem. It depends on your cpu i think (i used an AMD Athlon X4 Phänom), so with my new Intel i5 all works fine...

---------- Post added at 12:54 ---------- Previous post was at 12:50 ----------

i wanted to create lineage for my arm32 Moto G6. When compiling I always get the following errors:

FAILED: /home/mcc/Lineage/out/soong/build.ninja
/home/mcc/Lineage/out/soong/.bootstrap/bin/soong_build -t -l /home/mcc/Lineage/out/.module_paths/Android.bp.list -b /home/mcc/Lineage/out/soong -n /home/mcc/Lineage/out -d /home/mcc/Lineage/out/soong/build.ninja.d -o /home/mcc/Lineage/out/soong/build.ninja Android.bp
error: vendor/qcom/opensource/cryptfs_hw/Android.bp:11:1: "libcryptfs_hw" depends on undefined module "generated_kernel_headers"
ninja: build stopped: subcommand failed.
12:05:18 soong bootstrap failed with: exit status 1

How can I fix this?
[Treble-Enabled Device Guides, News, & Discussion] MatrixHack01:
" Edit the .mk for your ROM "

Sorry, but i'm not able to properly get to know What exactly to edit and maybe because of that, i'g getting the following error. Could you guide me through this one step ??
[Treble-Enabled Device Guides, News, & Discussion] theGeekyLad:
I'm building a stock AOSP GSI right off the pie-gsi tag.

Everything's fine but for in-call audio. It's like, it doesn't even beep when it's connecting right before it starts ringing and for that matter, no ringing tone either. Absolutely no in-call audio.

I'm building for a Walleye (Pixel 2) and since it's a GSI, no vendor.img. The build process spits out just a system.img and a vbmeta.img (to disable AVB). I've also tried flashing / installing Lineage OS dialer but no luck.

Any idea?
[Treble-Enabled Device Guides, News, & Discussion] Louis1977:
help ;

============================================================

Get Ready To Be Xtended

============================================================

MSM Xtended ROM by Team-Xtended

============================================================

XTENDED_VERSION=Xtended--20190602-XP7-UNOFFICIAL-Release-v14.5

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=9

TARGET_PRODUCT=treble_arm64_bgS

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_GCC_VERSION=4.9

TARGET_ARCH=arm64

TARGET_ARCH_VARIANT=armv8-a

TARGET_CPU_VARIANT=generic

TARGET_2ND_ARCH=arm

TARGET_2ND_ARCH_VARIANT=armv8-a

TARGET_2ND_CPU_VARIANT=generic

BUILD_ID=PQ3A.190505.002

OUT_DIR=/home/luis/xtended/out

=============================================================

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-4.15.0-1032-gcp-x86_64-Ubuntu-16.04.6-LTS

HOST_CROSS_OS=windows

HOST_CROSS_ARCH=x86

HOST_CROSS_2ND_ARCH=x86_64

===============================================================

ninja: no work to do.

[1/1] /home/luis/xtended/out/soong/.bootstrap/bin/soong_build /home/luis/xtended/out/soong/build.ninja

FAILED: /home/luis/xtended/out/soong/build.ninja

/home/luis/xtended/out/soong/.bootstrap/bin/soong_build -t -l /home/luis/xtended/out/.module_paths/Android.bp.list -b /home/luis/xtended/out/soong -n /home/luis/xtended/out -d /home/luis/xtended/out/soong/build.ninja.d -o /home/luis/xtended/out/soong/build.ninja Android.bp

(0x8fcd40,0xc4201371d0)error: vendor/xtended/build/soong/Android.bp:31:8: module "generated_kernel_includes": cmd: unknown variable '$(KERNEL_MAKE_FLAGS)'

ninja: build stopped: subcommand failed.

03:56:41 soong bootstrap failed with: exit status 1
[Treble-Enabled Device Guides, News, & Discussion] @mind.mafia:
:confused:full secret my phone