On Thu, Jun 14, 2012 at 3:14 AM, Andreas Pakulat <ap...@gmx.de> wrote:
> Hi, > > On Thu, Jun 14, 2012 at 8:13 AM, Till Oliver Knoll < > till.oliver.kn...@gmail.com> wrote: > >> >> >> Am 14.06.2012 um 01:52 schrieb Josiah Bryan <josiahbr...@gmail.com>: >> >> > ... >> > I'll double-check globals, but a stack trace is really what's needed >> > here anyway - debugger just says "Application exited with exit code >> > exit-code="03"" (Yes, I googled that - no, the only three results I >> > found did not help.) >> >> What compiler do you use? The MS Visual Studio compiler? If so, double >> check that you link against the proper C runtime libraries: debug vs >> release, single vs multithread support. Any mix can lead to spurious >> problems you have described. (Just a first rough guess) >> > > In particular make sure you use the same runtime as the Qt libraries. So > if your Qt links against the release runtime, your app has to do that too > (no matter wether you compile with or without debug-symbols) and > vice-versa. Qt debug libraries on Windows are usually having a 'd' suffix > in their name. > > I would expect qmake to take care of that though, when you switch your > .pro file from release to debug mode. > > I'm just using Qt Creator and (I assume) Mingw - I installed the Qt SDK with it's default settings, so however it configured Qt Creator - that's what I use. I would assume that Qt Creator / qmake is taking care of using the proper debug libraries, wouldn't it?
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
