regarding building Qt on S60

[prajna123]

Dear All,

I have installed Qt for S60.Its configured properly as I got the message as Qt is configured and build Qt using bldmake bldfiles and abld build winscw udeb. after running the command configure -platform win32-mwc -xplatform symbian-abld -qconfig symbian.

Next step is to build Qt.But when I give bldmake bldfiles it is giving error as EPOC32 not found.


My Symbian installed path is C:\Symbian\9.2\S60_3rd_FP1_3 and
Qt package is in C:\Qt\4.4.2-pyramid.
I have substituted C:\Symbian\9.2\S60_3rd_FP1_3 with Q drive.



I think we have to map epoc32 of s60 into Qt.Is there any method for that??.
Can you please suggest where I am going wrong.

[wizard_hu_]

Have you set EPOCROOT environment variable? Qt is reported to need that.

[prajna123]

I have extended the path by adding C:\Qt\4.4.2-pyramid\bin in path variable( that is, in My computer-Properties-advanced-environment variables---system variables-Path.)

And in My computer-Properties-advanced-environment variables---User variables, I have set the EPOCROOT to \( as I substituted C:\Symbian\9.2\S60_3rd_FP1_3 with Q drive.)


Could you please suggest me where I am going wrong.

[wizard_hu_]

In that case make sure that you also access Qt via drive Q:. The requirement of "projects and the SDK have to reside on the same drive" still applies.

[prajna123]

ok. Then I will not create any virtual drive for my S60 SDK.I will try from my original C dive.

One more problem I am getting .
After installing plugin (nokia plug-in as mentioned to install in install.txt) for s60 sdk FP1,epoc is not working fine.It launches but gets stuck.

Before installing it was working fine.

Qt for S60 needs this plug-in.What can be done for this?
Could you please suggest the solution for this??

[Sorcery-ltd]

Which plugin? The Open C/C++ plugin?

It's working fine on my setup.

Maybe you should try again from scratch (re-install). You're correct that you don't want to subst your EPOCROOT to another drive, just run everything from the C: drive.

Sorcery

[prajna123]

Thanks a lot.
Yes, I was refering to Open C/C++ plugin.Now that problem got solved after uninstall and install plug-in again.

I tried buiding Qt from C drive.Now EPOCROOT problem got solved.Commands bldmake bldfiles and abld build winscw udeb is working properly now.

Bot epoc command is not working for Qt examples after building.epoc is launched but its not responding.Its blocked.

I uninstalled all the set up and installed again.Still the same.( EPOC was working fine for S60 applications before even after plug-in installation).
What could be the problem??

[Sorcery-ltd]

Does the same thing happen if you launch the emulator from Carbide.c++? If so, you could look in the console output and see if you can see an error where it gets stuck? If not you could look at the epocwind.out file (assuming your epoc.ini file enables logging to file).

I hope that makes sense, I'm not sure how much Symbian/S60 experience you have.

Sorcery

[prajna123]

In carbide its different thing.
I am able to build Qt application but when I run the application epoc gets launched and disappears all of a sudden.I checked.(but in command prompt epoc gets launched and remains blocked.)

Thank you for your suggestion.
I will check console output and epocwind.out.
(I have 2 years of experience on Symbian)

[prajna123]

I checked my epocwind.out file for logs.
Some panic is coming.(Thread WSERV.EXE::Wserv Panic WSERV-INTERNAL 13
)Below is the log.


PlatSecEnforcement OFF
PlatSecDiagnostics ON
PlatSecProcessIsolation ON
PlatSecEnforceSysBin ON
PlatSecDisabledCaps NONE
0.000 Thread 008e1280 created @ 0x8e1280 - Win32 Thread ID 0xe54
0.000 Thread EKern.exe::Supervisor created @ 0x9d34ec - Win32 Thread ID 0xc0c
0.000 Thread EKern.exe:fcThread0 created @ 0x9d3fa4 - Win32 Thread ID 0xb14
0.000 Thread EKern.exe:fcThread1 created @ 0x9d43c8 - Win32 Thread ID 0x1fc
0.000 Thread EKern.exe::TimerThread created @ 0x9d4ca4 - Win32 Thread ID 0x1a0
7.570 Thread EKern.exe::FlashThread created @ 0x9d6c20 - Win32 Thread ID 0x8c0
8.490 Thread EKern.exe::MultiMediaCard0 created @ 0x9d7bf4 - Win32 Thread ID 0x1b8
8.720 Thread EKern.exe::NandThread created @ 0x9dec9c - Win32 Thread ID 0xe08
9.645 Thread EFile.exe::Main created @ 0x9dfb4c - Win32 Thread ID 0x58c
10.315 Thread EFile.exe::Local-009e71dc created @ 0x9e749c - Win32 Thread ID 0x508
10.445 Thread EFile.exe::LoaderThread created @ 0x9edf80 - Win32 Thread ID 0xd7c
10.450 Thread EFile.exe::StartupThread created @ 0x9eea34 - Win32 Thread ID 0xb80
11.015 Thread E32STRT.EXE::Main created @ 0x9f8d70 - Win32 Thread ID 0x964
11.070 Thread EFile.exe::Local-009f92d8 created @ 0x9f9598 - Win32 Thread ID 0xd98
11.075 Thread EFile.exe::Local-009f9814 created @ 0x9f9ad4 - Win32 Thread ID 0x3e0
11.205 Thread EFile.exe::InitCompleteThread created @ 0x9fb1d4 - Win32 Thread ID 0x5a8
11.345 Thread HALSettings.exe::Main created @ 0x9fbafc - Win32 Thread ID 0x384
11.470 Thread HALSettings.exe::Main Killed -12
11.610 Thread domainSrv.exe::Main created @ 0x9fc35c - Win32 Thread ID 0x8c4
11.655 Thread SysAgt2Svr.exe::Main created @ 0x9fd2a0 - Win32 Thread ID 0x6b8
14.120 Thread WSERV.EXE::Main created @ 0x9fece4 - Win32 Thread ID 0xa2c
14.145 Thread WSERV.EXE::Wserv Panic WSERV-INTERNAL 13

How this can be solved.
Could you suggest me how to resolve this kind of problem?

[Sorcery-ltd]

Sorry, no idea. WSERV Panic 13 is invalid font handle, but WSERV-INTERNAL 13 is likely something else that isn't in the public SDK docs.

I'm guessing your SDK installation is getting corrupted somehow. None of the steps for the Qt install should do that though.

Sorcery

[prajna123]

Thank you for the reply.

I think S60 SDK is corrupted now.
But it was working fine before. (before Qt install)

What could be the reason behind this?Is this because of Rpipe library?
Can this be resolved by uninstall/install again???

[Sorcery-ltd]

It shouldn't have anything to do with the RPipe library, since that is only an addition to the 3rd FP1 SDK (you don't want to add it to FP2 though). I think it is the only step where you unzip something over the top of the actual SDK manually though... so maybe that's when it happened.

Unfortunately the best thing I can suggest is to re-install the SDK again (you should be able to leave Qt installed). Make sure you have the correct SDK selected in the command prompt when you are calling 'epoc' (check with 'devices' command). Try running the emulator after each step of your setup and see if/when it breaks.

Sorcery

[Sorcery-ltd]

OK, following your posts on the qtS60 feedback mailing list it's clear that you didn't read the instructions quite carefully enough. The wsini.ini file that you've replaced is for the S60 5th Edition SDK ONLY - you MUST NOT replace it on any earlier SDKs.

I'm just writing this here so there's a record if anyone else has the same problem.

Sorcery

[Jack Torrance]

Once again thanks Sorcery!

We're working on the next Qt/S60 release that will be much easier to take into usage. It will come out soon and I'll update this forum immediately!

Thanks,
Jack