Re: [Qt-creator] unsubscribe
Hmm..that didn't work... _ From: qt-creator-boun...@trolltech.com [mailto:qt-creator-boun...@trolltech.com] On Behalf Of Boy Lenssen Sent: dinsdag 30 maart 2010 9:25 To: qt-creator@trolltech.com Subject: [Qt-creator] unsubscribe __ Information from ESET NOD32 Antivirus, version of virus signature database 4983 (20100329) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 4983 (20100329) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] help
___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Creating an exotic target for qt4 project
(this discussion applies to qt-creator git master) I'm trying to contribute to qt creator by trying to implement a new target (in addition to Desktop, Maemo, Symbian). For the purposes of this excercise, let's call it scratchbox - it would not execute qmake directly, but a series of magical incantations to build the code in scratchbox (and in case of run settings, run it). [Yes, I know about madde, no need to point that out] I added the target information to qt4projectmanagerconstants.h, qt4target.cpp and qtversionmanager.cpp. So far so good; I can already see the target I created, but now I'm wondering how to make that target do something useful. What I'd need is: - Custom build / run settings pane in projects tab. By looking at the code, it would seem I would need to create a new project type instead of just a new target. - Custom behavior. Am I mistaken in my idea that all I can do in Qt4 project type is to control the qt version, which would basically amount to specifying qmake path? I'd like to execute completely custom code when this particular target (scratchbox) is active. -- Ville M. Vainio http://tinyurl.com/vainio ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Creating an exotic target for qt4 project
On 30.03.2010 10:11, ext Ville M. Vainio wrote: (this discussion applies to qt-creator git master) I'm trying to contribute to qt creator by trying to implement a new target (in addition to Desktop, Maemo, Symbian). For the purposes of this excercise, let's call it scratchbox - it would not execute qmake directly, but a series of magical incantations to build the code in scratchbox (and in case of run settings, run it). Sounds intersting, but ... [Yes, I know about madde, no need to point that out] you know about MADDE, don't you? ;-) I added the target information to qt4projectmanagerconstants.h, qt4target.cpp and qtversionmanager.cpp. You already did the tricky part then:-) So far so good; I can already see the target I created, but now I'm wondering how to make that target do something useful. What I'd need is: - Custom build / run settings pane in projects tab. By looking at the code, it would seem I would need to create a new project type instead of just a new target. Build Settings/Generic is created by Qt4ProjectConfigWidget and is project specific. The Build/clean steps in the BuildSettings view are handled by the buildstep's configuration widget (e.g. MakeStepConfigWidget). The Run Settings are managed by the runconfiguration's widget (e.g. Qt4RunConfigurationWidget) - Custom behavior. Am I mistaken in my idea that all I can do in Qt4 project type is to control the qt version, which would basically amount to specifying qmake path? I'd like to execute completely custom code when this particular target (scratchbox) is active. You will need to implement custom buildsteps (see e.g. MakeStep in Qt4ProjectManager). In addition you will probably need to provide a custom runconfiguration (what is to be run?) as well as runcontrols (how is this run?). Please be aware that the destinction between RunConfiguration and RunControl is not as strict as we would like it to be. I must tell you that I think that this change is a bit problematic: It extends one of our plugins, so it is using internal interfaces which we do change quite frequently. We are further concentrating our efforts on MADDE, so chances are slim to get this merged. So please be prepared for maintainance overhead! OTOH this definitely is a great project to get to know the inner workings of the Qt4 plugin and the build infrastructure of creator and I do not want to discourage you from doing it. 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] (no subject)
abhishek...@gmail.com ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] How *not* hard-code Qt Project Build Environment variable LD_LIBRARY_PATH ?
Sorry, I am stuck on this... When it comes to dynamically loaded shared libs that are required at link time, I can not figure out the trick of completely removing hard-coded paths from my Qt Creator project build environment. Setting LD_LIBRARY_PATH under the Qt Project Build Environment to a relative path works fine for building / linking. Example: LD_LIBRARY_PATH=/opt/qtsdk-2010.02/lib/qtcreator:/home/esutton/projects/myproject/guiproject/../../lib Question: How can I replace the base part of the relative path with a variable? Replacing with $(PWD), does not work. Apparently at the build environment stage, PWD is set to the qmake working directory of /opt/qtsdk-2010.02/qt/bin LD_LIBRARY_PATH=/opt/qtsdk-2010.02/lib/qtcreator:$(PWD)/../../lib Can a variable added to the Qt project file be referenced in the Qt project Build Environment ? I tried adding this to my Qt Project File: MYLDLIBPATH = $$PWD/../../lib message(MYLDLIBPATH == $$MYLDLIBPATH) and adding a reference to this variable in the Qt project Build Environment: LD_LIBRARY_PATH=/opt/qtsdk-2010.02/lib/qtcreator:$(MYLDLIBPATH) This does *not* work even though the qmake message displays the desired path: Project MESSAGE: MYLDLIBPATH = /home/esutton/projects/myproject/guiproject/../../lib I am building under Red Hat Enterprise Linux 5.x. I do not want to use rpath because I want to avoid hard-coded paths in released binaries. My goal is to retrieve source code from the repository and to build a release using: qmake myproject.pro make -Ed ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] How *not* hard-code Qt Project Build Environment variable LD_LIBRARY_PATH ?
On Mar 30, 2010, at 10:36 AM, Ed Sutton wrote: Sorry, I am stuck on this... When it comes to dynamically loaded shared libs that are required at link time, I can not figure out the trick of completely removing hard-coded paths from my Qt Creator project build environment. Setting LD_LIBRARY_PATH under the Qt Project Build Environment to a relative path works fine for building / linking. Example: LD_LIBRARY_PATH=/opt/qtsdk-2010.02/lib/qtcreator:/home/esutton/projects/myproject/guiproject/../../lib Question: How can I replace the base part of the relative path with a variable? Replacing with $(PWD), does not work. Apparently at the build environment stage, PWD is set to the qmake working directory of /opt/qtsdk-2010.02/qt/bin LD_LIBRARY_PATH=/opt/qtsdk-2010.02/lib/qtcreator:$(PWD)/../../lib Can a variable added to the Qt project file be referenced in the Qt project Build Environment ? I tried adding this to my Qt Project File: MYLDLIBPATH = $$PWD/../../lib message(MYLDLIBPATH == $$MYLDLIBPATH) and adding a reference to this variable in the Qt project Build Environment: LD_LIBRARY_PATH=/opt/qtsdk-2010.02/lib/qtcreator:$(MYLDLIBPATH) This does *not* work even though the qmake message displays the desired path: Project MESSAGE: MYLDLIBPATH = /home/esutton/projects/myproject/guiproject/../../lib I am building under Red Hat Enterprise Linux 5.x. I do not want to use rpath because I want to avoid hard-coded paths in released binaries. My goal is to retrieve source code from the repository and to build a release using: qmake myproject.pro make I found a solution myself for linking to shared libraries. Use rpath-link ( Just like the linker warning had informed me ;-) If I understand it correctly, rpath-link, tells the linker where to look for run-time shared libs to link with and unlike rpath will not hard-code any run-time paths into my binaries. LIBS += -L../../lib #Note the character following the -Wl switch is a lower-case 'L' LIBS += -Wl,-rpath-link,$$PWD/../../lib LIBS += -lmysharedlib -Ed ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
