[Gtkradiant] 1.3.4-nightly and Linux

[Timothee Besset]

quick FYI:

1.3 / trunk is the developement version. There is no release date
scheduled for it. The GL fixes we talked about need to be done on the
Stable-1_2 branch.

TTimo

On Wed, 16 Oct 2002 15:54:27 +0200
David Olofson <david.olofson@reologica.se> wrote:

> 
> (Not much spare time, so no patches today.)
> 
> I grabbed the development CVS tree yesterday, and noticed a few things:
> 
> 	1. There seems to be no "-I/usr/X11R6/include" anywhere. Had
> 	   to add that, as Mandrake (and Red Hat and many others) put
> 	   GL and stuff in there. Where would be the *correct* place
> 	   (and way) to add it? (I'm an autotools guy - no experience
> 	   with cons, and 'man cons' doesn't seem to suggest anything
> 	   that would fit into the current scripts.)
> 
> 	2. _exit() is used in some file, but needs unistd.h.
> 	   Is that really intended? Where (and what!) is _exit() on
> 	   Win32? (I suppose I can't just add #include <unistd.h>
> 	   without an #ifdef. :-)
> 
> 	3. The q3map (IIRC) module uses ExtractFileName() without
> 	   linking with anything that provides it. Adding cmdlib to
> 	   the LDFLAGS seems to work, although I haven't done much
> 	   testing.
> 
> 	4. parse.cpp in mapq3 uses an extern declaration instead of
> 	   including cmdlib.h. (Naughty! :-) Why?
> 
> 	5. Ok, if you think tabs are 2 characters wide, fine ;-)
> 	   but why is the source flooded with tabs, despite the
> 	   "Source files formating" entry in the FAQ saying that
> 	   only spaces should be used? (I hate spaces and small
> 	   tabs - but mixing them is even worse! :-)
> 
> 	6. I get *lots* of warnings about missing linefeeds at EOF.
> 	   Mind if I fix them while at it?
> 
> 	7. IMHO, "-Wall -Werror" (for gcc) is reasonable to use
> 	   during development. In my experience, that eliminates
> 	   many bugs before you even get the code to compile. Can
> 	   I start eliminating warnings if I'm bored some day? :-)
> 
> 
> That's about it... I got 1.3.4 to run, but I haven't implemented the 
> G400/FireGL "fix" yet.
> 
> Speaking of which, either I'm blind, or I didn't get a clear answer; Is 
> there a real reason why GL_LINE is used for culled faces in many places - 
> or are there even places where these faces are *not* culled?
> 
> Or; should the "fix" be optional and show up in the user preferences 
> dialog?
> 
> 
> //David Olofson - Programmer, Composer, Open Source Advocate
> 
> .- Coming soon from VaporWare Inc...------------------------.
> | The Return of Audiality! Real, working software. Really!  |
> | Real time and off-line synthesis, scripting, MIDI, LGPL...|
> `-----------------------------------> (Public Release RSN) -'
> .- M A I A -------------------------------------------------.
> |    The Multimedia Application Integration Architecture    |
> `----------------------------> http://www.linuxdj.com/maia -'
>    --- http://olofson.net --- http://www.reologica.se ---
> 
> _______________________________________________
> Gtkradiant mailing list
> Gtkradiant@zerowing.idsoftware.com
> http://zerowing.idsoftware.com/mailman/listinfo/gtkradiant
>