Re: [Qt-creator] New EnvironmentId variable in .creator.user files
On 17.09.2010 20:33, ext Bryce Schober wrote: I'm extremely disappointed. I'm using Qt Creator exclusively for generic Makefile development. It has had its warts for that purpose, but this makes it much worse, because now there is no way for me to share build configurations with others. What could be done to improve your use case? So you just want a set of additional make targets to be (pre-)defined for users as well as a list of things that can be run? Would it help if we added some more files to make those known to creator? This is going to completely kill my usage scenario if it continues. What is you usage scenario? From our point of view we are not continuing, but just made our users aware about something that has never worked before. We had lots of complaints about trouble due to sharing a .user-file. Since there is little we can do to make it share better we had to at least provide a warning. Maybe this is just one of those you're not our customer situations, but it's pretty disappointing. Now generic project support is even more of an orphan than it was. We are willing to accept merge requests to improve any part of creator including the different build system integrations. Unfortunately we do not have much time ourselves to improve the generic project support:-( Some of us are using the generic project to contribute to open source projects that are not qmake based, so it is regularly excersied and tested and we do make sure to not break those use cases. Best Regards, Tobias -- Tobias Hunger Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] get current active editor
hi all, how can I get current active editor in my own qt-creator plugin? of couse, a qt-creator had opened a txt/cpp file. thanks ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] how to change .gdbinit of qtcreator
Hi, I am currently debugging webkit with qtcreator, this requires change in .gdbinit, Here is the code I want to change in .gdbinit. GDB support for WebKit types. Add this to your gdb by amending your ~/.gdbinit as follows: python import sys sys.path.insert(0, /path/to/tools/gdb/) import webcore So Where can I find the .gdbinit of qtcreator? for more details please visit below link, http://trac.webkit.org/wiki/GDB Thanks, Sunny ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] The last two weeks in Creator
Hello! We managed to skip last weeks report (again), so today we have two weeks worth of changes for you: ---++ Nokia Qt SDK * Nokia Qt SDK version 1.0.1 was released. It includes Qt Creator 2.0.1. See: http://labs.qt.nokia.com/2010/09/14/nokia-qt-sdk-101-released/ ---++ Designer * Support for QIcon::theme was added to Designer: Use the icons from your preferred theme! This will become available in Qt 4.8. ---++ Generic * Creator can now auto-restore the last open session. This can be done either globally via the UI (File-Session-Session Manager, check Restore last session there) or for the next start only via the command line switch -lastsession. * Generic Highlighting and what it can do was blogged about: http://labs.qt.nokia.com/2010/09/16/generic-highlighter-in-qt-creator/ ---++ Qmake * Project wizards were extended to make the generated .pro-files more usable for use in SUBDIRS pro-files. * New wizard to help with adding new library dependencies to .pro-files. ---++ Symbian * Deployment of shared libraries to Symbian devices should finally work. Some wizard to set up the deployment-related .pro-file section still needs to get added. * Deployment of SUBDIRS projects to Symbian devices does work now. ---++ Maemo * QML and Mobile wizards were steamlined and improved for Maemo development. ---++ Debugging * The thread list in the debugger can now display thread names. One source of those names is the objectName ot QThreads. * Loading of gdb was optimized (Linux only). ---++ Documentation * Many new features found in QtCreator master were documented. Check your documentation for all the awesomeness;-) ---++ Nightly Builds * Our build system infrastructure was much improved. * Nightly builds of the master branch are now available at: ftp://ftp.qt.nokia.com/qtcreator/snapshots/ All work (except for the Designer part!) happened on the master branch available here: http://qt.gitorious.org/qt-creator Please feel free to give it a try:-) Please report any issues you run into or suggestions for improvements here: http://bugreports.qt.nokia.com/ Best Regards, Tobias -- Tobias Hunger Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] The last two weeks in Creator
On Mon, Sep 20, 2010 at 03:25, Tobias Hunger tobias.hun...@nokia.com wrote: Hello! We managed to skip last weeks report (again), so today we have two weeks worth of changes for you: ---++ Nokia Qt SDK * Nokia Qt SDK version 1.0.1 was released. It includes Qt Creator 2.0.1. See: http://labs.qt.nokia.com/2010/09/14/nokia-qt-sdk-101-released/ ---++ Designer * Support for QIcon::theme was added to Designer: Use the icons from your preferred theme! This will become available in Qt 4.8. ---++ Generic * Creator can now auto-restore the last open session. This can be done either globally via the UI (File-Session-Session Manager, check Restore last session there) or for the next start only via the command line switch -lastsession. * Generic Highlighting and what it can do was blogged about: http://labs.qt.nokia.com/2010/09/16/generic-highlighter-in-qt-creator/ ---++ Qmake * Project wizards were extended to make the generated .pro-files more usable for use in SUBDIRS pro-files. * New wizard to help with adding new library dependencies to .pro-files. ---++ Symbian * Deployment of shared libraries to Symbian devices should finally work. Some wizard to set up the deployment-related .pro-file section still needs to get added. * Deployment of SUBDIRS projects to Symbian devices does work now. ---++ Maemo * QML and Mobile wizards were steamlined and improved for Maemo development. ---++ Debugging * The thread list in the debugger can now display thread names. One source of those names is the objectName ot QThreads. * Loading of gdb was optimized (Linux only). ---++ Documentation * Many new features found in QtCreator master were documented. Check your documentation for all the awesomeness;-) ---++ Nightly Builds * Our build system infrastructure was much improved. * Nightly builds of the master branch are now available at: ftp://ftp.qt.nokia.com/qtcreator/snapshots/ Awesome! This is much appreciated, and will be a big time-saver, given that my work-flow depends on the ever-improving Maemoisms in Creator. Out of curiousity (I'm not complaining, just wondering), is there a technical reason why the Linux nightlies seem to lag the Win/Mac builds by a couple of days? Thanks, - Jeffery MacEachern All work (except for the Designer part!) happened on the master branch available here: http://qt.gitorious.org/qt-creator Please feel free to give it a try:-) Please report any issues you run into or suggestions for improvements here: http://bugreports.qt.nokia.com/ Best Regards, Tobias -- Tobias Hunger Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] The last two weeks in Creator
On 9/20/2010 12:39 PM, ext Jeffery MacEachern wrote: On Mon, Sep 20, 2010 at 03:25, Tobias Hungertobias.hun...@nokia.com wrote: Hello! We managed to skip last weeks report (again), so today we have two weeks worth of changes for you: ---++ Nokia Qt SDK * Nokia Qt SDK version 1.0.1 was released. It includes Qt Creator 2.0.1. See: http://labs.qt.nokia.com/2010/09/14/nokia-qt-sdk-101-released/ ---++ Designer * Support for QIcon::theme was added to Designer: Use the icons from your preferred theme! This will become available in Qt 4.8. ---++ Generic * Creator can now auto-restore the last open session. This can be done either globally via the UI (File-Session-Session Manager, check Restore last session there) or for the next start only via the command line switch -lastsession. * Generic Highlighting and what it can do was blogged about: http://labs.qt.nokia.com/2010/09/16/generic-highlighter-in-qt-creator/ ---++ Qmake * Project wizards were extended to make the generated .pro-files more usable for use in SUBDIRS pro-files. * New wizard to help with adding new library dependencies to .pro-files. ---++ Symbian * Deployment of shared libraries to Symbian devices should finally work. Some wizard to set up the deployment-related .pro-file section still needs to get added. * Deployment of SUBDIRS projects to Symbian devices does work now. ---++ Maemo * QML and Mobile wizards were steamlined and improved for Maemo development. ---++ Debugging * The thread list in the debugger can now display thread names. One source of those names is the objectName ot QThreads. * Loading of gdb was optimized (Linux only). ---++ Documentation * Many new features found in QtCreator master were documented. Check your documentation for all the awesomeness;-) ---++ Nightly Builds * Our build system infrastructure was much improved. * Nightly builds of the master branch are now available at: ftp://ftp.qt.nokia.com/qtcreator/snapshots/ Awesome! This is much appreciated, and will be a big time-saver, given that my work-flow depends on the ever-improving Maemoisms in Creator. Out of curiousity (I'm not complaining, just wondering), is there a technical reason why the Linux nightlies seem to lag the Win/Mac builds by a couple of days? The build machine ran out of disk space. Linux builds should be at their usual place in about an hour. Cheers, Daniel -- Daniel Molkentin, Software Engineer, Nokia, Qt Development Frameworks website: http://qt.nokia.com Rudower Chaussee 13, DE-12489 Berlin Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] how to change .gdbinit of qtcreator
On Monday 20 September 2010 12:17:55 ext sunny shah wrote: Hi, I am currently debugging webkit with qtcreator, this requires change in .gdbinit, Here is the code I want to change in .gdbinit. GDB support for WebKit types. Add this to your gdb by amending your ~/.gdbinit as follows: python import sys sys.path.insert(0, /path/to/tools/gdb/) import webcore So Where can I find the .gdbinit of qtcreator? There is no .gdbinit of qtcreator, the gdb session started from Qt Creator will read .gdbinit on its own. for more details please visit below link, http://trac.webkit.org/wiki/GDB This looks like your goal is to make Webkit data types visible in Qt Creator. If so, http://doc.qt.nokia.com/qtcreator-snapshot/creator-debugging-helpers.html might help to get you started. Andre' ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] New EnvironmentId variable in .creator.user files
Without wanting to say anything on behalf of others, let me just give my personal 2 cents. We develop based on CMake projects with a group of people and with shadow builds. Most of us use Qt Creator, this works quite well. The only thing that is a hassle is the .user file and the settings therein. When we quickly want to hand over a project, we pack the root directory of the source tree, i.e., the one that also holds the CMakeLists.txt. Unfortunately, also the CMakeLists.txt.user file is located here, and hence it gets distributed. This is a pain, because the build-directory and run-working-directory could (so far) not be defined relative to a user-defined location and/or an environment variable. Fortunately, this has been fixed quickly after I reported this (http://bugreports.qt.nokia.com/browse/QTCREATORBUG-2377), thanks for that. From the discussion above, I have learned that we should just not distribute the .user file. From my perspective, it would be preferable to have the build settings and run settings removed from the .user file and store these in separate files like you suggested, which then can be saved in the source tree. I would suggest then that the .user file is stored in the build directory, not in the source tree. I will consider making patches if this is something that people would like to have. However, I am not familiar with the internals of Qt Creator so far, so it would take me a while and I'm not sure about the quality... Regards, Theo. 2010/9/20 Tobias Hunger tobias.hun...@nokia.com: On 17.09.2010 20:33, ext Bryce Schober wrote: I'm extremely disappointed. I'm using Qt Creator exclusively for generic Makefile development. It has had its warts for that purpose, but this makes it much worse, because now there is no way for me to share build configurations with others. What could be done to improve your use case? So you just want a set of additional make targets to be (pre-)defined for users as well as a list of things that can be run? Would it help if we added some more files to make those known to creator? This is going to completely kill my usage scenario if it continues. What is you usage scenario? From our point of view we are not continuing, but just made our users aware about something that has never worked before. We had lots of complaints about trouble due to sharing a .user-file. Since there is little we can do to make it share better we had to at least provide a warning. Maybe this is just one of those you're not our customer situations, but it's pretty disappointing. Now generic project support is even more of an orphan than it was. We are willing to accept merge requests to improve any part of creator including the different build system integrations. Unfortunately we do not have much time ourselves to improve the generic project support:-( Some of us are using the generic project to contribute to open source projects that are not qmake based, so it is regularly excersied and tested and we do make sure to not break those use cases. Best Regards, Tobias -- Tobias Hunger Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] New EnvironmentId variable in .creator.user files
From my perspective, it would be preferable to have the build settings and run settings removed from the .user file and store these in separate files like you suggested, which then can be saved in the source tree. I would suggest then that the .user file is stored in the build directory, not in the source tree. I like your thinking, but the build directory isn't a singular location. Creator uses different build directories based on what you're building for, to allow you to have (for example) a desktop build and a mobile simulator build. /s/ Adam ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] New EnvironmentId variable in .creator.user files
Well, I wasn't planning on a treatise, but I guess that's what we got: On Mon, Sep 20, 2010 at 1:24 AM, Tobias Hunger tobias.hun...@nokia.comwrote: What is you usage scenario? I'm using Qt Creator alongside a complex set of legacy makefiles. Their arrangement isn't straightforward to something like Qt Creator, but works ok from the command line if you can remember where you need to be in the multi-product/multi-target hierarchy. Each product has its own Makefile, with usually at least two different applications for that product, each linking in a common boot-loader that is built separately. Because of this complexity of targets for each product, we also have a top-level Makefile that is used to organize them, so that the user can simply make all targets for product foo, building the individual applications, linking them to the boot-loader, and creating all the final deliverables. So I eventually decided to create one Qt Creator project for each low-level target, which means that for a simple product with two applications and a shared boot-loader, I have three different projects. This decision was driven by a couple factors. First, Qt Creator's highlighting and find features enforce a very narrow perspective of the source code. This has very distinct benefits, which I like. But it also has the drawback of pushing me to separate projects for each application target, even if the only difference is Makefile-driven command-line #defines. (Qt Creator doesn't have per-configuration includes or defines, unlike some IDEs). Fortunately, each of these targets already had separate output directories and automatic dependency generation. So I wrote a shell script that slurps up all the source dependency information and updates the project.files list. This works reasonably well, but has to warn the user to re-load the project.files file, since that isn't re-loaded automatically. Because it's an extra warning, I hid that from non-Qt-creator users by doing the project.files update as a separate build step. What could be done to improve your use case? It would be nice to prompt to re-load project files when edited externally, even if they're not open. Then my project file updating could be silent on the command line. The sheer number of projects resulting from the above constraints is a bit overwhelming, and if they had to be set up by each user in each of their branch sandboxes, using Qt creator for frequent development would never get off the ground. Also, as you'll note above, the application gets built separately from the boot-loader, and then linked as a new combined target. This leads to a lot of inter-project dependencies that are currently impossible to share between users. This is actually what has stalled my roll-out of Qt Creator as the preferred IDE for developers in our organization. Qt Creator really needs some way to express a workspace of project and their dependencies in a way that can be resident in the source tree and independent of physical location. I'm really conflicted about Qt Creator, because it has so much to offer as an clean simple editor, but also with the sophistication that can make the developer's like so much easier with good code completion, refactoring, and a good debugger interface. But as I continue to use it and live with the warts that keep me from promoting it to everyone, I feel that its roots may just be too deeply rooted in the Qt world to work for us (without converting all our Makefiles to QMake). Its handling of Makefile projects is decidedly second-class, and that makes perfect sense, as its primary purpose is as a QT IDE. I guess the compromises are what keep it from becoming the bloated whale that is Eclipse. I would *so much* like it to be able to be a better general-purpose C/C++ IDE, but I simply can't justify spending much more time with it. -- Bryce Schober P.S. If we hypothetically did convert our Makefiles to use QMake and Qt Creator for active development, would that obligate us under the full Qt licensing scheme, or not? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] New EnvironmentId variable in .creator.user files
P.S. If we hypothetically did convert our Makefiles to use QMake and Qt Creator for active development, would that obligate us under the full Qt licensing scheme, or not? Of course not, not any more than you're subject to the license of GNU Make if you use that to compile your application. Obviously you have to comply with the licensing if you're distributing qmake and Creator themselves but the products you produce using them don't include any part of the build tools themselves. /s/ Adam ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] The last two weeks in Creator
---++ Qmake * Project wizards were extended to make the generated .pro-files more usable for use in SUBDIRS pro-files. * New wizard to help with adding new library dependencies to .pro-files. Just had a quick play with the library wizard. This is a HUGE step forward for Creator! ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
