| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Commit a2826324 only actually changed the Xproto tests to use the xts
shared libraries. This does it for the rest of the tests. On my x86_64
linux box compiling at the default -g -O2, the installed size has gone
from 237MB to 72MB. Yay.
Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
|
|
Making libapi shared saves quite a bit of space since it's linked into
every test program. However, parts of the API are intended to be linked
statically into the program, so libapi and libtcm have been split into
static and shared (_s) portions.
In order to satisy undefined extern variables with shared libraries,
tet_pname and tet_thistest have been added to tcc and exported.
Hopefully, more code can be moved into the shared _s portion with just
small stubs linked statically into the tests.
Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
|
|
There are still two left:
XDrawRectangle/XDrawRectangle.c:4211: warning: unused variable ‘jssav’
XDrawRectangles/XDrawRectangles.c:4292: warning: unused variable ‘jssav’
These are a little harder to fix because the declaration is generated but jssav
is only used in some of the tests.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Acked-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
tprogs lists the test programs without $(EXEEXT), so substituting
the $(EXEEXT) with .c to get BUILD_SOURCES fails to work correctly
when $(EXEEXT) isn't empty
Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
|
|
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.
|
|
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.
|
