summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authormidipix <writeonce@midipix.org>2018-03-06 12:56:21 -0500
committermidipix <writeonce@midipix.org>2018-03-06 12:56:21 -0500
commite62ede6683574d4ad1256eda175fd93f55d30839 (patch)
tree584c7815316291fc10b9ead67d99872a60c57844
parent9160500b62fca721ace9df94d440d9e71d587a35 (diff)
downloadslibtool-e62ede6683574d4ad1256eda175fd93f55d30839.tar.bz2
slibtool-e62ede6683574d4ad1256eda175fd93f55d30839.tar.xz
README: clarify difference between variants (slibtool[-shared|-static]).
-rw-r--r--README4
1 files changed, 3 insertions, 1 deletions
diff --git a/README b/README
index 4834742..1199be3 100644
--- a/README
+++ b/README
@@ -68,7 +68,9 @@ script; two examples of such packages are `binutils` and `gdb`, which both
have shared library builds disabled by default. A quick way to determine
whether this invocation form is appropriate with a specific package is to
run `./libtool --features` from the build directory, then check whether the
-output has either shared or static library builds disabled.
+output has either shared or static library builds disabled. When slibtool
+is invoked as a basic tool (i.e. slibtool, dlibtool, etc.), then building
+of both a shared library and a static archive is enabled by default.
## Differences from GNU libtool