On Nov 4, 2015, at 10:21 AM, Steve Atkins <[email protected]> wrote: > > >> On Nov 4, 2015, at 11:11 AM, [email protected] wrote: >> >> It would appear that the problem lies with running the macdeployqt script >> after build. If I don't run it, then I can debug my app - except that my app >> needs to be sandboxed, and if I sandbox the app but DON'T run macdeployqt, >> then the app crashes - probably because it doesn't have read access to the >> Qt libraries. Without sandboxing, I get weird behavior (specifically, it >> appears to be getting some settings from SOMEWHERE - using QSettings -, but >> for the life of me I can't figure out where), and it's not really a valid >> test anyway. So I'm a bit stumped here - unless I can somehow modify >> macdeployqt to prevent breaking debugging? > > macdeployqt --help says: > > -no-strip : Don't run 'strip' on the binaries > -use-debug-libs : Deploy with debug versions of frameworks and plugins > (implies -no-strip)
Thanks. The -no-strip did the trick. For some reason -use-debug-libs prevent the package from being properly code signed, so the resulting application couldn't be sandboxed, but just using the -no-strip should be good enough. Strange that I never had to do that before though. Oh well. > > Cheers, > Steve > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
