# gc.a - builds basic library
# c++ - adds C++ interface to library
# cords - adds cords (heavyweight strings) to library
-# test - prints porting information, then builds basic version of gc.a,
-# and runs some tests of collector and cords. Does not add cords or
-# c++ interface to gc.a
+# check - prints porting information, then builds basic version of gc.a,
+# and runs some tests of collector and cords. Does not add cords or
+# c++ interface to gc.a
# cord/de - builds dumb editor based on cords.
ABI_FLAG=
setjmp_test: $(srcdir)/tools/setjmp_t.c $(srcdir)/include/gc.h $(UTILS)
$(CC) $(CFLAGS) -o setjmp_test $(srcdir)/tools/setjmp_t.c
-test: cord/cordtest gctest setjmp_test
+check: cord/cordtest gctest setjmp_test
./setjmp_test
./gctest
cord/cordtest
+# A synonym to "check" (for compatibility with older GC versions).
+test: check
+
add_gc_prefix: $(srcdir)/tools/add_gc_prefix.c $(srcdir)/include/gc_version.h
$(CC) -o add_gc_prefix $(srcdir)/tools/add_gc_prefix.c
INSTALLATION:
Under UN*X, Linux:
-Alternative 1 (the old way): type "make test" in this directory.
- Link against gc.a. With the most recent GC distributions
- you may have to type "make -f Makefile.direct test" or
- copy Makefile.direct to Makefile first.
+Alternative 1 (the old way): type "make -f Makefile.direct check".
+ Link against gc.a.
Alternative 2 (the new way): type
"./configure --prefix=<dir>; make; make check; make install".
you should run `pkg-config` once before running `./autogen.sh` (autoreconf).
Below we focus on the collector build using classic makefile.
-For the Makefile.direct-based process, typing `make test` instead of `make`
+For the Makefile.direct-based process, typing `make check` instead of `make`
will automatically build the collector and then run `setjmp_test` and `gctest`.
`Setjmp_test` will give you information about configuring the collector, which is
useful primarily if you have a machine that's not already supported. Gctest is