Qt status

Just to exploit the new shiny Qt Forum facility, here is a short status update:

Qt is now 100% cross compilable (with cygwin), which should speed up development a fair amount.

Current work is going on with libQtWebKit, which will eventually end up as a working demo browser and the vacuum jabber client. Currently the biggest obstacle is a mysterious tendency of the webkit module to slow down oozes when javascript is turned on.

When all that is done (eg webkit and vacuum released) I am doing to look at the possibility to get some office apps ported (since that seems to be a biggie in terms of users wanting it). Which means, that I am maybe going to have a look at porting KDE and looking at KOffice. But first things first.

Great mate!
Are the changes on sourceforge?

Quote:
Are you sure Qt is fast enough to make "something big" run fast?

KDE O_O qt doesn't help there i guess, sounds like a massive job, really cool. Good luck!

@afxgroup

Yes they are!

Just download the trunk.

What do you use to configure it? CMake or configure? Any tip?

@alfkil

GREAT news!
I really hope that you can do all your job fast :)

Qt was a really big resource!

Keep up good work!

Great news, thanks a lot for your work!!! :)

@afxgroup

You should read the file README.amigaos4 in the base of the trunk.

0) First step is to configure the mkspec properly for cross compiling. Go to trunk/mkspec/amigaosnative-g++/qmake.conf and replace each instance of ppc-amigaos-gcc and ppc-amigaos-c++ with gcc and c++. After building all the command line tools, you will need to switch this back. Also possibly you need to comment out the part on the "DEFINES +=" line that says QT3_SUPPORT.

1) Now to build qmake. There is a makefile ready for use in the qmake directory. Remember to always use gmake in place of make for unix style paths.

2) When qmake is built, you should add the trunk/bin directory to the PATH variable.

3) Next step is to build the other command line tools. Go to trunk/src/tools directory. First you need to build the bootstrap. Go to bootstrap directory and run qmake first, then gmake. After that you should go to moc, rcc and uic directories and run qmake and then gmake for each.

4) Now you are ready to build the libraries and everything else. First go back to mkspecs/amigaosnative-g++/qmake.conf and replace gcc with ppc-amigaos-gcc etc, and also remove the comment in front of QT3_SUPPORT.

5)Start with the corelib in trunk/src/corelib. Go to the directory and run first qmake then gmake.

Build the libraries in following order:

src/corelib
src/gui
src/network
src/opengl
src/sql
src/xml
src/xmlpatterns
src/webkit
etc etc.......

6) You also need to build some plugins for everything to work:

src/plugins/graphicssystems/opengl
src/plugins/imageformats/ (all)
src/plugins/sqldrivers/sqlite

7) ...and you can also build the designer and the assistant in trunk/tools...

Feel free to ask questions if you get stranded!

noo! i need to cross compile it.. :) so should i use my qmake? (i mean the cywin/macosx one)?

@alfkil

Excellent news mate !
If we are able to get some more speed and a proper Amiga GUI style ... well would be a dream

I'm really curious to try the new QT web based browser

ok, i'm compiling it using -spec parameter passing os4 specs.

i have an error in this file:

corelib/io/qfsfileengine_unix.cpp at line 635:

Quote:

../../corelib/io/qfsfileengine_unix.cpp:635: error: within this context
../../corelib/io/qfsfileengine_unix.cpp: In member function 'uchar* QFSFileEnginePrivate::map(qint64, qint64, QFile::MemoryMapFlags)':

[edit]
you must use QLatin1String("/qt/home") instead of "/qt/home"

@afxgroup

Try replacing the problematic line with this:

home = QString("/qt/home");

and if that doesn't work try this:

return(QString("/qt/home"));

EDIT: Oh wait, what component are you building?? Is this building qmake or have you moved on to build corelib?? If you get this problem building corelib, there is a problem with your setup. I forgot to mention, that you should set QMAKESPEC veriable to "amigaosnative-g++", that should get you the right specs.

Where did you get qmake from?? A pc or linux distribution?? I have not tried using that to build qt, I'm using custom built qmake made the way described above.

EDIT EDIT: Ah I see you solved the problem! Good for your .

i've downloaded QT4 from cygwin directly. Now bootsrap is compiled correctly.
I've also set the default spec of qmake like amigaosnative-g++ with a symbolink link to "default" dir. BTW i'm using the -spec flag just to be sure
Now when i try to compile corelib i receive an error:

make: *** No rule to make target `../../bin/moc', needed by `.moc/release-shared/moc_qabstractanimation.cpp'. Stop.

but I have no moc in the bin directory..

P.S.
do you have some skype (or whatever else) account? so we can speak quickly

@afxgroup

moc should be built by entering trunk/src/tools/moc and running qmake/gmake.

I do have Skype, my name is just 'alfkil'.

Quote:

this is great news as the OO light port looks like it has yet a long,long way to go

Yesterday night i've compiled QtScript since almost all changes are the same i've made in the past with OWB and its javascript library

@afxgroup

I've been bugging alfkil for that for ages, can you upload it somewhere?

ehm.. i could but yesterday my version of qt was crashing on my sam.. so it is better that is Alf that compile it. Today i'll add the changes to svn

changes committed