#984 Executable when running outside C::B complains about missing libs

[Michel Le Bihan]

Hello,
In C::B 20.03 setup mingw fresh install with default settings, console app template, no build config changes when I build and run a simple Hello World from C::B everything works fine, but when I try to run the same executable outside of C::B by double clicking on it in Explorer or from terminal, it complains about missing libs. It's missing libstdc++-6.dll, libwinpthread-1.dll and libgcc_s_seh-1.dll. When doing the same in C::B 17.12 I can run the executable just fine.

This is very annoying. It's very common to run executables outside of C::B when testing, using the tool or distributing it. For every project I need to copy those from MinGW lib dir to the project bin dir. I think that C::B should either copy the libs automatically or make sure that the exectuable is statically linked.

[Teodor Petrov]

Sorry, complain about this to the vendor of the compiler you're using. C::B is an IDE, not compiler I don't think you'll want the IDE to do the copying automatically.

Some versions of GCC/mingw allow static linking to these libs, but then you'll have to check the licensing requirements when you do it.

You'll have this problem with any IDE which uses this compiler for building.