Hi,

> The only thing that confuses me is when I read 
> (http://qt.gitorious.org/qt-creator/pages/QtS60WithQtCreator) that you can 
> use Qt Creator to build for winscw too.

> How do you actually do that? That page suggests to check that the path I'm 
> using for my default Qt installation during the build is the correct path - 
> ok but this
> doesn't allow me to switch between gcce and winscw ..does it?

The winscw tool chain is the default tool chain that is used by the Makefiles 
that are generated by qmake for S60, i.e. it is what is built for if you just 
call 'qmake && make'.
To switch between different tool chains you need to change the target that is 
given the 'make' command in the build steps. E.g. 'debug-gcce' for using gcce.
If you want to switch regularly between these configurations, you should create 
additional build configurations, one for gcce and one for winscw.

Yes, you can just run the executable in winscw\udeb to run the app in the 
emulator (as described in the Wiki you already mentioned).

Br, Eike

________________________________________
From: [email protected] [[email protected]] On 
Behalf Of ext Salvatore Rinaldo [[email protected]]
Sent: Monday, September 07, 2009 18:27
To: [email protected]
Subject: [Qt-creator] Qt Creator with S60

Hi guys,

I have built the latest snapshot of Qt Creator from the git repo to see whether 
you can actually make it work with the S60 emulator
and I can actually build for gcce using Qt Creator, which is cool ... obviously 
debugging won't work.

...
On the other hand, once you build for winscw from command line (by the way you 
need Carbide installed for winscw) and you have the executable in 
epoc32\release\winscw\udeb,
you can always set up the run environment (from Projects -> Run Settings -> Run 
Environment) to launch the S60 emulator.

Has anyone tried this successfully yet?

Thanks,
--
Salvatore

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator

Reply via email to