Open pal1000 opened 2 years ago
pacman -Syu
then pacman -Su
;pacman -S bison flex git ${MINGW_PACKAGE_PREFIX}-{cc,clang,libclc,meson,pkgconf,python-mako,spirv-llvm-translator,spirv-tools,zstd} --needed
git clone --branch=main https://gitlab.freedesktop.org/mesa/mesa.git mesa
cd mesa
${MINGW_PREFIX}/bin/meson setup build --buildtype=release -Db_ndebug=true -Dzstd=enabled --prefer-static -Dcpp_rtti=true -Dllvm=enabled -Dshared-llvm=disabled -Dgallium-drivers= -Dvulkan-drivers= -Dshared-glapi=auto -Dmicrosoft-clc=enabled -Dstatic-libclc=all -Dc_args="-march=core2 -pipe" -Dcpp_args="-march=core2 -pipe" -Dc_link_args="-static -s -ltre -lintl -liconv" -Dcpp_link_args="-static -s -ltre -lintl -liconv"
${MINGW_PREFIX}/bin/ninja -C build
There should be a warning during config about clang-cpp being a shared library only just like with 1st case but it's not.
Microsoft CLC built like this always crashes. I wonder if clang-cpp actually gets linked in or clang doesn't get linked in at all. The latter justifies the crashes.
Native
Windows 11
3.10.6
meson --version
0.63.1
ninja --version
if it's a Ninja build1.11.0
This issue was first mentioned here.
Case 1: library is required
To Reproduce
pacman -Syu
thenpacman -Su
;pacman -S bison flex git ${MINGW_PACKAGE_PREFIX}-{cc,meson,pkgconf,python-mako,vulkan-loader,zlib,zstd} --needed
${MINGW_PREFIX}/bin/meson setup build --buildtype=release -Db_ndebug=true -Dzstd=enabled --prefer-static -Dllvm=disabled -Dgallium-drivers=zink -Dvulkan-drivers= -Dshared-glapi=enabled -Dc_args="-march=core2 -pipe" -Dcpp_args="-march=core2 -pipe" -Dc_link_args="-static -s -ltre -lintl -liconv" -Dcpp_link_args="-static -s -ltre -lintl -liconv"
${MINGW_PREFIX}/bin/ninja -C build
Expected behavior
Build should succeed with gallium megadriver linked with Vulkan shared library as there is no static library. This warning is displayed as it should though:
WARNING: Static library 'vulkan' not found for dependency 'vulkan', may not be statically linked
Actual result
System parameters
Native
Windows 11
3.10.6
meson --version
0.63.1
ninja --version
if it's a Ninja build1.11.0
Another instance of this issue was analyzed here.