summaryrefslogtreecommitdiff
path: root/debian/README.build
blob: b44a4c42ef2104a67756423837bbcccb5896cf87 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
I have added a few new configuration files to the configs directory:

    There's a base configuration, debian, which sets things up for
    building in a debian environment.

    There's also a debian-static configuration, which is for static
    building.

All the others are derived from one of these two configurations.

The platform-specific optimizations go into a debian-foo_ARCH file, like
debian_i386 or debian_sparc.  You can name this files whatever you want,
but the last token must be a debian arch name.  Note the "_"!  These
will be picked up automatically by the debian/rules.

In order to actually install the new files, you need to edit
debian/libdir.map, the format is:

    target-name libdir package package-dev

The architecture optimized libraries should go under
/usr/lib/<something>, where <something> matches the optimizations used,
e.g. "cmov" or "v9".

Only packages listed in the control file *and* libdir.map are actually
built.  That means that even if debian/libdir.map lists
libgl1-random-stuff, if libgl1-random-stuff is *not* listed in
debian/control it *won't* be built.  The other way around, if
libgl1-random-stuff is listed in debian/control but there's no entry for
it in debian/libdir.map it *won't* be built.

Again...

If the libdir.map file doesn't mention your (lib)-(config), e.g.
gl-debian_i386, THE TARGET WON'T BE BUILT.

If the package listed in libdir.map is not listed in debian/control, THE
TARGET WON'T BE BUILT.

For architectures where glide3 is available an extra package is built
(iff this is the mesa-legacy source package).  The list of supported
architectures in found in the control file.

There's an alioth project for this package:
http://alioth.debian.org/projects/pkg-mesa/