Qt Celestia

Post #61by **t00fri** » 11.01.2008, 21:05

cartrite wrote:
t00fri wrote:I never encountered ANY problems with glext.cpp. Strange...

F.
That's probably because your not using the MinGW compiler. With the binary MinGW version of QT, you are stuck with g++win32. So maybe the config file needs to be set up correctly to compile Celestia.
cartrite

The way I understand all this is as follows:

In Qt/4.3.3/mkspecs there are MANY dirs for different compilers containing qmake.conf files. These are merged when the Makefiles are generated by qmake.

So you must assign the right one as 'default' . That's probably all. It worked fine for me, at least.

Bye Fridger

cartrite · Post #62by **cartrite** » 11.01.2008, 21:09

t00fri wrote:
cartrite wrote:
t00fri wrote:I never encountered ANY problems with glext.cpp. Strange...

F.
That's probably because your not using the MinGW compiler. With the binary MinGW version of QT, you are stuck with g++win32. So maybe the config file needs to be set up correctly to compile Celestia.
cartrite

The way I understand all this is as follows:

In Qt/4.3.3/mkspecs there are MANY dirs for different compilers containing qmake.conf files. These are merged when the Makefiles are generated by qmake.

So you must assign the right one as 'default' . That's probably all. It worked fine for me, at least.

Bye Fridger

This is true if you can build it, but if you download the open source binaries your your stuck with g++win32.
cartrite

Post #63by **t00fri** » 11.01.2008, 21:13

why don't you download the *.zip SOURCES and build them yourself. Drink some beers for an hour or so ;-)

It worked for me (the beers actually ;-)

)

F.

PS: you can always redefine the "default" compiler for qmake. In general it's done automatically during the compilation step. But you can also influence this by hand.

F.

cartrite · Post #64by **cartrite** » 11.01.2008, 21:17

t00fri wrote:why don't you download the *.zip SOURCES and build them yourself. Drink some beers for an hour or so

It worked for me (the beers actually )

F.

I already tried. But my build system is missing some files so the build fails. Probably because it's free.
cartrite

Post #65by **t00fri** » 11.01.2008, 21:18

cartrite wrote:
t00fri wrote:why don't you download the *.zip SOURCES and build them yourself. Drink some beers for an hour or so

It worked for me (the beers actually )

F.
I already tried. But my build system is missing some files so the build fails. Probably because it's free.
cartrite

Show me how it dies

F.

cartrite · Post #66by **cartrite** » 11.01.2008, 21:21

t00fri wrote:
cartrite wrote:
t00fri wrote:why don't you download the *.zip SOURCES and build them yourself. Drink some beers for an hour or so

It worked for me (the beers actually )

F.
I already tried. But my build system is missing some files so the build fails. Probably because it's free.
cartrite

Show me how it dies

F.

http://celestiaproject.net/forum/viewtopic.php?p=98391#98391

Post #67by **t00fri** » 11.01.2008, 21:26

cartrite,

something is wrong with this link...
F.

Vincent · Post #68by **Vincent** » 11.01.2008, 21:29

t00fri wrote:What do you do with qtdemo.pro??

I think for compilation of Qt/4.3.3 you are ONLY supposed to hit

> configure
> nmake

Only at the END of all this you hit qtdemo to start the demos...It all worked fine for me, actually.

Well, I do nothing with qtdemo...
When I type 'configure', things go fine for ~ 5 minutes, and then I get:
"Generating Visual Studio project files..."
"Reading blablabla..."

Then, the compiler stops responding when I get:
"Reading ... qtdemo.pro"

How long does your 'configure' phase last ?

cartrite · Post #69by **cartrite** » 11.01.2008, 21:32

t00fri wrote:cartrite,

something is wrong with this link...
F.

I tried to compile qt4 on WindowsXP and failed. It looks for at least 2 files. msvcprt.lib and msvcrt.lib Not part of my sdk or 2003 toolkit. There was a warning that official qt4 will only compile on MinGW.
http://psi-im.org/wiki/Compiling_Qt4_on_Windows
There is a patch that can be applied that is supposed to get it to compile with msvc but that didn't work either.

Here is what I was trying to link to.
cartrite

cartrite · Post #70by **cartrite** » 11.01.2008, 21:39

Vincent wrote:
t00fri wrote:What do you do with qtdemo.pro??

I think for compilation of Qt/4.3.3 you are ONLY supposed to hit

> configure
> nmake

Only at the END of all this you hit qtdemo to start the demos...It all worked fine for me, actually.
Well, I do nothing with qtdemo...
When I type 'configure', things go fine for ~ 5 minutes, and then I get:
"Generating Visual Studio project files..."
"Reading blablabla..."

Then, the compiler stops responding when I get:
"Reading ... qtdemo.pro"

How long does your 'configure' phase last ?

I got past the configure phase after I pasted the file msvcprt.lib. I had this file in another folder (Microsoft Visual Studio 8\VC\lib) in my sdk libs. I think that was part of a world wind install. Anyhow, it took a long time. Then it failed when I ran make. When I built it on Linux it took about an hour or so. Didn't have any problems either. :wink:

cartrite

Post #71by **t00fri** » 11.01.2008, 21:45

Vincent wrote:
t00fri wrote:What do you do with qtdemo.pro??

I think for compilation of Qt/4.3.3 you are ONLY supposed to hit

> configure
> nmake

Only at the END of all this you hit qtdemo to start the demos...It all worked fine for me, actually.
Well, I do nothing with qtdemo...
When I type 'configure', things go fine for ~ 5 minutes, and then I get:
"Generating Visual Studio project files..."
"Reading blablabla..."

Then, the compiler stops responding when I get:
"Reading ... qtdemo.pro"

How long does your 'configure' phase last ?

Pretty long! On my Core2Duo 2GHz it takes about 15-20 minutes I would guess.

Have you been too impatient, perhaps?

F.

phoenix · Post #72by **phoenix** » 11.01.2008, 22:42

I first installed MinGW and then the Qt-binaries and didn't even try to compile Qt from source.

chris change to glext.cpp fixed the compile-errors for me (i was just about to give up).

after this I just had to replace some libs and use the dynamic-linked versions of libpng, libjpeg and zlib because all of them gave me link-errors with MinGW.

now all is working fine for me ;-)

Post #73by **t00fri** » 11.01.2008, 22:58

chris wrote:
t00fri wrote:Chris,

I think your last glext.cpp fix was no good . It generated a link error also in my environment and didn't help cartrite either ...

Can we return to the old setup?

F.

Strange . . . I tested it with both MinGW / Qt4 and MSVC / Win32. I'll figure out what's going on. I can't build MinGW/Qt4 without the change.

--Chris

Chris,

your glext.cpp "fix" works fine for Linux, but definitely crashes under my VS2003.Net. I undid your changes and everything compiles fine again!

F.

cartrite · Post #74by **cartrite** » 11.01.2008, 23:33

I just went out on a limb and installed Microsoft Visual C++ 2005 Express Edition - ENU and the Platform SDK 2003 server sp1. The qt4 build has been humming along now for about 45 minutes. It looks like this is going to work.

It should be done soon.
I hope I can still build Celestia.
cartrite

cartrite · Post #75by **cartrite** » 12.01.2008, 01:32

Well,
I built qt4.3.3
I compiled celestia.pro with msvc 2005
I can't link. :cry:

Why is there references to a libjpeg2.lib???????
I change it to libjpeg.lib and this is what I get.

Code: Select all

        link /LIBPATH:"h:\qt4\lib" /NODEFAULTLIB:libc /NOLOGO /INCREMENTAL:NO /S
UBSYSTEM:WINDOWS /OUT:..\celestia-qt4.exe @C:\DOCUME~1\cartrite\LOCALS~1\Temp\nm
22.tmp
   Creating library ..\celestia-qt4.lib and object ..\celestia-qt4.exp
libjpeg.lib(jerror.obj) : error LNK2019: unresolved external symbol __iob refere
nced in function _output_message
..\celestia-qt4.exe : fatal error LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\l
ink.EXE"' : return code '0x460'

This is becoming a joke.
cartrite

Post #76by **chris** » 12.01.2008, 01:44

cartrite wrote:Well,
I built qt4.3.3
I compiled celestia.pro with msvc 2005
I can't link.
Why is there references to a libjpeg2.lib???????
I change it to libjpeg.lib and this is what I get.
Code: Select all
link /LIBPATH:"h:\qt4\lib" /NODEFAULTLIB:libc /NOLOGO /INCREMENTAL:NO /S UBSYSTEM:WINDOWS /OUT:..\celestia-qt4.exe @C:\DOCUME~1\cartrite\LOCALS~1\Temp\nm 22.tmp Creating library ..\celestia-qt4.lib and object ..\celestia-qt4.exp libjpeg.lib(jerror.obj) : error LNK2019: unresolved external symbol __iob refere nced in function _output_message ..\celestia-qt4.exe : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\l ink.EXE"' : return code '0x460'

This is becoming a joke.
cartrite

Almost there . . . With MinGW I had to use a different libjpeg.lib. You can download it here:

http://www.celestiaproject.net/~claurel/celest ... bjpeg2.zip

--Chris

cartrite · Post #77by **cartrite** » 12.01.2008, 02:23

HOORAAAA!!! It works.

I would quess you need libjpeg2.lib with msvc 2005 too.
A couple of notes. I used the older version of glext.cpp. The old glext file that gave me so much trouble flew right through with this newer compiler. I also added the line /NODEFAULTLIB:libc to the LFlAGS in Makefile.Release. I got a link error from libc without it. I also get a link error from libc when I build it the regular way.

I noticed that msvc 2005 builds differently than the 2003 toolkit. I'll have to reeducate myself here. The 2005 gui is pretty cool. Didn't have that with the 2003 toolkit. I'll have to learn this QT4 software too. I used to play around with Visual Studio 6 a few years back. Starting to like Windows again. :wink:

Thanks Chris, Fridger

cartrite

cartrite · Post #78by **cartrite** » 12.01.2008, 04:05

Chris,
I can confirm that the new glext.cpp works fine with msvc 2005 and QT4.

Edit: I haven't checked glext version 1.15 yet so I just now checked glext version 1.15 now and confirm that I had a link error. So it seems that version 1.16 fixes the link error.

cartrite

Post #79by **t00fri** » 12.01.2008, 09:14

cartrite wrote:HOORAAAA!!! It works.
I would quess you need libjpeg2.lib with msvc 2005 too.
...
Thanks Chris, Fridger

cartrite

Congratulations, cartrite :lol:

-----------------------------------------------------------------------------
I KNEW you would NOT give up despite your repeated respective statements ;-)

...
-----------------------------------------------------------------------------
Let me remind you of this "harmless" sentence in my brief instructions from yesterday morning:

possibly adapt the names of libjpg and|or libpng in celestia.pro, depending on the versions used.

I also had to do this, since I work with my own optimized JPG and PNG libs...

Cheers,
Fridger

Post #80by **t00fri** » 12.01.2008, 09:22

Chris,

this is to confirm that [ unlike 1.15 ], your latest glext.cpp fix (1.16) that arrived here by this morning (10:30 am now), does NOT break my VS2003.Net compilation.

Your new spectral class filter is very instructive, really.

Despite operating the Qt version with all my 64k VT's and all other stuff the fps rates are significantly higher than under same conditions with normal Windows or KDE(Qt3) Linux. I did put some optimization in, however.

The enhancement is like 49 -> 60 fps both under Linux and Windows.

Anyway it all looks neat and works smoothly, both under Linux

++++++++++++++++++++
Actually, how are things with you meanwhile? Did you switch back to VS2005 express??
++++++++++++++++++++

...and just in case, remember that the generation of the project files for the GUI VS200X.Net compiling environment is extremely simple:

> qmake -t vcapp celestia.pro

Bye Fridger