| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Linking the xts libraries statically into each test program results in a
massive size for the collection of programs. The libraries have been
changed to private libtool modules that default to shared, resulting in
a much smaller installed size.
One consequence of linking to shared objects is that the linker errors
on undefined extern variables. The obsolete and unused startup routines
in linkstart.c had one of these, so they have been removed from the
build.
Next is to create the tet library shared.
|
|
The meanings of the variables were confusing or obfuscating. Now it's
much clearer which libraries are in use.
|
|
Let's use DISPLAY like every other sane X application does, not through a
variable set at configure time.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
|
|
In order to keep the scenarios usable in the source tree and while
installed, install the test programs to subdirectories of $(libexecdir)
matching the source tree. This gives, for example,
/usr/libexec/xts5/Xproto/pAllocColor.
|
|
|
|
One less directory to ascend...
|
|
|
|
|
|
The tset directory was mostly useless and causes extra baggage if the
scenario files are going to be used on an installed package. The test
directories are now flattened into xts5.
|
