General Thread

by Aardappel on 01/05/2002 01:55, 15499 messages, last message: 12/08/2021 21:22, 8826810 views, last view: 12/09/2021 06:28

for questions, announcements etc.

   Board Index   

#1711: Re: Cube KDE panel applet - Version 1.1 ready

by D.plomat on 07/05/2003 17:51, refers to #1710

Well, i didn't really checked this, i just made the #includes that were in the KDE-develop docs, and added the AC_PATH_QT_MOC_UIC in Makefile.am. I think normally it uses the most recent version installed on the system. you need the qt-devel version of the libs.
However, hungerburg told me he has to add a --with-qt-dir=/usr/share/qt3 option to the configure on a debian, i thought that adding the AC_PATH_QT_MOC_UIC would do the trick, but didn't tested it. What distro are you using?

reply to this message

#1712: Re: Cube KDE panel applet - Version 1.1 ready

by Thalion on 07/05/2003 22:27, refers to #1711

Mandrake 9.1. And yes, I do have qt-devel package installed.

reply to this message

#1713: Re: Cube KDE panel applet - Version 1.1 ready

by D.plomat on 07/06/2003 19:56, refers to #1712

Looked in some KDE development forum, qt3 is backward source compatible with qt2, but not binary. Maybe there's something to add in Makefile.am, but i don't think so. The fun thing is that i've used a KDE applet tutorial that was linked from KDE3 devel page, but some examples were on KDE2. When i'm back at home, i'll check if i've also qt2 libs installed and compile with qt3 only. Did you try with
./configure -prefix=/usr --with-qt-dir=/usr/lib/qt3 or /usr/lib/qt3/lib ?
That build system is really something... it took me ~3 times much time on the build system than with the simple C++ code of my applet ;)

reply to this message

#1714: Re: Cube KDE panel applet - Version 1.1 ready

by D.plomat on 07/06/2003 20:20, refers to #1712

Just got confirmation from hungerburg that we still need to specify the qt-dir. Still, don't understand why it doesn't need it on my RH 7.3, as the original files of the buid system weren't from my system, but some packages from KDE site.

reply to this message

#1715: help me on running cube

by Levelworm on 07/07/2003 13:38

well hello guys!
i own a p3550+128+tnt2 pc(win98) and can't run cube well.
it's like a hall of mirror and it mess up with my desktop.
i've checked the docs and changed some of the options.
help me plzz!

reply to this message

#1716: Re: help me on running cube

by D.plomat on 07/07/2003 13:56, refers to #1715

Searching the forum for "tnt2" brings you this amazing answer:

-you can download the latest drivers for your tnt2 on http://www.nvidia.com and install them on your system.

Happy frags :)

reply to this message

#1717: Re: Cube KDE panel applet - Version 1.1 ready

by D.plomat on 07/07/2003 20:27, refers to #1710

Have removed the KDE2-compat & Qt2 stuff from my system, it still compiles and run well. Also added the --with-qt-dir instruction on the installation section of the web page. Would you please send me, or give me the name and url of a Qt program you compiled on your system, so that i can check the Makefile.am, configure.in etc...?

reply to this message

#1718: Compiling Cube In Linux

by pushplay on 07/10/2003 08:20

Now that I have Cube compiling with mingw and something worth compiling, I'd like to compile it in linux. Where do I find the libraries and header files necessary to do this? I tried searching the net for it and came up empty handed.

reply to this message

#1719: Sniping...

by TheRealNitrocloud on 07/10/2003 09:08

I\\\'ve found some long distances in some maps, and dificulty picking off people at such long distances. So I created a script to add to your config file to emulate a zoom feature. This also can knock down mouse sensitivity to let you not lose control. The script is as follows:

//Sniper Script
alias in [
fov 20
sensitivity 1
]
alias out [
fov 100
sensitivity 3
]
bind Q in
bind E out

reply to this message

#1720: Re: Compiling Cube In Linux

by Thalion on 07/10/2003 10:02, refers to #1718

The makefile should be there. As for the libraries, you will need: ENet, SDL, SDL_image, SDL_mixer, zlib, and OpenGL. ENet is included, and is compiled automatically when you compile Cube. OpenGL and zlib I think you do have. =) So you only need SDL (http://www.libsdl.org), SDL_image (http://www.libsdl.org/projects/SDL_image), and SDL_mixer (http://www.libsdl.org/projects/SDL_mixer).

That should be it.

reply to this message

#1721: Re: Compiling Cube In Linux

by pushplay on 07/10/2003 10:33, refers to #1720

Actually... I don't have whatever I need to have to compile OpenGL. I don't know if I have zlib since I don't get passed the OpenGL needing part.

reply to this message

#1722: Re: Sniping...

by spentron-peanutbutter on 07/10/2003 16:41, refers to #1719

That's one way to do it but ...

The standard autoexec zooms on Q+mousewheel.

My latest autoexec, avail. on my page, zooms on mousewheel alone and compensates the mouse sensitivity the whole way. Pressing the wheel button toggles from this zoom to a preset fov. 4 weapons keys are added, 3 of which double as mousewheel editing in edit mode (ideal location for both).

I don't use mousewheel weapons, though, so others may not like this. Also, I don't use WASD in Cube so maybe I shouldn't have changed right mouse button from jump to another weapon function (the one I'd normally put on W).

Also have a mousewheel entities function not in the downloads. I see little download activity, would anyone prefer the above items changed if I come up with new versions?

reply to this message

#1723: Re: Compiling Cube In Linux

by Thalion on 07/10/2003 20:02, refers to #1721

I think you should install Mesa if you need the OpenGL headers. It overwrites NVidia's drivers, though, so these have to be reinstalled as well.

You have zlib almost for sure, it's so widely used that all distro makers include it...

reply to this message

#1724: Re: Compiling Cube In Linux

by pushplay on 07/10/2003 23:59, refers to #1723

Oh man. Installing nvidia drivers was a big enough pain in the ass the first time.

reply to this message

#1725: Re: Compiling Cube In Linux

by D.plomat on 07/11/2003 00:46, refers to #1724

I also have nvidia drivers... didnt' had something to do about it for compiling, cause it's already here.
I had the Mesa libs already before installing, so maybe as Thalion says there are still some headers on my machine that remains from Mesa.
I'm on a RH7.3 (with lots of libs -binary- updated, but this doesn't really matter). You just have to install the *-devel.rpm packages to compile Cube, as you would need the *.rpm packages to run Cube.
I just went into source/src and did 'make', and get the 'cube_client' and 'cube_server' binaries.
What error messages do you get from make?
If it's OGL/Mesa related, maybe you can extract some files from the Mesa RPMs without overwriting your nvidia drivers installation.

reply to this message

#1726: Re: Compiling Cube In Linux

by pushplay on 07/11/2003 05:58, refers to #1725

I don't want to boot into linux just to get the error message back, but it was looking for an OpenGL header file and didn't find it. I'm tempted to just release with the win binaries and source for the linux users. Linux users like painful install processes anyways, right?

reply to this message

#1727: Re: Compiling Cube In Linux

by Thalion on 07/11/2003 09:14, refers to #1726

That was exactly what I experienced. My solution was to install Mesa, then NVidia.

Oh, BTW, what's the problem with the drivers? They are self-installing, after all. Just as long as you're root... =)

reply to this message

#1728: Re: Compiling Cube In Linux

by pushplay on 07/11/2003 10:54, refers to #1727

Last time I installed the nvidia drivers I had to edit some config file by hand. If you don't know what you're doing that's a pretty big deal.

reply to this message

#1729: Re: Compiling Cube In Linux

by D.plomat on 07/11/2003 12:26, refers to #1728

I suppose it was /etc/modules.conf and/or /etc/X11/XF86Config-4.
When you install nvidia drivers, it can be done via self-extractor/installer or rpm package(i used this). But you still need a line in modules.conf to tell the kernel to load the kernel part of the driver on startup, then specify in XF86Config-4 the X server to use this driver, and activate its GLX extension.
If i remember correctly, there also are some headers in some nvidia packages, and also in mesa, but there are correct OGL headers already included in Cube source to avoid missing with nvidia/Mesa etc...
Well a moment you're running Linux, if you can note the error and missing file name, i can probably give you the way to install it on your system without interfering with nvidia/mesa.
Or... i you want, you can send me the sources and i can compile them for you, and send you back the cube_client & cube_server binaries.
On my system i just
cd cube/source/src
make
and it compiles in <10 sec :D

reply to this message

#1730: Strange place for GL headers... not very intuitive i agree

by D.plomat on 07/11/2003 15:39

First i was wondering why don't i have something like OpenGL-devel or Mesa-devel on my machine, so i assumed Cube compile needed only those in it's source dir.

Looks like they are in the package XFree86-devel, just take a look at the very end of the page, the file list: one of those could be what make misses.

http://fr2.rpmfind.net//linux/RPM/redhat/9/i386/XFree86-devel-4.3.0-2.i386.html

/usr/include/GL
/usr/include/GL/GLwDrawA.h
/usr/include/GL/GLwDrawAP.h
/usr/include/GL/GLwMDrawA.h
/usr/include/GL/GLwMDrawAP.h
/usr/include/GL/gl.h
/usr/include/GL/glext.h
/usr/include/GL/glu.h
/usr/include/GL/glx.h
/usr/include/GL/glxext.h
/usr/include/GL/glxint.h
/usr/include/GL/glxmd.h
/usr/include/GL/glxproto.h
/usr/include/GL/glxtokens.h
/usr/include/GL/osmesa.h

As they're only headers, not libraries/binaries, they won't mess up your nvidia drivers. As they're not used by the system (except when you compile an OGL app), you can safely make a backup copy of /usr/include/GL before.
So it looks like you just have to find and install the XFree86-devel package corresponding to your distro version on the CD or with http://rpmfind.net if you're using a Mandrake or RedHat

For zlib, Thalion, i think that if you don't choose the 'development station' option during the install, most distro will install only zlib package (binary library), not zlib-devel one (headers, api-specific build tools etc). I may be wrong, but i believe that if you need packages a and b to run app y, then you need packages a-devel and b-devel to compile y. At least, it looks like RH and Mdk does this way (this may sound total nonsense for a Gentoo or LFS user ;) don't know for debian/suse/slack...)

reply to this message

   Board Index