summaryrefslogtreecommitdiff
path: root/doc/ref/libguile-linking.texi
diff options
context:
space:
mode:
authorAndy Wingo <wingo@pobox.com>2011-10-12 13:07:30 +0200
committerAndy Wingo <wingo@pobox.com>2011-10-12 17:12:29 +0200
commitd32df1325dfe5f550cf1262dc7e90ba86b526a7c (patch)
treefc2ec0ec6b9bb115ff321b4c8f6c6823e2e71d2c /doc/ref/libguile-linking.texi
parentb09179d0eb0919920d4784b45af06c2f74b10c2d (diff)
downloadguile-d32df1325dfe5f550cf1262dc7e90ba86b526a7c.tar.gz
manual: reorganize autoconf, pkg-config info
* doc/ref/libguile-parallel.texi: New file, documenting parallel installation and the use of pkg-config. * doc/ref/libguile-linking.texi: Adapt. * doc/ref/libguile-autoconf.texi: Rename from autoconf.texi. Lower sections, and integrate in the "Programming in C" chapter. * doc/ref/guile.texi: Adapt.
Diffstat (limited to 'doc/ref/libguile-linking.texi')
-rw-r--r--doc/ref/libguile-linking.texi26
1 files changed, 9 insertions, 17 deletions
diff --git a/doc/ref/libguile-linking.texi b/doc/ref/libguile-linking.texi
index 3a90208be..de9076800 100644
--- a/doc/ref/libguile-linking.texi
+++ b/doc/ref/libguile-linking.texi
@@ -16,23 +16,15 @@ head of any C source file that uses identifiers described in this
manual. Once you've compiled your source files, you need to link them
against the Guile object code library, @code{libguile}.
-@code{<libguile.h>} is not in the default search path for headers,
-because Guile supports parallel installation of multiple versions of
-Guile, with each version's headers under their own directories. This is
-to allow development against, say, both Guile 2.0 and 2.2.
-
-To compile code that includes @code{<libguile.h>}, or links to
-@code{libguile}, you need to select the effective version you are
-interested in, and then ask @code{pkg-config} for the compilation flags
-or linking instructions. For effective version
-@value{EFFECTIVE-VERSION}, for example, you would invoke
-@code{pkg-config --cflags --libs guile-@value{EFFECTIVE-VERSION}} to get
-the compilation and linking flags necessary to link to version
-@value{EFFECTIVE-VERSION} of Guile. You would typically run
-@code{pkg-config} during the configuration phase of your program and
-use the obtained information in the Makefile.
-
-See the @code{pkg-config} man page, for more information.
+As noted in the previous section, @code{<libguile.h>} is not in the
+default search path for headers. The following command lines give
+respectively the C compilation and link flags needed to build programs
+using Guile @value{EFFECTIVE-VERSION}:
+
+@example
+pkg-config guile-@value{EFFECTIVE-VERSION} --cflags
+pkg-config guile-@value{EFFECTIVE-VERSION} --libs
+@end example
@menu
* Guile Initialization Functions:: What to call first.