Update: So I've found out that codeblocks does link this statically. I was thrown off because I thought the "full command line" build log reflected all the commands sent to gcc. I learned to program using IDEs and now I'm finding out what they're doing in the background without telling me!
Ok, so when I build a simple c++ program through codeblocks which includes <iostream>, the executable runs just fine on its' own with no apparent runtime dependencies.
But why? libstdc++6.dll is not in the executable path nor the project path and there's no static linking going on in the build log.
Is codeblocks silently telling my linker to link libstdc++ statically? (and what about libstdc++'s own runtime dependencies?) How is this getting linked? Is codeblocks omitting things from the build log?
I'm just trying to get a deeper understanding of what exactly is happening.