summaryrefslogtreecommitdiff
path: root/configure.ac
AgeCommit message (Collapse)AuthorFilesLines
2011-12-22configure.ac: Require libXau.Cyril Brulebois1-1/+1
It is used in several places, without an explicit dependency. Signed-off-by: Cyril Brulebois <kibi@debian.org>
2011-12-22configure.ac: Quote argument to m4_pattern_forbid.Cyril Brulebois1-1/+1
Without this, configure spits out: ./configure: line 12801: ac_fn_c_check_member: command not found ./configure: line 12815: ac_fn_c_check_type: command not found Also anchor the pattern to make it stricter. Signed-off-by: Cyril Brulebois <kibi@debian.org>
2011-05-26configure: Quote argument to m4_pattern_forbid.Cyril Brulebois1-1/+1
Without this, configure spits out: | ./configure: line 12748: ac_fn_c_check_member: command not found | ./configure: line 12762: ac_fn_c_check_type: command not found Signed-off-by: Cyril Brulebois <kibi@debian.org> Tested-by: Aaron Plattner <aplattner@nvidia.com> Reviewed-by: Aaron Plattner <aplattner@nvidia.com> Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
2011-05-24Bump version to 0.99.1Aaron Plattner1-1/+1
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
2010-09-16[dist] Don't configure directories that aren't distributed.Aaron Plattner1-4/+0
These four directories are not included in their respective SUBDIRS, which means they aren't built and aren't included in the distribution tarball. configure.ac still tries to generate their Makefiles, though, which causes configure failures when run from the dist tarball: config.status: error: cannot find input file: `src/tet3/inetlib/Makefile.in' config.status: error: cannot find input file: `src/tet3/servlib/Makefile.in' config.status: error: cannot find input file: `xts5/src/libXtaw/Makefile.in' config.status: error: cannot find input file: `xts5/src/libXtmu/Makefile.in' Fix this by just deleting those line. The corresponding Makefiles aren't used. Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
2010-09-14Build mc using the build architecture compilerAaron Plattner1-0/+15
When cross-compiling, we need to use the build compiler instead of the host compiler because mc is run during the build step to generate .c files from .m files. Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
2010-06-30Double-use the README as man-page.Peter Hutterer1-0/+19
If asciidoc and xmlto is available at install time, convert the README to a man page. The autotool hack for this is a bit complicated, but does the job. It's essentially copied from libXi that uses asciidoc + xmlto for man page generation as well. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Dan Nicholson <dbn.lists@gmail.com>
2010-06-21Roll back version to pre-1.0Dan Nicholson1-1/+1
Although it would be nice to assume that xts is ready for a milestone 1.0 release, the reality is that it's definitely still rough and will need a couple prereleases to settle down. Apologies to anyone who tried to package this already. Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
2010-06-21Rename the package to xts, the X Test SuiteDan Nicholson1-2/+2
This being the X Test Suite, and not XTest the extension, it is more appropriate to have the package name be "xts". That's what it's called internally, anyway. Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
2010-05-26xts: Introduce check.sh wrapper script for in-tree testingDan Nicholson1-0/+5
Having all the commands and environment variable overrides for in-tree testing in the Makefile was nice, but a wrapper script means you can do in-tree testing with or without the "make check" machinery. Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
2010-02-21xts5: Really fix silent rules with older automakeDan Nicholson1-1/+2
When using an older automake, the AM_SILENT_RULES macro is not used, but the custom silent rule for mc uses the variable AM_DEFAULT_VERBOSITY. Make sure it's defined even without AM_SILENT_RULES. Tested-by: Pat Kane <pekane52@gmail.com>
2010-02-17Add defines for default TET directoriesDan Nicholson1-0/+3
Not used yet, but will be much better than constant getenv("TET_ROOT").
2010-02-17xts5: Build and install vswrpt report analyzerDan Nicholson1-0/+1
This will be renamed to xts-report, but it has some clever argv[0] matching that prevents it for now. Also fixes a broken comment from an RCS ID removal.
2009-10-14xts5: Drop XP pkg-config checkDan Nicholson1-1/+0
The XP check for protocol tests in configure was grabbing the same packages as the general XTS check. Consolidate them.
2009-10-10tet: Allow for executables outside of TET_ROOT by defaultDan Nicholson1-0/+1
tet is really built around the notion that all the source, programs, data and output will all live in a single tree. However, often times the test programs are built and/or installed in a separate location. This can be worked around with various environment variables or command line options, but it would be better to build this behavior in by default. This introduces TET_EXEC_ROOT, which specifies the base directory for tet test programs. The tests will be found in the test suite subdirectory of TET_EXEC_ROOT. E.g., $TET_EXEC_ROOT/xts. The default here is to have TET_ROOT=$datadir and TET_EXEC_ROOT=$libexecdir.
2009-10-10Use a default TET_ROOT when not in the environmentDan Nicholson1-1/+3
Requiring an environment variable to be set in order to get any behavior is an obnoxious trait. Instead, a sane default TET_ROOT is built into the programs that use it. Users such as "make check" that need more control can continue using the environment variable. The scripts are now substituted from make so that we get full variable resolution.
2009-10-10xts5: Use xts-run wrapper script for executing testsDan Nicholson1-0/+1
xts-run is a simple wrapper script to generate a tetexec.cfg and run tcc with the appropriate arguments.
2009-10-07Purge XT_DISPLAY config variable, use DISPLAY environment var instead.Peter Hutterer1-13/+0
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>
2009-09-16Remove no-xcb requirement by copying libX11 source files.Peter Hutterer1-9/+31
This also requires the xtrans macros be used to define the transport methods.
2009-09-16xts5: Move tests out of tset directoryDan Nicholson1-20/+19
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.
2009-09-11Add tetexec_cfg, tet_scen and the scenarios to data files.Tinderbox user1-0/+1
2009-09-10Shutup make. AM_SILENT_RULES FTWPeter Hutterer1-0/+2
2009-06-24xts5: Add XI testsDan Nicholson1-0/+1
2009-06-24xts5: Add XI Protocol testsDan Nicholson1-0/+1
2009-06-24Only use automake subdir-objects option when neededDan Nicholson1-1/+1
Using the subdir-objects automake option slows done the build, so it should really only be used where needed in the tests.
2009-06-24Define common macros in config.h instead of on command lineDan Nicholson1-1/+7
Now that we have all the sources pulling in config.h, we can setup the common macros during configure instead of passing them on the command line.
2009-06-18xts5: Add tests for Xlib Chapter 17 - Application Utility FunctionsDan Nicholson1-0/+1
2009-06-18xts5: Add tests for Xlib Chapter 16 - Resource Manager FunctionsDan Nicholson1-0/+1
2009-06-17xts5: Add Xlib Chapter 15 - Inter-Client Communication Functions testsDan Nicholson1-0/+1
2009-06-17xts5: Add tests for Xlib Chapter 14 testsDan Nicholson1-0/+1
These tests work the functions in Xlib Chapter 14 tests- Locales and Internationalized Text Functions.
2009-06-17xts5: Add tests for Xlib Chapter 13 - Input Device FunctionsDan Nicholson1-0/+1
2009-06-17xts5: Add tests for Xlib Chapter 12 - Event Handling FunctionsDan Nicholson1-0/+1
2009-06-17xts5: Add tests for Xlib Chapter 11 - EventsDan Nicholson1-0/+1
2009-06-17xts5: Add Xlib Chapter 10 - Window and Session Manager Functions testsDan Nicholson1-0/+1
2009-06-15xts5: Add tests for Xlib Chapter 9 - Graphics FunctionsDan Nicholson1-0/+1
2009-06-14xts5: Add tests for Xlib Chapter 8 - Graphics Context FunctionsDan Nicholson1-0/+1
2009-06-14xts5: Add tests for Xlib Chapter 7 - Color Management FunctionsDan Nicholson1-0/+1
This requires linking to the libXR5 library to support the AVSCODE statements in some tests.
2009-06-14xts5: Add tests for Xlib Chapter 6 - Pixmap and Cursor FunctionsDan Nicholson1-0/+1
2009-06-14xts5: Add tests for Xlib Chapter 5 - Window Information FunctionsDan Nicholson1-0/+1
2009-06-14xts5: Add tests for Xlib Chapter 4 - Window FunctionsDan Nicholson1-0/+1
I'm not sure if this needs the -DGENERATE_PIXMAPS setup or not.
2009-06-08xts5: Enable Xlib3 testsDan Nicholson1-0/+1
These are tests for the macros and functions in Chapter 3 of the Xlib Programming Manual. The macro tests aren't quite working yet.
2009-05-27xts5: Enable the Xopen testsDan Nicholson1-0/+1
These are a bit different than the Xproto tests in that some of the test programs have separate source files. We also use a different set of libraries since we don't need libproto and this is what "tcc -b" would have done.
2009-05-27Compile objects in the same subdirectory as the sourcesDan Nicholson1-2/+2
For the tests, we want to just have top-level Makefiles and build the sources in their own subdirectory. Typically, automake would create the object files at the top-level, but this can cause conflicts when the source files have the same name. Use the subdir-objects automake option and enable the necessary AM_PROG_CC_C_O macro.
2009-05-19Error if Xlib does not have _XConnectDisplayDan Nicholson1-0/+9
Unfortunately, XTest uses _XConnectDisplay to connect to the server and this is only available in non-xcb Xlib. Hopefully this can be fixed someday.
2009-05-10xts5: Check for xset and xdpyinfo before running xts-configDan Nicholson1-7/+4
Ensure that the user has xset and xdpyinfo and that xts-config uses those tools. Additionally, move the generation of tetexec.cfg to the Makefile to handle all the environment variables and prerequisites.
2009-05-09Allow the display to test to be specified via configureDan Nicholson1-2/+15
Since we're now handling xts-config from configure, allow the user to specify the display to use instead always implicitly using $DISPLAY.
2009-05-09xts5: Make sure we have perl before running xts-configDan Nicholson1-2/+10
2009-05-09xts5: Generate tetexec.cfg from configureDan Nicholson1-1/+7
Move the tetexec.cfg template to a .in file so we can keep it pristine for the repo.
2009-05-09xts5: Use pkg-config to get X librariesDan Nicholson1-1/+4
We need to link the xts libraries and test applications with X libraries. This was being defined in common.mk as *SYSLIBS, but now the convention is to use the <var>_{CFLAGS,LIBS} used by PKG_CHECK_MODULES. A couple of the existing CFLAGS variables needed to be renamed to avoid conflicting with the pkg-config variables. This is all still pretty messy in common.mk, and should be cleaned up eventually.
2009-05-09xts5: Build and run tests using unique namesDan Nicholson1-0/+2
Automake is now used to build the tests instead of "tcc -b". We can control the build more accurately and provide more portability using the autotools instead of the massive convolution of tcc. Additionally, we're going to build the tests using unique names since automake will handle that better. There's no reason to always have the program named Test. Right now this only handles the Xproto allcclr test until things get smoothed out.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-08 03:45:07 +0000