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
I'm building the toolchain and watching it re-process the picolibc meson configuration dozens of times. Is there some reason the build cannot use the picolibc multi-lib support, once for arm and once for aarch64? I'm doing this in picolibc CI using -Dmultilib-exclude=aarch64 for the 32-bit build and -Dmultilib-exclude=arm for the 64-bit build to split out arm and aarch64 libs as the picolibc build system doesn't handle multiple architectures.
The text was updated successfully, but these errors were encountered:
Thank you for pointing this out, there may be an opportunity to simplify, indeed, however now it is done this way because of the testing setup that require different options.
I'm building the toolchain and watching it re-process the picolibc meson configuration dozens of times. Is there some reason the build cannot use the picolibc multi-lib support, once for arm and once for aarch64? I'm doing this in picolibc CI using
-Dmultilib-exclude=aarch64
for the 32-bit build and-Dmultilib-exclude=arm
for the 64-bit build to split out arm and aarch64 libs as the picolibc build system doesn't handle multiple architectures.The text was updated successfully, but these errors were encountered: