Community
Participate
Working Groups
As a developer using Qt to build applications I want to be able to easily create new Qt projects, import existing Qt projects, build Qt projects, and debug Qt applications. This is an epic describing efforts to improve Qt development with CDT. Key elements include: A new CDT optional feature and new CDT plug-ins for Qt development. These would replace the Qt Eclipse integration currently available from Nokia. Tools for creating and importing Qt projects that have multiple build configurations supporting multiple versions of Qt. Synchronization of CDT projects and Qt project files. Users shouldn't have to directly modify QT project files for most use cases. A CDT builder and error parser for Qt projects. Ensuring the indexer is correctly and completely enabled for Qt projects. Qt project importer that will create CDT projects with multiple build configurations and include files from anywhere in the file system. Qt UI designer support will retain the design and features of the current integration, but will not require COM dll registration on Windows. The EDC Windows debugger will be brought up to production quality, optimized, and become the default for Qt projects. The above items will be broken down into more detailed stories that will refer to this bug.
We need to find a way to provide generic support for external build file generators, such as qmake. That would include running the generator when needed and setting up the configurations for the project based on what was generated. We could then reuse this for CMake and configure which are the most popular external build file generators that I know of.
Hmm, not sure why I assigned this to myself. My initial focus is on CMake. Whatever I do there should work for Qt as well (at least on the build side) but I'm not sure I'll get time to finish the job there.
Ah, maybe that's it. Fixing the component.
Hi Ken, is there anything new on the Nokia side about Qt support? I'm interested in this. How can I help? Has it been decided what will be kept from the existing integration? Should I start poking around the existing integration source code?
Interestingly enough, I have a commercial need for better Qt integration as well. Qt is popular with our Wind River Linux customers. I'll try to help where I can as I'll be focusing much more on TCF for the foreseeable future.
To start with we where thinking about taking most of the pieces from the current trolltech Qt plug-ins and get them into EPL CDT plug-ins (org.eclipse.cdt.qt...) so it will be easy for the CDT community to build on what's there already. We would like to have better builder integration and do some simple auto-discovery of Qt SDKs. I'll try to come up with a more concrete proposal for the CDT summit.
Cool. Sounds like the best place to start. I'll flesh out my build plans for the summit as well. We should be able to come up with a builder story that covers both CMake and qmake.
I am interested in cmake support (I believe Doug referred to it as "Advanced Makefile Support") at Eclipse Con 2013. Is this under active development now? Is it planned for the next release? If I am interested to help collaborating, whom should I work with?
No plans for the moment. It's been sidetracked by other things. Feel free to create a bug on cmake and start the discussion there.
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.
