> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 03.04.2014 14:42, Koehne Kai wrote: > > Hi, > > > > Anyone knows by heart what to check for in a PE header to decide > > whether a dll is a debug build, or not? > > > > Background: Qt has a neat tool to package all of the Qt/non qt > > dependencies together for deployment: windeployqt. To function > > properly, it has to decide whether an executable/dll is a debug build, > > or not ... > > Why does it need to know whether a binary is a debug build or not?
Because in the Qt packages we go the 'MSVC way' in Qt and offer both a full debug build and a release build of our libraries side by side. You don't really want to package all of them by default though (the gcc debug binaries can be obscenely large). So given a binary, I need a hint what type of build it is. > Also, define "debug build"? -g? -O0? -DDEBUG=1? Well, in the MSVC world it's easy: A debug build is s.th. that depends on debug version of the MSVC runtime :) For my use case, I think actually any of the above would be 'good enough'. (Btw, what I'd _love_ to do actually is having a setup like it's common on Linux, where you've one set of libs/binaries, but stripped debug information besides. Never managed to get this working with MinGW though ... Anyone has experience with such a setup ?) Regards Kai ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
