On Wed, May 22, 2013 at 9:14 PM, Preet <[email protected]> wrote: > Hiya, > > I noticed that when using the BlackBerry Kit with QtCreator (2.7), QtCreator > will create a bar-descriptor.xml file in my project's root directory. Right > now I'm building for desktop Linux and a Playbook, but say I end up adding > more targets, like Android, Ubuntu, Sailfish, etc. It seems like it might be > a bad idea to add target specific files all in the root directory... its > messy, and imagine a case where there's a generic 'config.xml' file that > multiple targets generate or something (or maybe the user has a config.xml > in their root directory for their own application!) > > I'm guessing what gets created where is plugin/kit specific, but I'd like to > suggest that platform specific assets get their own folder, or at least be > user configurable. Maybe something like > /projectdir/platforms/platform_name/platformasset.stuff or whatever the case > may be. > > Or maybe the suggested way of doing things is to manage separate platforms > as separate project files? Like... > desktop/myapp.pro > raspi/myapp.pro > blackberry/myapp.pro > > > > Regards, > > Preet > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator >
Close! Actually you can use .pri files for the platform-specific parts and then conditionally include them into the .pro file with the platform-agnostic parts, based on the selected makespec. /s/ Adam _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
