Ok, once again thanks.

I'm still new to this, and though i'm getting more and more into it, there are 
still many components that needs to fit before it works.

So final question must be, If I have both the TP and the Master of mobility in 
two different directories on my machine, would I then be able to "switch" just 
by configuring and building each of them.

Or do I need separate virtual machines to test each?

Do you understand the question?

/Anders
From: Luoma Antti [mailto:[email protected]]
Sent: 14. september 2010 10:02
To: Anders Kjærgaard Hansen; [email protected]
Subject: RE: [Qt-mobility-feedback] Still having trouble building QtMobility 
1.1 TP

Hi,

I am not the best person to answer this question, but some things to consider:

- if everything you need will, work -> don't update
- use only modules you need from the api (confiugure -modules "location 
multimedia")
- I think there are bug fixes and some new features/backends. -> worth to update
- newer could be "more ready" -> worth to update
- I think api's have changed -> worth to update and check your code against that

master branch should compile on all platforms.

-Antti

________________________________
From: Anders Kjærgaard Hansen [mailto:[email protected]]
Sent: Tuesday, September 14, 2010 10:56 AM
To: Luoma Antti; [email protected]
Subject: RE: [Qt-mobility-feedback] Still having trouble building QtMobility 
1.1 TP
By the way Antti.

You say I can get the master from the git repo.

What would you recommend. I would expect that it should be possible to build 
the 1.1 TP (even though I've used a lot of time on it).

But would I be better off building against the master, and modify my code as we 
move towards the final release of 1.1.

Or is it primarily bugfixes and not API changes that will be changed until 
release. And as such only necessary to get stuff from master if I run into 
problems.

What would you recommend?

/Anders

From: Luoma Antti [mailto:[email protected]]
Sent: 14. september 2010 09:11
To: Anders Kjærgaard Hansen; [email protected]
Subject: RE: [Qt-mobility-feedback] Still having trouble building QtMobility 
1.1 TP

Hi,

Check that you have recent winscw compiler installed. I have :

mwccsym2.exe :

Nokia Carbide C/C++ Compiler for Windows/x86.
Copyright (c) 2009, Nokia Corporation
All rights reserved.
Version 3.2.5 build 489
Runtime Built: Feb 19 2010 13:19:12

You can get latest (and greatest) code directly from git repository with a 
command, but we warned: that's not released code..

git clone git://gitorious.org/qt-mobility/qt-mobility.git

-antti


________________________________
From: Anders Kjærgaard Hansen [mailto:[email protected]]
Sent: Tuesday, September 14, 2010 9:45 AM
To: Luoma Antti; [email protected]
Subject: RE: [Qt-mobility-feedback] Still having trouble building QtMobility 
1.1 TP
Thank you for the good reply antti.

That solved those two problems.

Now I run into another issue though. Running the command below (part of make 
debug-winscw) fails with the error below:

C:\qtmobility\qt-mobility-opensource-src-1.1.0-tp>make -s  -r -f 
"\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\qtmobility\qt-mobility-opensource-src-1.1.0-tp\MMF_0X2002AC76\WINSCW\MMF_0X2002AC76.WINSCW"
 UDEB
s60audiocapturesession.cpp
C:\Qt\4.7.0-rc1\src\corelib\tools\qhash.h:611: internal compiler error (please 
report at <http://www.forum.nokia.com>)
C:\Qt\4.7.0-rc1\src\corelib\tools\qhash.h:611: while executing in file 
'CException.c' line: 3187
C:\Qt\4.7.0-rc1\src\corelib\tools\qhash.h:611: (compiling 'value' in 
's60audiocapturesession.cpp')

Errors caused tool to abort.
C:\S60\devices\S60_3rd_FP2_SDK_v1.1\epoc32\tools\make.exe: *** 
[\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\qtmobility\qt-mobility-opensource-src-1.1.0-tp\MMF_0X2002AC76\WINSCW\udeb\s60audiocapturesession.o]
 Error 1

Can you help me figure this out as well?

Aren't I'm supposed to be using the 1.1 tp zip file, or is there a better/newer 
place to be going?

/Anders

From: Luoma Antti [mailto:[email protected]]
Sent: 14. september 2010 08:02
To: Anders Kjærgaard Hansen; [email protected]
Subject: RE: [Qt-mobility-feedback] Still having trouble building QtMobility 
1.1 TP

Hi,

Answer 1) Def files should be in place. 2 problems could cause this. There is 
EXPORTUNFROZEN statement in location.pro file or you have configured qtmobility 
with "-symbian-unfrozen" option. And I checked that location.pro seems to 
include
symbian {
    TARGET.CAPABILITY = ALL -TCB
    TARGET.UID3 = 0x2002AC83
    MMP_RULES += EXPORTUNFROZEN

.. which is causing this. This has been fixed at some point.

Answer 2) So it is trying to include that moc file but fails. The path looks 
ok, but the include should be just #include "moc_qmtmengine_symbian_p.cpp" and 
not ending with semicolon. Have you checked that the moc generated cpp file 
exist?

-antti

________________________________
From: [email protected] 
[mailto:[email protected]] On Behalf Of Anders 
Kjærgaard Hansen
Sent: Monday, September 13, 2010 11:00 AM
To: [email protected]
Subject: [Qt-mobility-feedback] Still having trouble building QtMobility 1.1 TP
Hi all

Im getting more and confident with Qt and Qt Mobility - but i'm still having 
some troubles figuring the last parts out.

After succesfull configure, I get the following warning when running "make 
debug-winscw"
MMPFILE 
"\qtmobility\qt-mobility-opensource-src-1.1.0-tp\src\location\LOCATION_0X2002AC83.MMP"
WARNING: Frozen .def file 
\qtmobility\qt-mobility-opensource-src-1.1.0-tp\src\bwins\QtLocationu.def not 
found - project not frozen

By looking at different files, I've found that the LOCATION_0X2002AC83.MMP file 
ends with the EXPORTUNFROZEN statement, where as e.g. messaging_0x2002AC82.mmp 
ends with
#ifdef WINSCW
DEFFILE ../s60installs/bwins/QtMessaging.def
#elif defined EABI
DEFFILE ../s60installs/eabi/QtMessaging.def
#endif
Telling to look for def files in s60installs library.

Question 1: Why doesn't location look for the def file here?

Next, when building Messaging I get the following error:
C:\qtmobility\qt-mobility-opensource-src-1.1.0-tp\src\messaging\qmtmengine_symbian.cpp:5802:
 `#include' expects "FILENAME" or <FILENAME>
ERROR: cpp.EXE failure
make[1]: *** [MAKEFILEMESSAGING_0X2002AC82] Error 33
make[2]: 
\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\qtmobility\qt-mobility-opensource-src-1.1.0-tp\MESSAGING_0X2002AC82\GCCE\MESSAGING_0X2002AC82.GCCE:
 No such file or directory
make[2]: *** No rule to make target 
`\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\qtmobility\qt-mobility-opensource-src-1.1.0-tp\MESSAGING_0X2002AC82\GCCE\MESSAGING_0X2002AC82.GCCE'.
  Stop.
make[1]: *** [LIBRARYMESSAGING_0X2002AC82] Error 2
make[2]: 
\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\qtmobility\qt-mobility-opensource-src-1.1.0-tp\MESSAGING_0X2002AC82\GCCE\MESSAGING_0X2002AC82.GCCE:
 No such file or directory
make[2]: *** No rule to make target 
`\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\qtmobility\qt-mobility-opensource-src-1.1.0-tp\MESSAGING_0X2002AC82\GCCE\MESSAGING_0X2002AC82.GCCE'.
  Stop.
make[1]: *** [RESOURCEMESSAGING_0X2002AC82] Error 2

The line 5802 in qmtmengine_symbian.cpp is this:
#include "..\..\build\Release\QtMessaging\moc\moc_qmtmengine_symbian_p.cpp";

Which relative to the qmtmengine_symbian file should exist. I have tried 
changing this path to relative from root, and other paths, but it doesn't seem 
to make a difference.

Question 2: What does the compiler error exactly mean - I thought it just 
couldn't find the file to include, but it should exist.

I hope somebody can help me figure these two things out, as this is where I am 
stuck for now.

Best regards
/Anders
_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback

Reply via email to