[sdl3-mixer] build failure

[StarGate-One]

Operating system

Windows Version 11 [10.0.26200.8246]

Compiler

Visual Studio Community 2026 Version: [18.5.2] VS Tools Version: [14.50.35717] Microsoft (R) C/C++ Optimizing Compiler Version [19.50.35730] for x64

Steps to reproduce the behavior

`vcpkg install sdl3-mixer[fluidsynth,libflac,libvorbis,libxmp,mpg123,opusfile,wavpack]`

vcpkg install sdl3-mixer[fluidsynth,libflac,libvorbis,libxmp,mpg123,opusfile,wavpack]
Computing installation plan...
The following packages will be built and installed:
    sdl3-mixer[core,fluidsynth,libflac,libvorbis,libxmp,mpg123,opusfile,wavpack]:x64-windows@3.2.0#2
Installing 1/1 sdl3-mixer[core,fluidsynth,libflac,libvorbis,libxmp,mpg123,opusfile,wavpack]:x64-windows@3.2.0#2...
sdl3-mixer[core,fluidsynth,libflac,libvorbis,libxmp,mpg123,opusfile,wavpack]:x64-windows@3.2.0#2 package ABI: 0a05e89cbcb7448f941e7ca4471ab7ba4333b4545cd4895684fe8eb448b3042b
Building sdl3-mixer[core,fluidsynth,libflac,libvorbis,libxmp,mpg123,opusfile,wavpack]:x64-windows@3.2.0#2...
-- Using cached libsdl-org-SDL_mixer-release-3.2.0.tar.gz
-- Cleaning sources at D:/vcpkg/buildtrees/sdl3-mixer/src/ease-3.2.0-36575875f8.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkg-downloads/libsdl-org-SDL_mixer-release-3.2.0.tar.gz
-- Using source at D:/vcpkg/buildtrees/sdl3-mixer/src/ease-3.2.0-36575875f8.clean
-- Using cached msys2-mingw-w64-x86_64-pkgconf-1~2.5.1-1-any.pkg.tar.zst
-- Using cached msys2-msys2-runtime-3.6.5-1-x86_64.pkg.tar.zst
-- Using msys root at D:/vcpkg-downloads/tools/msys2/3e71d1f8e22ab23f
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Warning at scripts/cmake/vcpkg_execute_build_process.cmake:65 (message):
  Please ensure your system has sufficient memory.
Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/sdl3-mixer/portfile.cmake:50 (vcpkg_cmake_install)
  scripts/ports.cmake:206 (include)


-- Restarting build without parallelism
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j8
    Working Directory: D:/vcpkg/buildtrees/sdl3-mixer/x64-windows-dbg
    See logs for more information:
      D:\vcpkg\buildtrees\sdl3-mixer\install-x64-windows-dbg-out.log
      D:\vcpkg\buildtrees\sdl3-mixer\install-x64-windows-dbg-out-1.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/sdl3-mixer/portfile.cmake:50 (vcpkg_cmake_install)
  scripts/ports.cmake:206 (include)


error: building sdl3-mixer:x64-windows failed with: BUILD_FAILED
See https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
Elapsed time to handle sdl3-mixer:x64-windows: 3.6 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
  https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+sdl3-mixer
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=%5Bsdl3-mixer%5D%20build%20error%20on%20x64-windows&body=Copy%20issue%20body%20from%20D%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

Failure logs

install-x64-windows-dbg-out-1.log
install-x64-windows-dbg-out.log

Additional context

It fails to link mp3lame.lib

Update 2026-04-30: I have done some more troubleshooting and I am able to get a successful build if I remove feature fluidsynth from the vcpkg port sdl3-mixer command line:

vcpkg install sdl3-mixer[libflac,libvorbis,libxmp,mpg123,opusfile,wavpack]

Looks like port fluidsynth was just updated to version 2.5.4 last week.

Update 2026-05-01: Further research has ruled out fluidsynth and changes made to sdl3-mixer last week as I created a new fresh vcpkg current instance from github and only installed sdl3-mixer[fluidsynth,libflac,libvorbis,libxmp,mpg123,opusfile,wavpack] letting vcpkg install all the pre-requisite ports. Everything installed fine, so I created an additional vcpkg instance and installed all my normal ports/features and sdl3-mixer failed again with the same issue. Bottomline I think I have a source conflict somewhere that will take time to research.

I am not sure why a message of Please ensure your system has sufficient memory. is being shown as the PC has 192GB of memory and all the disk drives have at least 1TB free each?

[dg0yt]

I am not sure why a message of Please ensure your system has sufficient memory. is being shown as the PC has 192GB of memory and all the disk drives have at least 1TB free each?

For some packages linking fails due to memory pressure with high concurrency and lack of an adequate amount of memory. That's why the build process is restarted without concurrency after the first error.

But here, the error is LNK1104: cannot open file 'mp3lame.lib'.
The link lib actually named libmp3lame.lib. Some package is handling link libs incorrectly.

[dg0yt]

A possible dependency chain:
sdl3-mixer[fluidsynth] -> fluidsynth[sndfile] -> libsndfile[mpeg] -> mp3lame

[dg0yt]

mp3lame provide CMake config.
libsndfile uses and propagates CMakeConfig.
But check the installed version of libsndfile.
Or build sdl3-mixer with --trace-expand and share the config log.

[StarGate-One]

Thank you for the hints on the dependency chain and asking for the config.logs from trace-expand. This will give me something to study. I also see you found some things needing some work,

Here are the config log files:

vcpkg install --cmake-args=-DVCPKG_CMAKE_CONFIGURE_OPTIONS=--trace-expand sdl3-mixer[fluidsynth]

config-x64-windows-dbg-CMakeCache.txt.log
config-x64-windows-dbg-CMakeConfigureLog.yaml.log
config-x64-windows-dbg-ninja.log
config-x64-windows-out.log
config-x64-windows-rel-CMakeCache.txt.log
config-x64-windows-rel-CMakeConfigureLog.yaml.log
config-x64-windows-rel-ninja.log

[dg0yt]

There is -lmp3lame coming via pkg-config from fluidsynth... Not sure if sdl3-mixer should use pkg-config here, but fluidsynth also shouldn't pass the wrong link lib. (Well, I blame mp3lame. It doesn't provide pkg-config but can't be used consistently with (-l)mp3lame.)

[dg0yt]

FluidSynthConfigVersion.cmake:

# The created file sets PACKAGE_VERSION_EXACT if the current version string and
# the requested version string are exactly the same and it sets
# PACKAGE_VERSION_COMPATIBLE if the current version is >= requested version,
# but only if the requested major and minor versions are the same as the current
# one.
...
set(PACKAGE_VERSION "2.5.4")

sdl3-mixer/CMakeLists.txt:

find_package(FluidSynth "2.2.0" ${required})

Not the same major and minor... That's why it is falling back to pkg-config (and eventually ignores the version).

Finally reproduced in https://dev.azure.com/vcpkg/public/_build/results?buildId=131061&view=results.

[dg0yt]

#51508 should be good now.

[StarGate-One]

FluidSynthConfigVersion.cmake:

# The created file sets PACKAGE_VERSION_EXACT if the current version string and
# the requested version string are exactly the same and it sets
# PACKAGE_VERSION_COMPATIBLE if the current version is >= requested version,
# but only if the requested major and minor versions are the same as the current
# one.
...
set(PACKAGE_VERSION "2.5.4")

sdl3-mixer/CMakeLists.txt:

find_package(FluidSynth "2.2.0" ${required})

Not the same major and minor... That's why it is falling back to pkg-config (and eventually ignores the version).

Finally reproduced in https://dev.azure.com/vcpkg/public/_build/results?buildId=131061&view=results.

Wow it is amazing you found this!!!

I made an overlay port using the patch to sd3-mixer and it works great now.

Thank you so very much, it would have taken me a while to find this.

[dg0yt]

In the end it is just following the traces of CMake and/or pkgconfig.

[dg0yt]

I'm glad that you reported it because it enabled two fixes in one PR.