You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After commit 1830042 , slint-compiler invokes a configure script for jemalloc which seems to use autoconf to cross-compile.
When building within a Yocto environment, CC, etc. are set to the target compiler, and during the Slint-cpp crate build we have some build scripts that use cc.rs to build for the host. Therefore we set CC_${host} and cc.rs uses that instead.
As per 3c37c51 the same trick would work for jemalloc's configure to get past checking whether the C compiler works... no, but then we hit this:
checking how to run the C preprocessor... aarch64-poky-linux-gcc -E -mcpu=cortex-a57 -march=armv8-a+crc -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/runner/work/slint/yocto-sdk/sysroots/cortexa57-poky-linux
and that can't work.
The text was updated successfully, but these errors were encountered:
tronical
added
the
a:ci
Automation for CI (Continous integration system) and tests (mT,bO)
label
Jan 26, 2025
Maybe we need to make a change in corrosion?
We can also make the jemalloc a feature in slint-compiler and not enable it when cross compiling.
Or we just don't use jemalloc in the slint-compiler at all, that is not performance critical.
After commit 1830042 , slint-compiler invokes a configure script for jemalloc which seems to use autoconf to cross-compile.
When building within a Yocto environment, CC, etc. are set to the target compiler, and during the Slint-cpp crate build we have some build scripts that use cc.rs to build for the host. Therefore we set CC_${host} and cc.rs uses that instead.
As per 3c37c51 the same trick would work for jemalloc's configure to get past
checking whether the C compiler works... no
, but then we hit this:and that can't work.
The text was updated successfully, but these errors were encountered: