[HELP] Compiling OmniROM for Nubia Z18 (NX606J) - Android Q&A, Help & Troubleshooting

Hi folks,
I've been trying to port OmniROM to ZTE's new Nubia Z18 (codename NX606J) but I'm stuck when trying to compile the ROM and need some help and leading advice as I'm new to ROM development as a whole.
I already asked in the Omni specific thread but didn't get an answer up until now. So since I believe this isn't just Omni related, please forgive me to ask again in the general section. :angel:
Device specific source can be found on my GitHub.
Kernel source is taken from nubia directly but forked by me for modifications in the future
Now onto the error I'm experiencing:
I run make -j4 after lunch-ing my device and it fails with:
Code:
[945/945] including vendor/omni/Android.mk ...
packages/apps/Bluetooth/Android.mk: error: Bluetooth (APPS android-arm) missing libbluetooth_jni (SHARED_LIBRARIES android-arm)
Available variants:
libbluetooth_jni (SHARED_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:833: error: exiting from previous errors.
03:34:57 ckati failed with: exit status 1
If I set ALLOW_MISSING_DEPENDENCIES=true (which I guess is bad practice) I get:
Code:
[ 99% 1390/1391] glob vendor/omni/overlay/common/**/*
ninja: error: '/run/media/curtisy/Solus-Data/omni_nx606j/out/target/product/nx606j/obj_arm/SHARED_LIBRARIES/libbluetooth_jni_intermediates/link_type', needed by '/run/media/curtisy/Solus-Data/omni_nx606j/out/target/product/nx606j/obj/APPS/Bluetooth_intermediates/2ND_jni_link_type', missing and no known rule to make it
03:39:28 ninja failed with: exit status 1
The lunch overview in case that's of any use, looks like this:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=omni_nx606j
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=kryo300
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=kryo
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.19.1-98.current-x86_64-Solus-3.9999
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PQ1A.181105.017.A1
OUT_DIR=/run/media/curtisy/Solus-Data/omni_nx606j/out
============================================
I'm hoping anyone with more experience has some idea as to what's the issue here. Maybe a look at my boardconfig will help, but I'm not sure. (My uneducated guess is that it's trying to compile for arm and arm64 but fails to link libbluetooth_jni to arm?)
Thanks in advance for any help, I'm really grateful for any straw I can hold onto currently.

---

better ask omni or lineage team my friend~gd luck!

---

If anyone comes across this in the future. Seems to be some weird setup with how some things use Android.bp and others Android.mk. That and the interaction the two have between each other. A quick fix is to just make it build both by editing the Android.bp file. Worked for me, though this issue doesn't seem to be that prevalent, might be caused by some other configuration issue? This works as quick fix, not sure if having two different binaries has some other negative effects though.
Code:
android/lineage/packages/apps/Bluetooth/jni/Android.bp:
cc_library_shared {
name: "libbluetooth_jni",
compile_multilib: "both", <---------- from "first" -> "both"