Hi NXP experts,
I get the NXP BSP LF5.15.32_2.0.0 and encounter failed issue when I try to "bitbake qtwebengine -c configure".
The log message shows that
CMake Error at src/CMakeLists.txt:123 (message):
No gn found for cross-compilation
-- Configuring incomplete, errors occurred!
In the log I found something strange:
-- Could NOT find Gn: Found unsuitable version "1938 (0153d369)", but required is exact version "6.3.1" (found /media/1t/se_euro/nxp/imx-yocto-bsp/build-wayland/tmp/work/armv8a-poky-linux/qtwebengine/6.3.1-r0/recipe-sysroot-native/usr/bin/gn)
The required version number for Gn is "6.3.1"? It seems not a reasonable version format for gn...
Can anyone help me to build the qtwebengine module working?
解決済! 解決策の投稿を見る。
Hi @Neil-Hsu
I received the following explanation and solution from Yocto team:
There are two versions of gn-native available and the wrong version is getting picked up.
./meta-qt6/recipes-qt/qt6/gn-native_git.bb
./meta-browser/meta-chromium/recipes-browser/chromium/gn-native_96.0.4664.110.bb
We need to use the one from meta-qt6.
Please add the following line in local.conf to get pass this build error:
BBMASK += "/meta-browser/meta-chromium/recipes-browser/chromium/gn-native_.*\.bb"
Hi All,
This issue still happen in 5_15_71_220 BSP version.
I found a workaround to skip this problem. Comment out the meta-chromium layer in the bblayers.conf. But I can not confirm if this will cause other problems.
Hi @Neil-Hsu
I received the following explanation and solution from Yocto team:
There are two versions of gn-native available and the wrong version is getting picked up.
./meta-qt6/recipes-qt/qt6/gn-native_git.bb
./meta-browser/meta-chromium/recipes-browser/chromium/gn-native_96.0.4664.110.bb
We need to use the one from meta-qt6.
Please add the following line in local.conf to get pass this build error:
BBMASK += "/meta-browser/meta-chromium/recipes-browser/chromium/gn-native_.*\.bb"
If you comment out the meta-chromium layer in the bblayers.conf, the chromium may may not work properly.
The R&D team is handling this issue.I will update this case if they give any reply/patch.
Hi @Neil-Hsu
I can see same issue and i have post this in internal .