you are right, I meant the -g option, "produce debugging symbols". I was not talking about the d prefix.
My main focus between debug/release was the debug symbols, though, not so much the differences in CRT. Maybe thats why I was confused by some of the statements before. But I understand the difference with the C-runtime libs. I also understand the differences of the CRTs, maybe I just did not honour those differences high enough.
However, up to now I convinced that the main reason for the huge size difference between a wxWidget debug lib and a runtime lib (5Mb vs. 30Mb) was not due to the differences in CRT release vs. CRT debug, but due to the symbols included.
The only difference is between debug/release on Linux is that debug build does not strip the symbols from the binaries. But the binaries are exactly bthe same.
Yes, but isn't that obvious? And am I wrong to expect this difference to be similar as in Windows (like a ration ~5MB/30MB)?
If it is right, I am lost because that would mean
a) nobody uses wxWidgets debugging symbols and that is the reason the installation instructions to not explain how to build them.
b) people are using it, but making their live unnecessary difficult by removing an easy way to create them (the --enable-debug option) and an easy way to put them in the same directory as the "normal" libs (aka the "d" prefix").
c) symbold are included by default and everyone keeps the debugging symbols in and ship them with the production code, because code execution is not changed.
I think c) is wrong, because the files I am getting seem to small. But still a) and b) seem stange to me.
I like this slightly confusing but interesting topic because it shows how much the apporaches differ between developing IDE-based or command line based. I my IDE I would create a new target with the gcc option "Produce debugging symbols (-g)" checked and would not think any more about it. On windows I acutally build me a project file for C::B, but I think Linux woudl be a lot more complex with the dependencies (jpeg, tiff, etc).
What would help me most at this point is to understand the command lines required to build wxWidgets with debugging symbold included.