[Qt-creator] Qt Creator for Python
Hi folks, Recently I forced to do some web interfaces for one of my projects so I decided to learn Python because -as I read- it's easy language to learn which supports web applications (in addition to GUI/Qt application) so I need to know the following: 1. Does Qt Creator supports Python (I'm sure 99.999% it's not because I'm using it since earlier versions)? 2. Are there any plans for supporting Python in future? 3. What's most alternative IDE to Qt Creator for Python? -- Best Regards Muhammad Bashir Al-Noimi My Blog: http://mbnoimi.net ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Building Debugging Helper library error
On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote: On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote: I'm having problems getting Qt Debugger libraries to build. Environment - Creator 2.0 built from source Qt 4.7 built from source Windows XP Nokia N97 SDK I have %epocroot% set to \ Creator is run from the command line at C:\git\creator2.0\bin You do not need the compiled debugging helpers for neither Symbian nor Windows/MinGW deverlopment. They have been replaced by Python scripts that do not need compilation. The problem I'm facing is that Creator Projects Build Settings Qt Version isn't listing all the Qt installations listed under Tools Options Qt4. The Projects tab within Creator allows general Build Settings to be set. One such setting is the Qt Version to use when building. The only Qt Versions listed are Qt installations where the helper library is built. At least it seems that way. I didn't know that Creator used devices.xml to auto-detect SDKs. I thought it really was auto-detecting them. I have changed devices.xml to use the the subst drive rather than the full path of the actual loation. I know have a different error message which I think is reated to the compiler and not Qt. However, there's another problem: Problem - In the Tools Options Qt4 window of Creator, varous Qt versions are listed split into two categories 1) Auto-detected, 2) Manual Under Auto-detected Creator has found Nokia_N97_v1.0(Qt 4.7). This is accurate since I have installed the Nokia N97 SDK and subst it to a drive V: such that the epoc32 is V:\epoc32 I have also created V:\git\qt, where the src for QT 4.7 lives. Creator seems to have detected all of this fine. SDK installed to D:\Nokia\, so that the epocroot is D:\Nokia\Nokia_N97_SDK_v1.0\epoc32 The SDK is subst to V:\, so that the epocroot is V:\epoc32 Qt src lives (and is built from) V:\git\qt The Symbian toolchain pretty much relies on everything being on the same drive. There are some exception, but as a rule of thumb you should avoid this kind of setup. If ayone has any advice on what I can do to resolve the problem, it would be very helpful. Try to re-install everything to the same drive. Everything is on one drive. The SDK and At 4.7 both exist on the subst drive V. Creator auto-detects the SDK under the S60 SDKs as being on V. I guess the confiusion is becuase devices.xml listed the epocroot as D:\Nokia\Nokia_N97_SDK_v1.0\ and not V:\. Smae with epoctools. Andre' ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator -- Regards Jack ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Creator for Python
Bashir: Among the free alternatives out there you can take a look at Eric4 Python IDE if you plan on using Python and the PyQt wrappers at the URL below: http://eric-ide.python-projects.org For wxWidgets development (although I doubt you plan on using the wxWidgets toolkit) I only know of BoaConstructor, which uses the corresponding wxPython wrappers, located here: http://sourceforge.net/projects/boa-constructor/files Other commercial IDEs have very nice features, such as the Komodo IDE, but it doesn't really support GUI development. Komodo IDE supports almost all the major scripting languages, and have very nice features for team development as well. They used to have a GUI builder, but do not support it any longer. You can get more information at this URL: http://www.activestate.com/komodo/ Good luck in your endeavours, Victor On 5/10/10 11:39 PM, M. Bashir Al-Noimi wrote: Hi folks, Recently I forced to do some web interfaces for one of my projects so I decided to learn Python because -as I read- it's easy language to learn which supports web applications (in addition to GUI/Qt application) so I need to know the following: 1. Does Qt Creator supports Python (I'm sure 99.999% it's not because I'm using it since earlier versions)? 2. Are there any plans for supporting Python in future? 3. What's most alternative IDE to Qt Creator for Python? ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator attachment: victor_sardina.vcf___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Creator 2.0 branch requires latest qt.git/4.7
Hi, Because of a change in qt.git/4.7 in the QtDeclarative module we had to patch creator/2.0 branch. Commit 74a615fbeec95786dfc3d85a667e994f731b73dd will hit the public repo with the usual 12 hour delay. Once you pull this commit, you've to update also your qt ... Regards Kai -- Kai Köhne Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443B 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] Qt Creator for Python
On Tuesday 11 May 2010 11:39:15 ext M. Bashir Al-Noimi wrote: Hi folks, Recently I forced to do some web interfaces for one of my projects so I decided to learn Python because -as I read- it's easy language to learn which supports web applications (in addition to GUI/Qt application) so I need to know the following: 1. Does Qt Creator supports Python (I'm sure 99.999% it's not because I'm using it since earlier versions)? 2. Are there any plans for supporting Python in future? 3. What's most alternative IDE to Qt Creator for Python? There is no real Python support in Creator. However, there is some generic syntax highlighter in the works that also covers Python, and Creator's debugger plugin already talks to pdb (the Python debugger) pretty much the same way it uses gdb for C++. Depending on your needs that might count as some Python support. Code completion would of course be nice, but I guess that'd be a nice Creative Weekend project for a external contributor. Andre' ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Building Debugging Helper library error
On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote: On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote: On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote: I'm having problems getting Qt Debugger libraries to build. Environment - Creator 2.0 built from source Qt 4.7 built from source Windows XP Nokia N97 SDK I have %epocroot% set to \ Creator is run from the command line at C:\git\creator2.0\bin You do not need the compiled debugging helpers for neither Symbian nor Windows/MinGW deverlopment. They have been replaced by Python scripts that do not need compilation. The problem I'm facing is that Creator Projects Build Settings Qt Version isn't listing all the Qt installations listed under Tools Options Qt4. The Projects tab within Creator allows general Build Settings to be set. One such setting is the Qt Version to use when building. The only Qt Versions listed are Qt installations where the helper library is built. At least it seems that way. It lists the Qt Versions that match the Target architecture of the target you have selected (probably Desktop ?). If you have Qt Versions installed (and known to Qt Creator) that make it possible to develop for multiple targets, your Projects mode should have tabs Targets, Editor Settings and Dependencies. Similar to http://doc.qt.nokia.com/qtcreator-snapshot/creator-building-running.html#building-for-symbian If you want to compile for a different target than shown in the tabs on the Targets page, e.g. Symbian devices, you need to add a target (press + next to the Desktop tab). I didn't know that Creator used devices.xml to auto-detect SDKs. I thought it really was auto-detecting them. Define really auto-detecting :) Regards, -- Eike Ziller 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] Building Debugging Helper library error
On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote: On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote: On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote: On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote: I'm having problems getting Qt Debugger libraries to build. Environment - Creator 2.0 built from source Qt 4.7 built from source Windows XP Nokia N97 SDK I have %epocroot% set to \ Creator is run from the command line at C:\git\creator2.0\bin You do not need the compiled debugging helpers for neither Symbian nor Windows/MinGW deverlopment. They have been replaced by Python scripts that do not need compilation. The problem I'm facing is that Creator Projects Build Settings Qt Version isn't listing all the Qt installations listed under Tools Options Qt4. The Projects tab within Creator allows general Build Settings to be set. One such setting is the Qt Version to use when building. The only Qt Versions listed are Qt installations where the helper library is built. At least it seems that way. It lists the Qt Versions that match the Target architecture of the target you have selected (probably Desktop ?). If you have Qt Versions installed (and known to Qt Creator) that make it possible to develop for multiple targets, your Projects mode should have tabs Targets, Editor Settings and Dependencies. Ok, that makes sense. I've added a target Symbian Device and in this scenario the Qt Version which is listed is Nokia_N97_SDK(Qt 4.7.0). So that means you're correct, and my idea of it being dictated by the debugger library faling to build, was definitely wrong. However I don't really want to build for a device, I want to build for the emulator in the SDK. So the build process should use abld, but the target should be winscw and not armv5. It seems that when I add a Symbian Device as a target, Creator will only build it for armv5. Does creator even know where epoc.exe is or is capable of launching the emulator? Similar to http://doc.qt.nokia.com/qtcreator-snapshot/creator-building-running.html#building-for-symbian If you want to compile for a different target than shown in the tabs on the Targets page, e.g. Symbian devices, you need to add a target (press + next to the Desktop tab). I didn't know that Creator used devices.xml to auto-detect SDKs. I thought it really was auto-detecting them. Define really auto-detecting :) OK. Good point. I assumed (bad I know) that it may have scanned for epoc32 or something like that. Regards, -- Eike Ziller 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 -- Regards Jack ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Building Debugging Helper library error
On May 11, 2010, at 2:37 PM, ext Jack Wootton wrote: On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote: On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote: On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote: On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote: I'm having problems getting Qt Debugger libraries to build. Environment - Creator 2.0 built from source Qt 4.7 built from source Windows XP Nokia N97 SDK I have %epocroot% set to \ Creator is run from the command line at C:\git\creator2.0\bin You do not need the compiled debugging helpers for neither Symbian nor Windows/MinGW deverlopment. They have been replaced by Python scripts that do not need compilation. The problem I'm facing is that Creator Projects Build Settings Qt Version isn't listing all the Qt installations listed under Tools Options Qt4. The Projects tab within Creator allows general Build Settings to be set. One such setting is the Qt Version to use when building. The only Qt Versions listed are Qt installations where the helper library is built. At least it seems that way. It lists the Qt Versions that match the Target architecture of the target you have selected (probably Desktop ?). If you have Qt Versions installed (and known to Qt Creator) that make it possible to develop for multiple targets, your Projects mode should have tabs Targets, Editor Settings and Dependencies. Ok, that makes sense. I've added a target Symbian Device and in this scenario the Qt Version which is listed is Nokia_N97_SDK(Qt 4.7.0). So that means you're correct, and my idea of it being dictated by the debugger library faling to build, was definitely wrong. However I don't really want to build for a device, I want to build for the emulator in the SDK. So the build process should use abld, but the target should be winscw and not armv5. It seems that when I add a Symbian Device as a target, Creator will only build it for armv5. Does creator even know where epoc.exe is or is capable of launching the emulator? 1) You need to point Qt Creator to your Carbide.c++ installation (which contains the necessary tool chain). To do that, open Tools-Options-Qt-Versions, select the Qt Version and point Carbide path to the Carbide install. 2) Add a target Symbian Emulator to your project Hope that helps, Eike Similar to http://doc.qt.nokia.com/qtcreator-snapshot/creator-building-running.html#building-for-symbian If you want to compile for a different target than shown in the tabs on the Targets page, e.g. Symbian devices, you need to add a target (press + next to the Desktop tab). I didn't know that Creator used devices.xml to auto-detect SDKs. I thought it really was auto-detecting them. Define really auto-detecting :) OK. Good point. I assumed (bad I know) that it may have scanned for epoc32 or something like that. Regards, -- Eike Ziller 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 -- Regards Jack ATT1..txt -- Eike Ziller 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] Building Debugging Helper library error
On May 11, 2010, at 2:59 PM, ext Eike Ziller wrote: On May 11, 2010, at 2:37 PM, ext Jack Wootton wrote: On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote: On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote: On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote: On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote: I'm having problems getting Qt Debugger libraries to build. Environment - Creator 2.0 built from source Qt 4.7 built from source Windows XP Nokia N97 SDK I have %epocroot% set to \ Creator is run from the command line at C:\git\creator2.0\bin You do not need the compiled debugging helpers for neither Symbian nor Windows/MinGW deverlopment. They have been replaced by Python scripts that do not need compilation. The problem I'm facing is that Creator Projects Build Settings Qt Version isn't listing all the Qt installations listed under Tools Options Qt4. The Projects tab within Creator allows general Build Settings to be set. One such setting is the Qt Version to use when building. The only Qt Versions listed are Qt installations where the helper library is built. At least it seems that way. It lists the Qt Versions that match the Target architecture of the target you have selected (probably Desktop ?). If you have Qt Versions installed (and known to Qt Creator) that make it possible to develop for multiple targets, your Projects mode should have tabs Targets, Editor Settings and Dependencies. Ok, that makes sense. I've added a target Symbian Device and in this scenario the Qt Version which is listed is Nokia_N97_SDK(Qt 4.7.0). So that means you're correct, and my idea of it being dictated by the debugger library faling to build, was definitely wrong. However I don't really want to build for a device, I want to build for the emulator in the SDK. So the build process should use abld, but the target should be winscw and not armv5. It seems that when I add a Symbian Device as a target, Creator will only build it for armv5. Does creator even know where epoc.exe is or is capable of launching the emulator? 1) You need to point Qt Creator to your Carbide.c++ installation (which contains the necessary tool chain). To do that, open Tools-Options-Qt-Versions, select the Qt Version and point Carbide path to the Carbide install. 2) Add a target Symbian Emulator to your project And to do some advertising for a better world ;) What about trying the Nokia Qt SDK beta, with the shiny new Qt Simulator? http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/IDEs/Nokia_Qt_SDK/ Best regards, Eike Similar to http://doc.qt.nokia.com/qtcreator-snapshot/creator-building-running.html#building-for-symbian If you want to compile for a different target than shown in the tabs on the Targets page, e.g. Symbian devices, you need to add a target (press + next to the Desktop tab). I didn't know that Creator used devices.xml to auto-detect SDKs. I thought it really was auto-detecting them. Define really auto-detecting :) OK. Good point. I assumed (bad I know) that it may have scanned for epoc32 or something like that. -- Eike Ziller 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] QtCreator 2.0 and wildcards on project files
Thanks for that tip! By the way I filed a bug with a sample project already. On Sat, May 8, 2010 at 3:12 AM, Bradley Smith brad...@baysmith.com wrote: I noticed the same problem and found that a workaround may be to use $ $files. For example, try HEADERS += $$files(./inc/*.h) ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator -- Gustavo Federico Bett ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Building Debugging Helper library error
I didn't realise Creator require Carbide to run the emualtor. At least now I have a Symbian Emulator target. thank you for the help on that. Now I get an error when building the project, related to the Meta Object creation files I think. myFile.cpp contains the Q_OBJECT macro since it contains signals and slots. This seems to be causing a problem: :: error: [myFile.cpp] Error -1073741515 regarding the Nokia SDK, a colleague is currently trying that out, however they have run into problems: 1. (Known bug) To uninstal the SDK the Nokia server is contacted, and that can't be done through our firewall. So we were unable to uninstall it. 2. (Known bug) You update the SDK through the firewall. 3. The following code causes an error in Creator. The troublesome source code is simply: // import Qt 4.7 import org.webkit 1.0 // And the exact error is: // Starting D:\qt\projects\qml\locator- build\debug\locator.exe... qrc:mainwindow.qml:2:1: module org.webkit is not installed // My colleague has attmepted two different configurations: 1. Nokia Qt SDK beta, targeting the Symbian simulator 2. Qt 4.7 beta, targeting Windows Both using Qt Creator 2.0 beta (though it’s reported as 1.3.83) and both installed using the binaries. The only real problem is point 3, since if the webkit error wasn't present, there would be no need to uninstall it. On Tue, May 11, 2010 at 2:03 PM, Eike Ziller eike.zil...@nokia.com wrote: On May 11, 2010, at 2:59 PM, ext Eike Ziller wrote: On May 11, 2010, at 2:37 PM, ext Jack Wootton wrote: On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote: On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote: On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote: On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote: I'm having problems getting Qt Debugger libraries to build. Environment - Creator 2.0 built from source Qt 4.7 built from source Windows XP Nokia N97 SDK I have %epocroot% set to \ Creator is run from the command line at C:\git\creator2.0\bin You do not need the compiled debugging helpers for neither Symbian nor Windows/MinGW deverlopment. They have been replaced by Python scripts that do not need compilation. The problem I'm facing is that Creator Projects Build Settings Qt Version isn't listing all the Qt installations listed under Tools Options Qt4. The Projects tab within Creator allows general Build Settings to be set. One such setting is the Qt Version to use when building. The only Qt Versions listed are Qt installations where the helper library is built. At least it seems that way. It lists the Qt Versions that match the Target architecture of the target you have selected (probably Desktop ?). If you have Qt Versions installed (and known to Qt Creator) that make it possible to develop for multiple targets, your Projects mode should have tabs Targets, Editor Settings and Dependencies. Ok, that makes sense. I've added a target Symbian Device and in this scenario the Qt Version which is listed is Nokia_N97_SDK(Qt 4.7.0). So that means you're correct, and my idea of it being dictated by the debugger library faling to build, was definitely wrong. However I don't really want to build for a device, I want to build for the emulator in the SDK. So the build process should use abld, but the target should be winscw and not armv5. It seems that when I add a Symbian Device as a target, Creator will only build it for armv5. Does creator even know where epoc.exe is or is capable of launching the emulator? 1) You need to point Qt Creator to your Carbide.c++ installation (which contains the necessary tool chain). To do that, open Tools-Options-Qt-Versions, select the Qt Version and point Carbide path to the Carbide install. 2) Add a target Symbian Emulator to your project And to do some advertising for a better world ;) What about trying the Nokia Qt SDK beta, with the shiny new Qt Simulator? http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/IDEs/Nokia_Qt_SDK/ Best regards, Eike Similar to http://doc.qt.nokia.com/qtcreator-snapshot/creator-building-running.html#building-for-symbian If you want to compile for a different target than shown in the tabs on the Targets page, e.g. Symbian devices, you need to add a target (press + next to the Desktop tab). I didn't know that Creator used devices.xml to auto-detect SDKs. I thought it really was auto-detecting them. Define really auto-detecting :) OK. Good point. I assumed (bad I know) that it may have scanned for epoc32 or something like that. -- Eike Ziller Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Re: [Qt-creator] Building Debugging Helper library error
Sorry, the error message was inaccurate; it should have read :: error: [moc_myFile.cpp] Error -1073741515 On Tue, May 11, 2010 at 2:33 PM, Jack Wootton jackwoot...@gmail.com wrote: I didn't realise Creator require Carbide to run the emualtor. At least now I have a Symbian Emulator target. thank you for the help on that. Now I get an error when building the project, related to the Meta Object creation files I think. myFile.cpp contains the Q_OBJECT macro since it contains signals and slots. This seems to be causing a problem: :: error: [myFile.cpp] Error -1073741515 regarding the Nokia SDK, a colleague is currently trying that out, however they have run into problems: 1. (Known bug) To uninstal the SDK the Nokia server is contacted, and that can't be done through our firewall. So we were unable to uninstall it. 2. (Known bug) You update the SDK through the firewall. 3. The following code causes an error in Creator. The troublesome source code is simply: // import Qt 4.7 import org.webkit 1.0 // And the exact error is: // Starting D:\qt\projects\qml\locator- build\debug\locator.exe... qrc:mainwindow.qml:2:1: module org.webkit is not installed // My colleague has attmepted two different configurations: 1. Nokia Qt SDK beta, targeting the Symbian simulator 2. Qt 4.7 beta, targeting Windows Both using Qt Creator 2.0 beta (though it’s reported as 1.3.83) and both installed using the binaries. The only real problem is point 3, since if the webkit error wasn't present, there would be no need to uninstall it. On Tue, May 11, 2010 at 2:03 PM, Eike Ziller eike.zil...@nokia.comwrote: On May 11, 2010, at 2:59 PM, ext Eike Ziller wrote: On May 11, 2010, at 2:37 PM, ext Jack Wootton wrote: On Tue, May 11, 2010 at 1:21 PM, Eike Ziller eike.zil...@nokia.com wrote: On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote: On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote: On Mon, May 10, 2010 at 11:33:31AM +0100, Jack Wootton wrote: I'm having problems getting Qt Debugger libraries to build. Environment - Creator 2.0 built from source Qt 4.7 built from source Windows XP Nokia N97 SDK I have %epocroot% set to \ Creator is run from the command line at C:\git\creator2.0\bin You do not need the compiled debugging helpers for neither Symbian nor Windows/MinGW deverlopment. They have been replaced by Python scripts that do not need compilation. The problem I'm facing is that Creator Projects Build Settings Qt Version isn't listing all the Qt installations listed under Tools Options Qt4. The Projects tab within Creator allows general Build Settings to be set. One such setting is the Qt Version to use when building. The only Qt Versions listed are Qt installations where the helper library is built. At least it seems that way. It lists the Qt Versions that match the Target architecture of the target you have selected (probably Desktop ?). If you have Qt Versions installed (and known to Qt Creator) that make it possible to develop for multiple targets, your Projects mode should have tabs Targets, Editor Settings and Dependencies. Ok, that makes sense. I've added a target Symbian Device and in this scenario the Qt Version which is listed is Nokia_N97_SDK(Qt 4.7.0). So that means you're correct, and my idea of it being dictated by the debugger library faling to build, was definitely wrong. However I don't really want to build for a device, I want to build for the emulator in the SDK. So the build process should use abld, but the target should be winscw and not armv5. It seems that when I add a Symbian Device as a target, Creator will only build it for armv5. Does creator even know where epoc.exe is or is capable of launching the emulator? 1) You need to point Qt Creator to your Carbide.c++ installation (which contains the necessary tool chain). To do that, open Tools-Options-Qt-Versions, select the Qt Version and point Carbide path to the Carbide install. 2) Add a target Symbian Emulator to your project And to do some advertising for a better world ;) What about trying the Nokia Qt SDK beta, with the shiny new Qt Simulator? http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/IDEs/Nokia_Qt_SDK/ Best regards, Eike Similar to http://doc.qt.nokia.com/qtcreator-snapshot/creator-building-running.html#building-for-symbian If you want to compile for a different target than shown in the tabs on the Targets page, e.g. Symbian devices, you need to add a target (press + next to the Desktop tab). I didn't know that Creator used devices.xml to auto-detect SDKs. I thought it really was auto-detecting them. Define really auto-detecting :) OK. Good point. I assumed (bad I know) that it may have scanned for epoc32 or something like that.
[Qt-creator] QtCreator does not update GUI while loading large project
Hi there, In our department we have a quite large Project, that uses the subdir feature of .pro files a lot. The project itself is stored on a NFS share (which makes IO a little slow). Every time I open this project in qtcreator the UI of qtcreator stops updating itself. There is no progress bar or anything. This state lasts for several seconds. And the all of the sudden the UI repaints and the project structure is fully visible in the project explorer. I observed this behaviour using QtCreator 1.3.83 on Linux. Is this a known Issue? Regards, Markus ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] QtCreator does not update GUI while loading large project
Hi, I think this was fixed in 4648a5b3a41ae177fbcc3c2fea2c617dd3357d80 ciao robe On May 11, 2010, at 4:00 PM, ext Liebe Markus (RtP2/TEF72) wrote: Hi there, In our department we have a quite large Project, that uses the subdir feature of .pro files a lot. The project itself is stored on a NFS share (which makes IO a little slow). Every time I open this project in qtcreator the UI of qtcreator stops updating itself. There is no progress bar or anything. This state lasts for several seconds. And the all of the sudden the UI repaints and the project structure is fully visible in the project explorer. I observed this behaviour using QtCreator 1.3.83 on Linux. Is this a known Issue? Regards, Markus ___ 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] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
My goal is to make a Qt project runnable from any user's Linux home directory (no hard coded paths). I tried setting the working directory setting found under Project-Run Settings-Running Executable-Working Directory? That your app depends on the working directory is the problem. Depending on how (and on which OS) your app is started, the working directory will contain all kind of interesting values. You should try to locate your data relative to e.g. QApplication::applicationDirPath(), or QDesktopServices::storageLocation(). I am not sure I understand. I am trying to make the Qt Creator project run settings paths relative (no hard-coded absolute paths ). I want any Red Hat Enterprise Linux developer to be able to extract a project tarball to his home directory, open the Qt project file and be able to build, run, and debug from within Qt Creator without having to modify any Qt Creator project setings. The problem is the Qt project Working Directory Run Setting seems to only accept hard-coded absolute paths. You mean I can access Qt class static methods in the *Qt Creator* project run settings? Or are you saying it cannot be done and the best I can do is to use these static methods at run-time? Thank you for your help, -Ed ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
On Tue, May 11, 2010 at 1:45 PM, Ed Sutton esut...@fescorp.com wrote: I am not sure I understand. I am trying to make the Qt Creator project run settings paths relative (no hard-coded absolute paths ). I want any Red Hat Enterprise Linux developer to be able to extract a project tarball to his home directory, open the Qt project file and be able to build, run, and debug from within Qt Creator without having to modify any Qt Creator project setings. The problem is the Qt project Working Directory Run Setting seems to only accept hard-coded absolute paths. Are you including the .pro.user files in the tarball? If you are, you shouldn't. -- André Fillipe ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
Or are you saying it cannot be done and the best I can do is to use these static methods at run-time? We're saying that the run-time solution is superior in general. Working directory is a notoriously fickle beast and it can change just depending on how you happen to invoke the program. The static methods, however, will always return a consistent path no matter how you invoke the application. /s/ Adam ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Creator for Python
Thanks Victor, On 11/05/2010 12:21 م, Victor Sardina wrote: Bashir: Among the free alternatives out there you can take a look at Eric4 Python IDE if you plan on using Python and the PyQt wrappers at the URL below: http://eric-ide.python-projects.org I'll test it now, any way I've read some articles about it most of them said that its code completion is so bad even by comparing with eclipse plugin. For wxWidgets development (although I doubt you plan on using the wxWidgets toolkit) I only know of BoaConstructor, which uses the corresponding wxPython wrappers, located here: http://sourceforge.net/projects/boa-constructor/files Oh no, I escaped from wxWidget since 5 years ago and I'll never back again :o Qt+Qt Creator are most precious developing tools (for me at least) :-D Other commercial IDEs have very nice features, such as the Komodo IDE, but it doesn't really support GUI development. Komodo IDE supports almost all the major scripting languages, and have very nice features for team development as well. They used to have a GUI builder, but do not support it any longer. You can get more information at this URL: http://www.activestate.com/komodo/ Good luck in your endeavours, Victor On 5/10/10 11:39 PM, M. Bashir Al-Noimi wrote: Hi folks, Recently I forced to do some web interfaces for one of my projects so I decided to learn Python because -as I read- it's easy language to learn which supports web applications (in addition to GUI/Qt application) so I need to know the following: 1. Does Qt Creator supports Python (I'm sure 99.999% it's not because I'm using it since earlier versions)? 2. Are there any plans for supporting Python in future? 3. What's most alternative IDE to Qt Creator for Python? -- Best Regards Muhammad Bashir Al-Noimi My Blog: http://mbnoimi.net ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Creator for Python
On Tue, May 11, 2010 at 4:15 PM, André Pönitz andre.poen...@nokia.com wrote: On Tuesday 11 May 2010 11:39:15 ext M. Bashir Al-Noimi wrote: There is no real Python support in Creator. However, there is some generic syntax highlighter in the works that also covers Python, and Creator's debugger plugin already talks to pdb (the Python debugger) pretty much the same way it uses gdb for C++. Really looking forward to generic syntax highlighter incl. for Python :D I too have the same wish as the original poster - develop my django apps as well as Qt C++ apps using the same IDE :) So far, I've only felt comfortable with Kate for python work. Regards Rajeev J Sebastian ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
On May 11, 2010, at 12:38 PM, André Fillipe wrote: On Tue, May 11, 2010 at 1:45 PM, Ed Sutton esut...@fescorp.commailto:esut...@fescorp.com wrote: I am not sure I understand. I am trying to make the Qt Creator project run settings paths relative (no hard-coded absolute paths ). I want any Red Hat Enterprise Linux developer to be able to extract a project tarball to his home directory, open the Qt project file and be able to build, run, and debug from within Qt Creator without having to modify any Qt Creator project setings. The problem is the Qt project Working Directory Run Setting seems to only accept hard-coded absolute paths. Are you including the .pro.user files in the tarball? If you are, you shouldn't. Yes, I am. I have also included the .pro.user files in version control. Is the preferred alternative to not rely on Qt Creator project settings at all? Basically everything should be persisted in the *.pro file? Obviously if I delete the .pro.user file I lose all Qt Project settings; custom build steps, build environment, run settings, and run environment settings. I had added an environment variable required by a 3rd-party library to the run settings environment. The pro.user persisted this and without this file a user cannot simply extract, open a project in Qt Creator, build, and run. I will need to think about alternatives. Coming from Windows Visual Studio 2008 I saw Qt Creator as a viable replacement tool (or maybe a crutch) in my new Linux world. I viewed the Qt *.pro files as the equivalent to Visual Studio's project *.sln solution file and *.csproj project file which I typically versioned control as well. Thank you both for sharing your experience and time. -Ed ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
On 05/11/2010 10:39 PM, Ed Sutton wrote: Obviously if I delete the .pro.user file I lose all Qt Project settings; custom build steps, build environment, run settings, and run environment settings. I had added an environment variable required by a 3rd-party library to the run settings environment. The pro.user persisted this and without this file a user cannot simply extract, open a project in Qt Creator, build, and run. I will need to think about alternatives. Users shouldn't even need to use Qt Creator. All they need is: qmake myproject.pro make Any tweaks you need should be coded inside the *.pro file. The qmake reference docs contain everything you need. ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
Any tweaks you need should be coded inside the *.pro file.
True.
The qmake reference docs contain everything you need.
Quite the opposite: qmake is probably the worst documented part of Qt.
Try and search for any info on $$qtLibraryTarget, the fakelib
template, $$files and the such. I spent this weekend rewriting my
team's convoluted build process and my best source of reference were
Qt Solutions .pro files. And lots of trial and error. We now build and
package straight from checkout, but it was a chore.
The improved build system in the Qt Roadmap is the feature I am most
anxious about. Qmake is showing its age and none of the replacements
are good enough.
Coming from Windows Visual Studio 2008 I saw Qt Creator as
a viable replacement tool (or maybe a crutch) in my new
Linux world. I viewed the Qt *.pro files as the equivalent
to Visual Studio's project *.sln solution file and *.csproj
project file which I typically versioned control as well.
They are. The *.pro.user files, however, are like the
*.vcproj.{machine}.{username}.user files which you usually shouldn't
version.
If you clarify what you are trying to accomplish (no need to go into
NDA-breaching specifics), maybe I can assist you. I think Qt Creator
is currently the best C++ IDE available for Linux and it would be a
shame not to use it.
--
André Fillipe
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
On May 11, 2010, at 4:08 PM, André Fillipe wrote:
Any tweaks you need should be coded inside the *.pro file.
True.
The qmake reference docs contain everything you need.
Quite the opposite: qmake is probably the worst documented part of Qt.
Try and search for any info on $$qtLibraryTarget, the fakelib
template, $$files and the such. I spent this weekend rewriting my
team's convoluted build process and my best source of reference were
Qt Solutions .pro files. And lots of trial and error. We now build and
package straight from checkout, but it was a chore.
Having spent a lot of time on making a (mostly)
automated-checkout-build-and-package process, I would be interested in hearing
an overview of your build process. I think I will grep some of the Qt .pro
files myself to see what new tricks I may learn.
The improved build system in the Qt Roadmap is the feature I am most
anxious about. Qmake is showing its age and none of the replacements
are good enough.
Coming from Windows Visual Studio 2008 I saw Qt Creator as
a viable replacement tool (or maybe a crutch) in my new
Linux world. I viewed the Qt *.pro files as the equivalent
to Visual Studio's project *.sln solution file and *.csproj
project file which I typically versioned control as well.
They are. The *.pro.user files, however, are like the
*.vcproj.{machine}.{username}.user files which you usually shouldn't
version.
If you clarify what you are trying to accomplish (no need to go into
NDA-breaching specifics), maybe I can assist you.
I probably just need to rethink things. My goals are to be able to:
1. Checkout a Qt project from Subversion ( or extract a tarball )
2. Open Qt project file in Qt Creator
3. Build
4. Run execuable from Qt Creator
5. or Start debugger from Qt Creator and debug step into the demo source code
I think it is mainly the running/debugging from Qt Creator that seems hard to
accomplish without the *.pro.user files or requiring the user to setup an
environment.
To run the demo executable, I have to set environment variables, tell it where
to located the dynamic myapi libraries, and pass it an xml configuration file
as a command line argument.
I can use rpath to tell it where to look for the libs (run-time search paths in
general have been a learning curve under Linux as there seems to be about 4
ways to do it). I am not sure about how to set an environment variable without
the *.pro.user file. The command line argument is solvable as long as I put
the xml file it the same
folder as the demo executable.
* I am building two rpm pacxkages from a single build.spec file; myapi and
myapi-devel.
* The build.spec gets all source from Subversion, calls the build
scripts(qmake *.pro -r -spec linux-g++, make), and makes the two rpms from the
build output..
* myapi rpm installs shared libraries to /usr/lib/myapi/
* myapi-devel installs the myapi header files to /usr/include/myapi/,
Doxygen HTML documentation for the API, and a source code example tarball
containing a Qt project GUI project demonstrating how to use the API
I am hoping to reduce tech support calls. I want the customer to be able to
use Qt Creator and not have to mess about with any environment variables or
settings. Using Qt Creator I want him to be able to open the project, compile,
run, and debug. Just get him started quickly and easily with no setup
configuration hassles.
I think Qt Creator
is currently the best C++ IDE available for Linux and it would be a
shame not to use it.
After making a couple attempts at using Eclipse C++ (with Qt integration), I
keep coming back to Qt Creator. I agree I have seen nothing better for a C++
Linux IDE and for my development I intend to stick with it. And if I can get a
few new customers hooked I am happy to spread the word. :-)
Thank you very much for your assistance,
-Ed
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Qt Build Settings can use $BUILDIR. Why not Project Run Settings?
I am totally unable to tell which part of your text is a quote and which
is something you wrote as a reply :-/
On 05/12/2010 01:54 AM, Ed Sutton wrote:
On May 11, 2010, at 4:08 PM, André Fillipe wrote:
Any tweaks you need should be coded inside the *.pro file.
True.
The qmake reference docs contain everything you need.
Quite the opposite: qmake is probably the worst documented part of Qt.
Try and search for any info on $$qtLibraryTarget, the fakelib
template, $$files and the such. I spent this weekend rewriting my
team's convoluted build process and my best source of reference were
Qt Solutions .pro files. And lots of trial and error. We now build and
package straight from checkout, but it was a chore.
Having spent a lot of time on making a (mostly)
automated-checkout-build-and-package process, I would be interested in
hearing an overview of your build process. I think I will grep some of the
Qt .pro files myself to see what new tricks I may learn.
The improved build system in the Qt Roadmap is the feature I am most
anxious about. Qmake is showing its age and none of the replacements
are good enough.
Coming from Windows Visual Studio 2008 I saw Qt Creator as
a viable replacement tool (or maybe a crutch) in my new
Linux world. I viewed the Qt *.pro files as the equivalent
to Visual Studio's project *.sln solution file and *.csproj
project file which I typically versioned control as well.
They are. The *.pro.user files, however, are like the
*.vcproj.{machine}.{username}.user files which you usually shouldn't
version.
If you clarify what you are trying to accomplish (no need to go into
NDA-breaching specifics), maybe I can assist you.
I probably just need to rethink things. My goals are to be able to:
1. Checkout a Qt project from Subversion ( or extract a tarball )
2. Open Qt project file in Qt Creator
3. Build
4. Run execuable from Qt Creator
5. or Start debugger from Qt Creator and debug step into the demo source
code
I think it is mainly the running/debugging from Qt Creator that seems hard to
accomplish without the *.pro.user files or requiring the user to setup an
environment.
To run the demo executable, I have to set environment variables, tell it
where to located the dynamic myapi libraries, and pass it an xml
configuration file as a command line argument.
I can use rpath to tell it where to look for the libs (run-time search paths
in general have been a learning curve under Linux as there seems to be about
4 ways to do it). I am not sure about how to set an environment variable
without the *.pro.user file. The command line argument is solvable as long
as I put the xml file it the same
folder as the demo executable.
* I am building two rpm pacxkages from a single build.spec file; myapi
and myapi-devel.
* The build.spec gets all source from Subversion, calls the build
scripts(qmake *.pro -r -spec linux-g++, make), and makes the two rpms from
the build output..
* myapi rpm installs shared libraries to /usr/lib/myapi/
* myapi-devel installs the myapi header files to /usr/include/myapi/,
Doxygen HTML documentation for the API, and a source code example tarball
containing a Qt project GUI project demonstrating how to use the API
I am hoping to reduce tech support calls. I want the customer to be able to
use Qt Creator and not have to mess about with any environment variables or
settings. Using Qt Creator I want him to be able to open the project,
compile, run, and debug. Just get him started quickly and easily with no
setup configuration hassles.
I think Qt Creator
is currently the best C++ IDE available for Linux and it would be a
shame not to use it.
After making a couple attempts at using Eclipse C++ (with Qt integration), I
keep coming back to Qt Creator. I agree I have seen nothing better for a C++
Linux IDE and for my development I intend to stick with it. And if I can get
a few new customers hooked I am happy to spread the word. :-)
Thank you very much for your assistance,
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
