I posted this on Qt-Interest, but didn't get any responses, so I thought I'd try over here:
I'm switching a bunch of Qt apps I've written over from Visual Studio, to Qt Creator and I'm a little stumped on how to handle a Qt shared library with each Qt app with respect to how Qt Creator handles project files. So say I have the following setup: myLib - library of common classes used by all apps appFoo - one application based on myLib appBar - a second application based on myLib Originally I'd have two solutions, appFoo.sln and appBar.sln, each containing two Visual Studio .vcproj files, one project for the application (i.e. appFoo.vcproj), and one for the shared library (myLib.vcproj). Then, when building the solution it would check dependencies for both projects, building each as necessary. More importantly, when debugging I could debug both appFoo and myLib. This debugging feature is what I'm really trying to regain in Qt Creator - to build able to step into the code of both the application and the shared library. I have working .pro files for everything (i.e., myLib.pro, appFoo.pro, appBar.pro) and I can build everything separately, but if I open one of those individual .pro files, I don't see the application AND library files, just one or the other. Should I be creating a "solution" .pro file for each app, and use SUBDIRS? Something like: appFooSolution.pro: TEMPLATE = subdirs SUBDIRS = appFoo myLib appBarSolution.pro: TEMPLATE = subdirs SUBDIRS = appBar myLib Sean _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
