Hi Tobias, Thanks for the explanation. The real problem is the "TARGET" variable isn't being picked up for the default run configuration if set in a .pri file. That's the only reason I was using a custom executable.
No worries, though. Moving the TARGET variable to the top-level .pro file fixes it. Cheers, ~ andy.f 2011/10/10 <[email protected]>: >> This appears to be a bug in QtCreator. When adding a custom run >> configuration, QtCreator uses CDB instead of the toolchain specified >> in the build configuration (mingw/gdb in my case). > > ... which is fixed in the 2.4 branch in > 5bfb5d9c324685dcb49753b42ee9a0f87e866bc5 > > We used to assume that we are running on the host, so the thing that is > running there > is compatible with the host's ABI. Since it may also be scripts and whatnot > we decided to > have the custom executable return a invalid ABI and have the debugger plugin > figure out > what to do. > > I hope that works better for you. > > Best Regards, > Tobias > > Tobias Hunger > Software Engineer > Nokia, Qt Development Frameworks > > Nokia gate5 GmbH > Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany > Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B > Umsatzsteueridentifikationsnummer: DE 812 845 193 > Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-creator > _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
