Sounds like you two have different goals.

Linking everything statically into your programs

If this is what you want, you can use the official binaries and don't have to build a toolchain yourself. Pass -static option to the linker when you link your programs, and you will get self-contained binaries. (Some people suggest -static-libgcc -static-libstdc++ but it doesn't affect libwinpthread-1.dll.)

You shouldn't build DLLs this way, or you will end up with multiple instances of the same runtime components in a single process, which will bite you later.

Linking everything statically into gcc itself

If this is what you want, you need to build a toolchain yourself. Pass whatever option you want and also --static-gcc to the build script. This should create self-contained gcc.exe, g++.exe etc.

Toolchains built this way will still create binaries linking to libwinpthread-1.dll and so on by default.

Please note that the above two are orthogonal. You can even choose both.

from mingw-builds.

I'd say this is by design.

If you don't want binaries built with gcc to depend on libwinpthread-1.dll, link everything statically or use win32 thread model.

from mingw-builds.

Do you have any example of a build where everything is linked statically? I was not able to make it work. Built tooling was failing during runtime on missing dll.

It required some patches in the scripts though so I might have made some mistake there. (was trying to build x86_64-13.2.0-static-release-posix-seh-msvcrt-rt_v11-rev0 configuration)

from mingw-builds.

Pass -static to the linker, and you should get a self-contained executable.

from mingw-builds.

It didn't build. https://github.com/ugomancz/mingw-builds-binaries/actions/runs/8599000577/job/23560986589 Here is an example of the job.

from mingw-builds.

Wait, are you trying to link everything statically into gcc itself? That will be hard with little gain. Why do you want that?

from mingw-builds.

When the binaries are not running in an msys shell which would add the dll to PATH, the dll needs to be copied everywhere,

My use case is that I have another bin folder outside of the built mingw and I generate multiple binaries on multiple locations in workspace during runtime. So then there is quite a lot of copies of the dll.

from mingw-builds.

Linking everything statically into your programs

I guess the op needs just link only libwinpthread-1.dll statically only, keeping others as-is?

from mingw-builds.

Linking shared libstdc++ with static winpthreads is probably not going to work. In that case they both should be linked statically.

from mingw-builds.