delta/glib.git/tests/Makefile.am, branch require-python34 gitlab.gnome.org: GNOME/glib.git tests: Port gen-casefold-txt.pl and gen-casemap-txt.pl to Python 3. See #1332 2018-06-12T20:18:03+00:00 Christoph Reiter creiter@src.gnome.org 2018-05-29T09:31:49+00:00 a580185cdca0de76cf71bd6b3c01230d281f5a05 I've tried to keep the code structure roughly the same. 
I've tried to keep the code structure roughly the same.
build: Drop nmake/MSC build system for GLib 2017-07-10T10:22:40+00:00 Philip Withnall withnall@endlessm.com 2017-07-03T10:30:08+00:00 a13113491855bf2803374bcfece824df0891c82a It hasn’t been seriously maintained for the best part of 10 years and is very outdated. The recommended way to build GLib on Windows is now Visual Studio: https://wiki.gnome.org/Projects/GTK%2B/Win32/MSVCCompilationOfGTKStack#GLib Signed-off-by: Philip Withnall <withnall@endlessm.com> https://bugzilla.gnome.org/show_bug.cgi?id=722047 
It hasn’t been seriously maintained for the best part of 10 years and is
very outdated. The recommended way to build GLib on Windows is now
Visual Studio:

https://wiki.gnome.org/Projects/GTK%2B/Win32/MSVCCompilationOfGTKStack#GLib

Signed-off-by: Philip Withnall <withnall@endlessm.com>

https://bugzilla.gnome.org/show_bug.cgi?id=722047
build: Use AM_TESTS_ENVIRONMENT rather than TESTS_ENVIRONMENT 2017-05-23T12:29:40+00:00 Philip Withnall withnall@endlessm.com 2017-05-23T12:28:19+00:00 a05b64a0cb234fffad12af0ca052296a1bae4a85 TESTS_ENVIRONMENT is reserved for the user to be able to set when running the tests. AM_TESTS_ENVIRONMENT is for the tests’ Makefile to set itself. https://www.gnu.org/software/automake/manual/html_node/Scripts_002dbased-Testsuites.html Signed-off-by: Philip Withnall <withnall@endlessm.com> https://bugzilla.gnome.org/show_bug.cgi?id=782996 
TESTS_ENVIRONMENT is reserved for the user to be able to set when
running the tests. AM_TESTS_ENVIRONMENT is for the tests’ Makefile to
set itself.

https://www.gnu.org/software/automake/manual/html_node/Scripts_002dbased-Testsuites.html

Signed-off-by: Philip Withnall <withnall@endlessm.com>

https://bugzilla.gnome.org/show_bug.cgi?id=782996
build: Give internal libraries higher precedence 2013-11-19T13:11:35+00:00 Michael Haubenwallner michael.haubenwallner@salomon.at 2013-11-14T15:22:10+00:00 b1af471a3f08c3afa4eb61f0791998aac5da80a8 Linking local libraries too late may cause preinstalled libraries to get found earlier, due to external library paths in .la files. https://bugzilla.gnome.org/show_bug.cgi?id=712314 
Linking local libraries too late may cause preinstalled libraries to
get found earlier, due to external library paths in .la files.

https://bugzilla.gnome.org/show_bug.cgi?id=712314
Rework the build system for a new tests approach 2013-06-01T03:12:15+00:00 Ryan Lortie desrt@desrt.ca 2013-05-30T04:07:32+00:00 f9eb9eed10b7123ef000e49be1290755b2d6ae8f Perform a substantial cleanup of the build system with respect to building and installing testcases. First, Makefile.decl has been renamed glib.mk and substantially expanded. We intend to add more stuff here in the future, like canned rules for mkenums, marshallers, resources, etc. By default, tests are no longer compiled as part of 'make'. They will be built when 'make check' is run. The old behaviour can be obtained with --enable-always-build-tests. --disable-modular-tests is gone (because tests are no longer built by default). There is no longer any way to cause 'make check' to be a no-op, but that's not very useful anyway. A new glibtests.m4 file is introduced. Along with glib.mk, this provides for consistent handling of --enable-installed-tests and --enable-always-build-tests (mentioned above). Port our various test-installing Makefiles to the new framework. This patch substantially improves the situation in the toplevel tests/ directory. Things are now somewhat under control there. There were some tests being built that weren't even being run and we run those now. The long-running GObject performance tests in this directory have been removed from 'make check' because they take too long. As an experiment, 'make check' now runs the testcases on win32 builds, by default. We can't run them under gtester (since it uses a pipe to communicate with the subprocess) so just toss them in TESTS. Most of them are passing on win32. Things are not quite done here, but this patch is already a substantial improvement. More to come. 
Perform a substantial cleanup of the build system with respect to
building and installing testcases.

First, Makefile.decl has been renamed glib.mk and substantially
expanded.  We intend to add more stuff here in the future, like canned
rules for mkenums, marshallers, resources, etc.

By default, tests are no longer compiled as part of 'make'.  They will
be built when 'make check' is run.  The old behaviour can be obtained
with --enable-always-build-tests.

--disable-modular-tests is gone (because tests are no longer built by
default).  There is no longer any way to cause 'make check' to be a
no-op, but that's not very useful anyway.

A new glibtests.m4 file is introduced.  Along with glib.mk, this
provides for consistent handling of --enable-installed-tests and
--enable-always-build-tests (mentioned above).

Port our various test-installing Makefiles to the new framework.

This patch substantially improves the situation in the toplevel tests/
directory.  Things are now somewhat under control there.  There were
some tests being built that weren't even being run and we run those now.
The long-running GObject performance tests in this directory have been
removed from 'make check' because they take too long.

As an experiment, 'make check' now runs the testcases on win32 builds,
by default.  We can't run them under gtester (since it uses a pipe to
communicate with the subprocess) so just toss them in TESTS.  Most of
them are passing on win32.

Things are not quite done here, but this patch is already a substantial
improvement.  More to come.
Move a pair of gobject tests to tests/gobject/ 2013-06-01T03:03:19+00:00 Ryan Lortie desrt@desrt.ca 2013-05-30T03:43:26+00:00 d7b3e558cfc91b1eaee80b156ad358774ded1c34 testgobject.c and timeloop-closure.c are the only two tests in the toplevel tests/ directory that depend on gobject, so move them to tests/gobject/ along with the other gobject tests. Both of these were in noinst_PROGRAMS and not TESTS, so keep them that way when we move them. 
testgobject.c and timeloop-closure.c are the only two tests in the
toplevel tests/ directory that depend on gobject, so move them to
tests/gobject/ along with the other gobject tests.

Both of these were in noinst_PROGRAMS and not TESTS, so keep them that
way when we move them.
More test fixes for builddir != srcdir 2013-05-28T02:05:19+00:00 Matthias Clasen mclasen@redhat.com 2013-05-28T02:05:19+00:00 4c9a7b65eb028f78ad4e68c177e4ee634124b694 






build: Fix usage of %.test again
2013-05-24T21:16:44+00:00

Colin Walters
walters@verbum.org

2013-05-24T21:16:44+00:00

0b167b0ae964fcd999ccf8a9fdc41804df936a28

We actually need the first dependency because it includes the
final executable name.  Rather, fix the original bug by using
the variable $(EXEEXT).





We actually need the first dependency because it includes the
final executable name.  Rather, fix the original bug by using
the variable $(EXEEXT).







tests: Drop unnecessary % from .test pattern match rule
2013-05-24T20:30:21+00:00

Colin Walters
walters@verbum.org

2013-05-24T19:42:12+00:00

5088c705ac5ce118502d0c6ea74aca1cec26b575

On Windows, the executables will have .exe, so this won't
match.  Furthermore, they aren't actually dependent on the
executable to build.





On Windows, the executables will have .exe, so this won't
match.  Furthermore, they aren't actually dependent on the
executable to build.







Convert more tests to installed tests
2013-05-21T03:41:49+00:00

Matthias Clasen
mclasen@redhat.com

2013-05-21T01:05:56+00:00

7ff5c082213c13c893f583f2bce77fa63a146af2

This makes the tests in tests installed, except for
the performance tests.





This makes the tests in tests installed, except for
the performance tests.