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 <[email protected]> wrote: >> >> On May 11, 2010, at 10:46 AM, ext Jack Wootton wrote: >> >>> On Mon, May 10, 2010 at 6:30 PM, Andre Poenitz >>> <[email protected]> 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 [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
