From 2adfe1c0de350de6030e80d06adc9b546699e652 Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Sat, 3 Oct 1998 19:00:59 +0000 Subject: [PATCH] *** empty log message *** --- ChangeLog | 9 +++++++++ NEWS | 13 +++++++++---- guile-config/ChangeLog | 44 ++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 62 insertions(+), 4 deletions(-) create mode 100644 guile-config/ChangeLog diff --git a/ChangeLog b/ChangeLog index 817c46fe7..978bd8da7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,12 @@ +1998-10-03 Jim Blandy + + * guile-config: Renamed from `build'. + * Makefile.am (SUBDIRS): Mention `guile-config', not `build'. + * configure.in: Create `guile-config/Makefile.in', not + `build/Makefile.in'. Doc fix, too. + * qthreads.m4: Doc fix. + * Makefile.in, aclocal.m4, configure: Regeneranegerederadea. + 1998-10-03 * configure.in: Check for a missing `sleep' declaration. diff --git a/NEWS b/NEWS index 3a8d96dc0..bc552f114 100644 --- a/NEWS +++ b/NEWS @@ -53,9 +53,9 @@ mirror site; the canonical location is "ftp://prep.ai.mit.edu/pub/gnu". * Changes to the procedure for linking libguile with your programs -** You can now use the 'build-guile' utility to link against Guile. +** You can now use the `guile-config' utility to link against Guile. -Guile now includes a command-line utility called 'build-guile', which +Guile now includes a command-line utility called `guile-config', which writes to its standard output a list of flags which you must pass to the linker to link against the Guile library. The flags include '-lguile' itself, and any other libraries the Guile library depends @@ -65,13 +65,18 @@ For example, here is a Makefile rule that builds a program named 'foo' from the object files ${FOO_OBJECTS}, and links them against Guile: foo: ${FOO_OBJECTS} - ${CC} ${CFLAGS} ${FOO_OBJECTS} `build-guile link` -o foo + ${CC} ${CFLAGS} ${FOO_OBJECTS} `guile-config link` -o foo Previous Guile releases recommended that you use autoconf to detect which of a predefined set of libraries were present on your system. -It is more robust to use build-guile, since it records exactly which +It is more robust to use `guile-config', since it records exactly which libraries the installed Guile library requires. +This was originally called `build-guile', but was renamed to +`guile-config' before Guile 1.3 was released, to be consistent with +the analogous script for the GTK+ GUI toolkit, which is called +`gtk-config'. + * Changes to Scheme functions and syntax diff --git a/guile-config/ChangeLog b/guile-config/ChangeLog new file mode 100644 index 000000000..8cc61ac71 --- /dev/null +++ b/guile-config/ChangeLog @@ -0,0 +1,44 @@ +1998-10-03 Jim Blandy + + * Directory renamed to guile-config from build. + * guile-config.in: Renamed from build-guile.in, for consistency + with the analogous script for GTK, called gtk-config. + * Makefile.am, .cvsignore: References to `build-guile' replaced + with `guile-config'. + +1998-07-29 Jim Blandy + + * Makefile.in: Regenerated using the last public version of + automake, not the hacked Cygnus version. + +1998-07-28 Jim Blandy + + * Makefile.in: Regenerated, after removing Totoro kludge. + +1998-07-26 Jim Blandy + + * Makefile.in: Rebuilt, for config changes in parent dir. + +1998-01-05 Tim Pierce + + * .cvsignore: New file. + +Mon Oct 6 11:45:59 1997 Jim Blandy + + * build-guile.in: Try to return an appropriate exit status. + + * build-guile.in: Rearranged to use a table of subcommands, and + include per-subcommand help. + + * build-guile.in: New "info" subcommand, for easy access to Guile + build variables. + +Mon Sep 29 23:53:14 1997 Jim Blandy + + * Makefile.in: Regenerated with automake 1.2c. + +Sat Sep 27 23:15:26 1997 Jim Blandy + + * New directory --- the build-guile command, intended to help + people build Guile-based applications. + * Makefile.am, Makefile.in, build-guile.in: New files.