Hi, > It's great to see the work done on improving the Maemo autopackager in > the Qt Creator nightlies, especially as pertains to packaging > libraries.
AFAIK, the nightly builds are the 2.1 branch. While there are improvements there as well, they are rather small compared to the work going on in the master branch. > I have a question, though. Currently, the Run feature > still expects to be able to execute some specific program (which > obviously won't exist in a library package), and thus fails to deploy > library packages at all. How is this planned to be handled in the > future? Simply fixing this issue would work, but ideally it would be > nice if "deployment" wasn't tied as tightly to "running/debugging" a > single app, since deployment/installation could then be handled more > generically. The master branch already has a "Deploy Project" action, which can exist without a run configuration. > Also, on an aside, is there any interest in extending the autopackager > plugin to produce packages for desktop platforms? I would assume that > for Debian-based systems, much of the current code might be > applicable, at least. Maemo is a platform with specific conventions, so we can make assumptions about the target device. For the desktop, the situation is much more complicated, because Creator is multi-platform: We can't provide a packaging feature just for Debian; we'd also have to support rpm-based Linux packages, Windows installers and whatever it is they use on Mac. Preferably supporting all kinds of cross compilers etc. You can add a suggestion in JIRA, but it probably won't get the highest priority. Christian _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
