Unable to link statically compiled SFML with clang MSVC

[ebots]

I have statically compiled SFML 2.6.1 from source using LLVM 19 on Windows
When I try to compile my code, lld-link omits an error saying "mismatch detected for 'RuntimeLibrary'

I tried looking up fixes for this problem, but they all involve changing settings within Visual Studio and I do not want to use Visual Studio

Code Used:

#include "SFML/Graphics.hpp"

int main() {
    sf :: RenderWindow window(sf :: VideoMode(400, 400), "SFML works!");

    sf :: CircleShape shape(100.f);
    shape.setFillColor(sf :: Color :: Green);

    while (window.isOpen()){
        sf :: Event event;

        while (window.pollEvent(event)) {
            if (event.type == sf :: Event :: Closed)
                window.close();
        }

        window.clear();
        window.draw(shape);
        window.display();
    }

    return 0;
};
 

Compile Command:

Code: [Select]

clang++ test.cpp -o test.exe -fuse-ld=lld-link -D SFML_STATIC -I "SFML-2.6.1\include" -L "SFML-2.6.1\build\lib" -l sfml-graphics-s -l sfml-window-s -l sfml-system-s -l opengl32 -l winmm -l gdi32

Error:

Code: [Select]

lld-link: error: /failifmismatch: mismatch detected for 'RuntimeLibrary':
>>> C:\Users\\AppData\Local\Temp\test-db37c8.o has value MT_StaticRelease
>>> sfml-graphics-s.lib(CircleShape.cpp.obj) has value MD_DynamicRelease
clang++: error: linker command failed with exit code 1 (use -v to see invocation)


[eXpl0it3r]

You need to set SFML_USE_STATIC_STD_LIBS to ON when building SFML with CMake, so that it too uses the static runtimes.

[ebots]

But then wouldn't that make it produce dlls instead of static libraries?

[eXpl0it3r]

Using static runtime with shared libraries is not a flow that SFML supports and neither one that you should ever be using, because you end up duplicating the runtime for each shared library (i.e. every DLL would have its own copy of the runtime), which can will cause issues.

[ebots]

So does that mean that building with SFML_USE_STATIC_STD_LIBS will produce static libraries?

[eXpl0it3r]

Not on its own, for that you need to set BUILD_SHARED_LIBS to OFF.

See also the CMake tutorial: https://www.sfml-dev.org/tutorials/2.6/compile-with-cmake.php

[ebots]

I tried compiling SFML with BUILD_SHARED_LIBS off and SFML_USE_STATIC_STD_LIBS on, but I am still getting the same linker error when trying to compile my code

[eXpl0it3r]

Make sure you're using the newly produced library files.

What's the exact new error?

[ebots]

Code: [Select]

lld-link: error: /failifmismatch: mismatch detected for 'RuntimeLibrary':
>>> C:\Users\\AppData\Local\Temp\test-af06e4.o has value MT_StaticRelease
>>> sfml-graphics-s.lib(CircleShape.cpp.obj) has value MD_DynamicRelease
clang++: error: linker command failed with exit code 1 (use -v to see invocation)


[eXpl0it3r]

Did you actually rebuild SFML or just rerun CMake?

Code: [Select]

>>> sfml-graphics-s.lib(CircleShape.cpp.obj) has value MD_DynamicRelease


This is clearly not updated to use the static runtime, so either SFML wasn't rebuilt or you're still pointing to the old files.

[ebots]

I did recompile SFML using the CMake GUI when I got that error, but regardless I tried recompiling SFML again with SFML_USE_STATIC_STD_LIBS on and BUILD_SHARED_LIBS off, and I am still getting the same linker error saying that the SFML static library has value MD_DynamicRelease. Also I checked and I am linking against the updated libraries

[ebots]

I did some more testing, and the problem seems to arise with the fact that LLVM downloaded directly from the website, uses MSVC, causing problems with linking and the runtime. Though I am not so sure why SFML is being marked as MD_DynamicRelease when it is static libraries. I tried using clang from MinGW, which uses GCC's standard library and that seems to work fine. I am not sure if this is an issue with MSVC or SFML, but it most likely seems to be an MSVC issue

[eXpl0it3r]

I did recompile SFML using the CMake GUI

But the CMake GUI itself doesn't build anything.
It just generates make/project files. You still need to invoke your toolchain to actually generate the libraries.

[ebots]

I forgot to mention I also ran the makefile after the CMake GUI