annotate README @ 32:fc2dba4c5a5f
fuck yeah, I fixed the motherfucker, now let's roll
| author |
John Tsiombikas <nuclear@member.fsf.org> |
| date |
Sun, 03 Jul 2011 05:23:30 +0300 |
| parents |
edbfc96fe80d |
| children |
|
| rev |
line source |
|
nuclear@7
|
1 Author: John Tsiombikas
|
|
nuclear@7
|
2 Contact: nuclear@member.fsf.org
|
|
nuclear@7
|
3
|
|
nuclear@7
|
4 Adding window system modules
|
|
nuclear@7
|
5 ----------------------------
|
|
nuclear@7
|
6 Window system modules are detected automatically by configure. For this to work,
|
|
nuclear@7
|
7 each module must be a single file in src/ called wsys_whatever.c.
|
|
nuclear@7
|
8
|
|
nuclear@7
|
9 Somewhere in the module, there must be a comment of the form: /* link-with:
|
|
nuclear@7
|
10 whatever */ where the whatever part is passed to the linker, and is also used to
|
|
nuclear@7
|
11 determine at compile time if the module should be enabled.
|
|
nuclear@7
|
12
|
|
nuclear@7
|
13 Finally the module source code must start by including "config.h", and the rest
|
|
nuclear@7
|
14 of it from that point on must be in a big ifdef USE_WSYS_MODULE_WHATEVER block.
|
|
nuclear@31
|
15
|
|
nuclear@31
|
16 Building on windows
|
|
nuclear@31
|
17 -------------------
|
|
nuclear@31
|
18 If you decide to use the visual studio project files to build sgl, you still
|
|
nuclear@31
|
19 need to run the configure script in order to generate config.h and modules.c.
|
|
nuclear@31
|
20 Msys or cygwin should do the trick.
|
