8b4e6dc5a382a83137a9b17de11986635d295f28
[mesa.git] / docs / README.DJ
1 Mesa 4.0 DOS/DJGPP Port version 0.4
2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3
4
5
6 Description:
7 ~~~~~~~~~~~~
8
9 Well, guess what... this is the DOS port of MESA 4.0, for DJGPP fans... Whoa!
10
11
12
13 Legal:
14 ~~~~~~
15
16 MESA copyright applies.
17
18
19
20 Installation:
21 ~~~~~~~~~~~~~
22
23 Type "make -f Makefile.DJ" to compile the libraries. Long filename support is
24 required during compilation. Also, you must have the DXE2 package (available
25 on SimTel.Net, courtesy of Andrew Zabolotny) installed in order to build the
26 dynamic modules; if you encounter errors, you can fetch a patched version from
27 my web page.
28 The demos are not built automagically (see Pitfalls below). To make them, use
29 one of the following rules:
30 Static:
31 gcc -o OUT.exe IN.c -lglut -lglu -lgl
32 Dynamic:
33 gcc -o OUT.exe -include dmesadxe.h IN.c -ligl -liglu -liglut -ldl
34 Usage of the dynamic modules requires three things:
35 - include DMESADXE.H in one of the sources, so references inside
36 dynamic modules will get resolved (or use `-include' directive)
37 - link against import libraries (libIgl*.a) and LIBDL.A, which will do
38 the dynamic linkage job for you
39 - put the DXEs somewhere along the library path (LD_LIBRARY_PATH) or
40 in the current directory
41
42 Tested on:
43 CPU: Intel Pentium w/ MMX @166 MHz
44 Mainboard: ViA Apollo VP2 w/ 128 MB SDRAM
45 Video card: Matrox Millenium 2064W w/ 2048 kB WRAM, BIOS v3.0
46 DJGPP: djdev 2.03 + gcc v3.0.3 + make v3.79
47
48
49
50 libGL (the core):
51 ~~~~~~~~~~~~~~~~~
52
53 Of course, MESA 4.0 core sources are required. It will probably work with
54 MESA 3.5, but not a chance with earlier versions due to major changes to the
55 MESA driver interface and the directory tree. All should compile succesfully.
56
57 The driver has its origins in ddsample.c, written by Brian Paul and found by
58 me in MESA 3.4.2. I touched almost all the functions, changing the coding
59 style :-( Sorry!
60
61 Pitfalls:
62 1. The current version supports only RGB[A] modes, for it made no sense to me
63 to endorse color-index (aka palette) modes.
64 2. Single-buffered is not allowed at all. Until I can find a way to use *REAL*
65 hardware acceleration, it won't get implemented.
66 3. Another weird "feature" is that buffer width must be multiple of 4 (I'm a
67 lazy programmer and I found that the easiest way to keep buffer handling at
68 peak performance ;-).
69
70
71
72 libGLU:
73 ~~~~~~~
74
75 Mesa GLU sources are required. No comment!
76
77
78
79 libGLUT (the toolkit):
80 ~~~~~~~~~~~~~~~~~~~~~~
81
82 Well, this "skeletal" GLUT implementation is not mine. Thanks should go to
83 Bernhard Tschirren, Mark Kilgard, Brian Paul and probably others (or probably
84 not ;-). I only changed it to be self-standing (Allegro-free). The keyboard,
85 mouse and timer drivers were inspired from an old project of mine (D3Xl) and
86 fixed with some Allegro "infusions"; I deeply thank to Shawn Hargreaves et co.
87
88 My keyboard driver used only scancodes, but since GLUT requires ASCII values
89 for keys, I borrowed the translation tables (and maybe more) from Allegro.
90 Ctrl-Alt-Del (plus Ctrl-Alt-End, for Windows users) will shut down the GLUT
91 engine unconditionally: it will raise SIGINT, which in turn will call the
92 destructors (let's hope), thus cleaning up your/my mess ;-) NB: since the
93 DJGPP guys ensured signal handlers won't go beyond program's space (and since
94 dynamic modules shall) the SIGINT can't be hooked (well, it can, but it is
95 useless), therefore you must live with the 'Exiting due to signal SIGINT'
96 message...
97
98 The mouse driver is far from complete (lack of positioning, drawing, etc),
99 but is enough to make almost all the demos work.
100
101 The timer is pretty versatile for it supports multiple timers with different
102 frequencies. It may not be the most accurate timer in the known universe, but
103 I think it's OK. Take this example: you have timer A with a very high rate,
104 and then you have timer B with very low rate compared to A; now, A ticks OK,
105 but timer B will probably loose precision!
106
107 As an addition, stdout and stderr are redirected and dumped upon exit. This
108 means that printf can be safely called during graphics, but all messages come
109 in bulk! A bit of a hack, I know, but I think it's better than to miss them
110 at all. "Borrowed" from RHIDE (Robert Hoehne) or SETEDIT (Salvador Eduardo
111 Tropea)... I'm not sure.
112
113 Window creating defaults: 640x480x16 at (0,0), 8-bit stencil, 16-bit accum.
114 However, the video mode is chosen in such a way that first window will fit.
115
116
117
118 History:
119 ~~~~~~~~
120
121 v0.1 feb-2002 initial release
122 v0.2 feb-2002 + fast triangle rasterizers
123 + enabled sw and 1.3 extensions
124 + hardware acceleration: FreeBE/AF
125 + single-buffer modes (15-, 16-, and 32-bit)
126 * video mode is set by CreateVisual, not MakeCurrent
127 * internal changes to support multi-buf (unfinished)
128 ! fixed some alpha issues... (thanks, Brian)
129 + glut has now an internal timer
130 * glut changed to support multi-window (unfinished)
131 ! minor PC_HW corrections
132 v0.3 mar-2002 - removed FreeBE/AF code
133 - removed single-buffer modes
134 v0.4 mar-2002 + dynamic module support
135
136
137
138 Contact:
139 ~~~~~~~~
140
141 Name: Borca Daniel
142 E-mail: dborca@yahoo.com
143 WWW: http://www.geocities.com/dborca/