quake-devel Mailing List for QuakeForge (Page 258)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Is it ok to apply a change yet?

-r



Hi all,


    I came up with some suggestions for this project last night.  First, we
should use a different name for our executables to distinguish from id's.
The hard part will be figuring out what name to use.  Second, we should put
in a "Classic Quake" mode.  It's not hard to do, just add a qboolean and an
MS_CheckParm and it's all set.  All future work can be preceded by an "if
(!classicmode)"  This may be annoying, but it's necessary.  The problem here
comes in deciding what exactly will be in classic mode and what won't.  I,
being the purist I am, suggest that all new additions, even bugfixes, be
preceded by an "if (!classicmode)".  I'll write a patch adding the qboolean
and MS_CheckParm this afternoon if I can figure out how to use diff.

    I also have some suggestions for rules on writing to CVS that came out
of last night's irc chat.  The more notable and useful ones are as follows:

1. There's a waiting period of at least 1 day before patches are added to
CVS
 2. All patches added to CVS must be preceded by an announcement on the
mailing list.

That's all I've got so far.

theoddone33




On Fri, Dec 24, 1999 at 02:06:41PM +0100, Marcus Sundberg wrote:
> > Out of this I only have one comment, errm, can we please just try and
> > forget that automake even exists?=20
> >
> > In my experience it is a complete horror to work with the moment you ne=
ed
> > to debug something, and sadly you /do/ have to debug things from time to
> > time..
>=20
> What does automake has to do with debugging? Or are you talking
> about debugging the build system?
>=20
> In any case it sounds like you haven't used automake very much.
> Unless you are aiming at only supporting a single platform there
> is nothing that comes even remotely close to the maintainability
> you get when using automake.

I have to agree with Marcus here *gagging and coughing, not sure if from
flu or from general dislike of automake*  Nobody in their right mind uses
automake because they LIKE it.  Most of the time you'll use it because
writing sufficiently portable (across platforms--you still need GNU make
obviously) makefiles is a pain in the ass and the results are usually not
a whole lot more readable than the automake generated variety.  Not as bad
mind you, but not sufficiently better.

There's also the standardization issue, automake is good at making things
work uniformly.

--=20
- Joseph Carter         GnuPG public key:   1024D/DCF9DAB3, 2048g/3F9C2A43
- kng...@de...   20F6 2261 F185 7A3E 79FC  44F9 8FF7 D7A3 DCF9 DAB3
--------------------------------------------------------------------------
It's as BAD as you think, and they ARE out to get you.


This message was sent from Geocrawler.com by "Steven Pinkham" <spi...@bi...>
Be sure to reply to that address.

I must say, it is really cool to be playing one of
my favorite games of all time with a binary I just
compiled myself. ;-)
Sorry, back to coding...
The first merge I would like to make is a few
makefile fixes that have the standard quake
compiling with ease .. I'll post the patch here
first for comment.
BTW, anyone get QW to compile yet? Haven't have
time to mess with that one myself much at all, but
judging by my quick attempt it seems more
buggered..

Geocrawler.com - The Knowledge Archive



On Fri, Dec 24, 1999 at 02:06:41PM +0100, Marcus Sundberg wrote:
> "Zephaniah E. Hull" <wa...@wh...> writes:
<snip>
> > On Fri, Dec 24, 1999 at 12:21:39AM -0800, Joseph Carter wrote:
> > <snip>
> > > but we're planning to dump the whole thing for autoconf and probably
> > > automake at some point anyway so the contents of the thing called
> > > "Makefile" soon won't matter anyway.
> >=20
> > Out of this I only have one comment, errm, can we please just try and
> > forget that automake even exists?=20
> >
> > In my experience it is a complete horror to work with the moment you ne=
ed
> > to debug something, and sadly you /do/ have to debug things from time to
> > time..
>=20
> What does automake has to do with debugging? Or are you talking
> about debugging the build system?

Debugging the build system..
>=20
> In any case it sounds like you haven't used automake very much.

I've used it a good bit, and I know that I will never willingly use it
again..

> Unless you are aiming at only supporting a single platform there
> is nothing that comes even remotely close to the maintainability
> you get when using automake.

This is true for autoconf, however, in my experience, automake is simply
evil..

Zephaniah E. Hull..
>=20
> //Marcus
> --=20
> -------------------------------+------------------------------------
>         Marcus Sundberg        | http://www.stacken.kth.se/~mackan
>  Royal Institute of Technology |       Phone: +46 707 295404
>        Stockholm, Sweden       |   E-Mail: ma...@st...
>=20
> _______________________________________________
> Quake-devel mailing list
> Qua...@li...
> http://lists.sourceforge.net/mailman/listinfo/quake-devel
>=20

--=20
 PGP EA5198D1-Zephaniah E. Hull <wa...@wh...>-GPG E65A7801
    Keys available at http://whitestar.soark.net/~warp/public_keys.
           CCs of replies from mailing lists are encouraged.

Hopefully it is very simple :

just add

 mouse_avail = 1;

in IN_Init() in gl_vidlinuxglx.c

it was left uninitailized to 0 !!

--
il fait bo!



"Zephaniah E. Hull" <wa...@wh...> writes:

> On Fri, Dec 24, 1999 at 12:21:39AM -0800, Joseph Carter wrote:
> <snip>
> > but we're planning to dump the whole thing for autoconf and probably
> > automake at some point anyway so the contents of the thing called
> > "Makefile" soon won't matter anyway.
> 
> Out of this I only have one comment, errm, can we please just try and
> forget that automake even exists? 
>
> In my experience it is a complete horror to work with the moment you need
> to debug something, and sadly you /do/ have to debug things from time to
> time..

What does automake has to do with debugging? Or are you talking
about debugging the build system?

In any case it sounds like you haven't used automake very much.
Unless you are aiming at only supporting a single platform there
is nothing that comes even remotely close to the maintainability
you get when using automake.

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: ma...@st...



Blue Lang wrote:
> 
> MAINDIR=<path_where_you_install_quake/QW>
> 
Make that

MAINDIR=$(shell pwd)

Filip

--
Get a life. Get Windows(tm). It makes you wanna spend a lot less time
with your pc.


<------------------------ Filip Van Raemdonck ----------------------->
fi...@xs...              Helpdesk        Tel: +32/(0)9/265.02.05
http://www.xs4all.be        Webengineering     Fax: +32/(0)9/265.02.50
<--------------------  XS4ALL Internet Belgium ---------------------->



Blue Lang wrote:
> 
> Is anyone planning on splitting the source out and using GNU configure?
> 
IMHO it would be a bad choice in splitting *anything* out, even if using
configure. This is even more true for qw than plain q1. There's lots of
shared stuff in there, and it future patches are more likely to break
things if Windows and Linux source each go their own way.

Filip

--
Get a life. Get Windows(tm). It makes you wanna spend a lot less time
with your pc.


<------------------------ Filip Van Raemdonck ----------------------->
fi...@xs...              Helpdesk        Tel: +32/(0)9/265.02.05
http://www.xs4all.be        Webengineering     Fax: +32/(0)9/265.02.50
<--------------------  XS4ALL Internet Belgium ---------------------->



On Fri, Dec 24, 1999 at 12:21:39AM -0800, Joseph Carter wrote:
<snip>
> but we're planning to dump the whole thing for autoconf and probably
> automake at some point anyway so the contents of the thing called
> "Makefile" soon won't matter anyway.

Out of this I only have one comment, errm, can we please just try and
forget that automake even exists?=20

In my experience it is a complete horror to work with the moment you need
to debug something, and sadly you /do/ have to debug things from time to
time..

Zephaniah E. Hull..

--=20
 PGP EA5198D1-Zephaniah E. Hull <wa...@wh...>-GPG E65A7801
    Keys available at http://whitestar.soark.net/~warp/public_keys.
           CCs of replies from mailing lists are encouraged.

I'm freezing the CVS tree so we can incorporate Deek's and Knghtbr's combined
efforts to merge the trees and make a workable source tree. After it's
inclusion we will discuss and come up with guidelines for CVS patching and
maintainance.

Sincerely,
Nelson Rush (palisade)

--

"Guns don't kill people. It's those damn bullets. Guns just make them go
 really really fast." -- Jake Johanson



On Fri, Dec 24, 1999 at 01:37:36AM -0700, Chris Borowski wrote:
> Same results here with glquake.glx (also Mesa 3.2 and a Voodoo 3).
> Setting "gl_ztrick '0'" in my autoexec.cfg cleared up the flashing
> texture thing, but alas no keyboard or mouse here either. I see that
> the non-X quakes want to use svgalib for keyboard and mouse input.
> Anybody know what the glquake.x11 would like to use for this?
> The gl_ztrick thing makes the game look perfect, so I assume that
> glquake.glx only needs to have the input thing fixed up before it is
> playable.

Add -window to the cmdline.  If you're running a 32bpp xserver like I am
and have MESA_GLX_FX=3Df in your environment you'll get a fullscreen quake
with a working keyboard.  You'll still need the gl_ztrick 0 naturally.  I
also couldn't get _windowed_mouse to work but I haven't tried to track
that down yet.

Good luck, and if you fix the mouse before me please post a diff -u or -c
of it..

--=20
- Joseph Carter         GnuPG public key:   1024D/DCF9DAB3, 2048g/3F9C2A43
- kng...@de...   20F6 2261 F185 7A3E 79FC  44F9 8FF7 D7A3 DCF9 DAB3
--------------------------------------------------------------------------
Moonchild without an opinion? Satan is skating to work tomorrow!
        -- Brett Manz


On Fri, Dec 24, 1999 at 08:59:02AM +0100, Michael Pujos wrote:
> Here's a message I sent to the mesa mailing list:
> 
> 
> I just got the latest Mesa from the 3_2 (stable) branch and compiled it with
> the voodoo driver enabled (I have a voodoo 3)
> 
> Then I compiled glquake.glx from the recently released quake source (after some
> minor Makefile tweaking) so it used mesa 3.1...and it doesnn't quite work:
> glquake launch then the keyboard doesnn't answer...hopefully ctrl-c works.
> I launched a map with glquake.glx +map dm4, then the map launch, still no
> keyboard and all i've got is a bunch of flashing (and wrong) textures...at this
> point the game didnn't crashed (the sound is playing fine) but ctrl-c and now
> it's crashed...
> I don't know if this is a mesa or glquake bug...
> 

Same results here with glquake.glx (also Mesa 3.2 and a Voodoo 3).
Setting "gl_ztrick '0'" in my autoexec.cfg cleared up the flashing
texture thing, but alas no keyboard or mouse here either. I see that
the non-X quakes want to use svgalib for keyboard and mouse input.
Anybody know what the glquake.x11 would like to use for this?
The gl_ztrick thing makes the game look perfect, so I assume that
glquake.glx only needs to have the input thing fixed up before it is
playable.
-- 
Just squeeze your rage into a bitter little ball and
release it at an appropriate time.  Like that day I
hit that referee with a whiskey bottle.  'Member that?
                -- Homer Simpson
=============================================================
PGP key at http://www.gci-net.com/~users/c/chrisb/key.asc
or finger ch...@un...



This is far from perfect.  It hasn't been gmake'ified yet, so it's still
way too long.  Looking at the diff I noticed I removed zoid's credit line
from the top in my mad deletion rampage (sorry Dave) but we're planning to
dump the whole thing for autoconf and probably automake at some point
anyway so the contents of the thing called "Makefile" soon won't matter
anyway.  Haven't touched the QW dir at all because I'm waiting on a merge
with deek tomorrow or so probably which will make anything I'd do to the
QW directory meaningless anyway.

Changes:

  CC is now just gcc instead of some locally installed egcs
    The source built with gcc 2.7.2 and gcc 2.95.something

  removed some paths where they looked useless (not completely done)
  
  removed the glquake (suffixless) build from TARGETS
    Why remove it?  Well in the libc5 days there was really just one
    glquake binary and there were a pair of wrapper shell scripts to make
    it work in 3 different ways.  That's no longer the case.  The
    suffixless glquake binary is useless unless you have a 3dfx card which
    is Voodoo2 or older.  If you have such a card you should be using
    lib3dfxgl.so anyway.
    
  made the names of the binaries created more consistant:
    squake          ->  quake-svga
    quake.x11       ->  quake-x11
    glquake.glx     ->  quake-gl
    glquake.3dfxgl  ->  quake-3dfx
  
  fixed typos like /usr/X11/lib
  
  replaced at least one -lMesaGL with -lGL, use Mesa 3.1!

  removed the damned RPM crap
    Nothing against RPM, but let's keep package building crap out of the
    main Makefiles, okay?  There's better places for it and there's also
    the consideration that autoconf isn't going to put RPM stuff there.

    Also worth noting is that the RPM building was incomplete, binary only
    stuff..  We have source now and everyone else should too!

  removed the -glibc here and there
    We're all using _some_ version of glibc these days I imagine?  Like
    the RPM stuff, keeping it around is only useful if you intend to
    produce binary-only packages (in this case that you intend for lots of
    people to be able to install even if they run antique systems like RH4
    and slackware ;> (sorry, couldn't resist)) so it's best to toss it.
    If you have libc5, you'll get libc5 binaries.  If you have libc6,
    you'll get libc6 binaries.


Caveats:

  as I noted, this isn't quite finished, but what's finished works

  quake-gl gets linked with BOTH svgalib and glide here, no idea why

  the asm fixes for jmp's earlier in the list is still needed to compile
  this thing

  quake-gl apparently doesn't treat all libGL's equally

  quake-gl must be started with -window if you want a working keyboard

  quake-gl doesn't seem to know about _windowed_mouse
  
  quake-3dfx builds because I have lib3dfxgl.so in /usr/lib, if you don't
  it probably won't link and make will die.  Remove it from targets if you
  want, I need to email people at both id and 3dfx about lib3dfxgl.so I
  guess..

  essentially, this is just a makefile, not a complete source fix

-- 
- Joseph Carter         GnuPG public key:   1024D/DCF9DAB3, 2048g/3F9C2A43
- kng...@de...   20F6 2261 F185 7A3E 79FC  44F9 8FF7 D7A3 DCF9 DAB3
--------------------------------------------------------------------------
Steal this tagline.  I did.


On Thu, Dec 23, 1999 at 09:15:05PM -0500, Blue Lang wrote:
> Can someone post a link/copy of the q1 shareware levels? I'm trying to
> hunt them down..

http://tank.debian.net/quake106.zip if you really need to get it from
somewhere.

Please be gentle people, I only have 128k upstream bandwidth and this is
not a small file.


Hmmm, the AI sig generator strikes again.

--=20
- Joseph Carter         GnuPG public key:   1024D/DCF9DAB3, 2048g/3F9C2A43
- kng...@de...   20F6 2261 F185 7A3E 79FC  44F9 8FF7 D7A3 DCF9 DAB3
--------------------------------------------------------------------------
* cesarb wonders if in less than a week Carmack will end up receiving in
  e-mail a courtesy copy of a version of the Quake source which is four
  times faster than what went out of his virtual hands...


On Thu, Dec 23, 1999 at 10:40:21PM -0600, Dan Olson wrote:
> Hi guys,
>  This is in relation to a post on the message board.  I don't have (and
> can't get) a sourceforge account, so I can't post in reply.  I don't know if
> the guy's on the mailing list or not, but perhaps one of you could kindly
> post this reply on the messageboard.

Has been posted.. Thanks...


				Steve



Hi guys,
 This is in relation to a post on the message board.  I don't have (and
can't get) a sourceforge account, so I can't post in reply.  I don't know if
the guy's on the mailing list or not, but perhaps one of you could kindly
post this reply on the messageboard.

He inquires why GLQuake won't work with his i740.  Under windows, you have
to delete the "opengl32.dll" that's in the same directory as quake for it to
work with an i740.

Happy source hacking

DDOI




On Thu, 23 Dec 1999, Steve Pinkham wrote:

> Here's my diff for the Makefile.linuxi386 file in the WinQuake dir
> (gotta change the name on that dir, BTW ;-)  The version I would commit
> would have more generic names for the dirs(and better comments if anyone
> feels like.. These are from my tired silly "took a final today" brain). 
> Also, we need a little text file on how to compile for linux.  (my ICQ
> uin is 4722973 if anyone wants to do this in more real time.. Do we have
> an IRC channel yet?) 

I agree.. actually, we need a configure script ;). I'll try and work one
out.. 

> +#In most cases this is unnecessary, as it will probably be /usr/local/lib
>  MESA_DIR=/usr/local/src/Mesa-2.6


Isn't the MESA_DIR define there for includes and not for the lib?

Thanks!

-- 
Blue Lang, Unix Systems Administrator, QSP Inc. - Raleigh, NC
Phone: 919.875.6994




Here's my diff for the Makefile.linuxi386 file in the WinQuake dir (gotta change the name on that dir, BTW ;-)
The version I would commit would have more generic names for the dirs(and better comments if anyone feels like.. These are from my tired silly "took a final today" brain).
Also, we need a little text file on how to compile for linux.
(my ICQ uin is 4722973 if anyone wants to do this in more real time.. Do we have an IRC channel yet?)

				Steve

--- Makefile.linuxi386  Thu Dec 23 21:21:43 1999
+++ Makefile    Thu Dec 23 22:19:02 1999
@@ -25,16 +25,25 @@
 endif
 NOARCH=noarch

-MOUNT_DIR=/grog/Projects/WinQuake
+#The dir you are in, ala /(place you unpacked source)/WinQuake
+MOUNT_DIR=/home/spinkham/work/q1/WinQuake
+
+#Used for making quake1 rpm's with the original data files, currently not used
+#in this project
 MASTER_DIR=/grog/Projects/QuakeMaster
+
+#Dir where the mesa lib you want to link is found.
+#In most cases this is unnecessary, as it will probably be /usr/local/lib
 MESA_DIR=/usr/local/src/Mesa-2.6
-TDFXGL_DIR = /home/zoid/3dfxgl
+
+#Where the file "lib3dfxgl.so" is found.  I got mine out of the quake2 distro.
+#For 3dfx miniport
+TDFXGL_DIR =/usr/local/games/quake2

 BUILD_DEBUG_DIR=debug$(ARCH)$(GLIBC)
 BUILD_RELEASE_DIR=release$(ARCH)$(GLIBC)

-EGCS=/usr/local/egcs-1.1.2/bin/gcc
-CC=$(EGCS)
+CC=gcc

 BASE_CFLAGS=-Dstricmp=strcasecmp
 RELEASE_CFLAGS=$(BASE_CFLAGS) -g -mpentiumpro -O6 -ffast-math -funroll-loops \
@@ -45,9 +54,9 @@
 XLDFLAGS=-L/usr/X11R6/lib -lX11 -lXext -lXxf86dga
 XCFLAGS=-DX11

-MESAGLLDFLAGS=-L/usr/X11/lib -L/usr/local/lib -L$(MESA_DIR)/lib -lMesaGL -lglide2x -lX11 -lXext -ldl
-TDFXGLLDFLAGS=-L$(TDFXGL_DIR)/release$(ARCH)$(GLIBC) -l3dfxgl -lglide2x -ldl
-GLLDFLAGS=-L/usr/X11/lib -L/usr/local/lib -lGL -lX11 -lXext -ldl -lXxf86dga -lXxf86vm -lm
 GLCFLAGS=-DGLQUAKE -I$(MESA_DIR)/include -I/usr/include/glide

 DO_CC=$(CC) $(CFLAGS) -o $@ -c $<



I had to make the following patches to get WinQuake to build on an ultrasparc
running Solaris 2.7

Loring

*** ../cvs/q1/WinQuake/net_udp.c	Wed Dec 22 05:19:48 1999
--- ./net_udp.c	Wed Dec 22 13:38:59 1999
***************
*** 20,25 ****
--- 20,29 ----
  // net_udp.c
  
  #include "quakedef.h"
+ #ifdef sun
+ /* Sun's model_t in sys/model.h conflicts w/ Quake's model_t */
+ #define model_t sunmodel_t
+ #endif
  
  #include <sys/types.h>
  #include <sys/socket.h>
***************
*** 28,33 ****
--- 32,41 ----
  #include <sys/param.h>
  #include <sys/ioctl.h>
  #include <errno.h>
+ 
+ #ifdef sun
+ #undef model_t
+ #endif
  
  #ifdef __sun__
  #include <sys/filio.h>
*** ../cvs/q1/WinQuake/vid_sunxil.c	Wed Dec 22 05:23:49 1999
--- vid_sunxil.c	Thu Dec 23 21:50:08 1999
***************
*** 20,27 ****
  // vid_sunxil.c -- uses X to setup windows and XIL to copy images (scaled as needed) 
  // 		   to screen
  
! #define _BSD
! #define BYTE_DEFINED 1
  
  #include <sys/time.h>
  #include <sys/types.h>
--- 20,28 ----
  // vid_sunxil.c -- uses X to setup windows and XIL to copy images (scaled as needed) 
  // 		   to screen
  
! // XXX - Not needed in Solaris 2.7
! //#define _BSD
! //#define BYTE_DEFINED 1
  
  #include <sys/time.h>
  #include <sys/types.h>



Hi,

is it possible to compile a perfectly valid qwsv for linux even if you
don't have all those X11 and mesa-libs ?

/-------------------------------------------------------------------\
| page:  http://www.ocrana.de     |           |            _ \      |
|                                 |       __| |      _ \  |   |     |
| mail:  sL...@oc...           |     \__ \ |     (   | ___/      |
|                             cya |     ____/_____|\___/ _|         |
\-------------------------------------------------------------------/





All I did was change 

MAINDIR=<path_where_you_install_quake/QW>

and changed the calls to -L/usr/X11/lib to /usr/X11R6/lib

does anyone know of any linuxes that don't include ldconfig? i think we
could get rid of the hardcoded lib paths for mesa and X.. those shuold
(usually) be system-wide.. 

--
Blue Lang, Unix Systems Administrator, QSP Inc. - Raleigh, NC
Phone: 919.875.6994




Can someone post a link/copy of the q1 shareware levels? I'm trying to
hunt them down..

thanks!

--
Blue Lang, Unix Systems Administrator, QSP Inc. - Raleigh, NC
Phone: 919.875.6994




For DirectSound under WinQuake, etc I recommend the following change.

line 265 of snd_win.c becomes:

if (DS_OK != pDS->lpVtbl->SetCooperativeLevel (pDS, mainwindow,
DSSCL_NORMAL))

I recommend removing the option for -primarysound (the else of the if block
started on line 305 of snd_win.c

This patch enables outside applications like TeamStream and Roger Wilco to
work more effectively.  Must be applied to all Windows clients
(QW/WinQuake).

-Robert




Yes.  Please post.  I've done some fiddling with it
but haven't had the time to make it compile yet.  

later,
Chad

--- Blue Lang <bl...@ca...> wrote:
> 
> Just got Q1 compiled on Linux, and was wondering if
> I should post a
> Makefile patch and quick readme for it?
> 
> Is anyone planning on splitting the source out and
> using GNU configure?
> 
> 
> --
> Blue Lang, Unix Systems Administrator, QSP Inc. -
> Raleigh, NC
> Phone: 919.875.6994
> 
> 
> _______________________________________________
> Quake-devel mailing list
> Qua...@li...
>
http://lists.sourceforge.net/mailman/listinfo/quake-devel
> 

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




1999	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (535)
2000	Jan (1127)	Feb (362)	Mar (529)	Apr (752)	May (487)	Jun (329)	Jul (190)	Aug (115)	Sep (53)	Oct (52)	Nov (345)	Dec (203)
2001	Jan (240)	Feb (317)	Mar (212)	Apr (57)	May (151)	Jun (70)	Jul (82)	Aug (23)	Sep (56)	Oct (35)	Nov (22)	Dec (60)
2002	Jan (33)	Feb (21)	Mar (16)	Apr (14)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2003	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

quake-devel Mailing List for QuakeForge (Page 258)

quake-devel — Main discussion forum. Watch the fur fly.