about summary refs log tree commit diff
path: root/INSTALL
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2015-01-02 12:00:29 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2015-01-02 12:00:29 +0000
commit91035b6582847f551bddae5446def2bda697c75b (patch)
treeee3ee13641b9c701361fa8e1642717765a3501fe /INSTALL
parent151f30888748cc37b82c1c21c4428c53279bf8eb (diff)
downloadexecline-91035b6582847f551bddae5446def2bda697c75b.tar.gz
execline-91035b6582847f551bddae5446def2bda697c75b.tar.xz
execline-91035b6582847f551bddae5446def2bda697c75b.zip
Better documentation for --enable-slashpackage
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL18
1 files changed, 16 insertions, 2 deletions
diff --git a/INSTALL b/INSTALL
index d2c6cac..a3d2a5a 100644
--- a/INSTALL
+++ b/INSTALL
@@ -112,8 +112,22 @@ absolute pathnames. skarnet.org packages support it: use the
 --enable-slashpackage=DIR for a prefixed DIR/package tree.
 This option will activate slashpackage support during the build
 and set slashpackage-compatible installation directories.
-Other options setting individual installation directories will be
-ignored.
+If $package_home is the home of the package, defined as
+DIR/package/$category/$package-$version with the variables
+read from the package/info file, then:
+
+  --dynlibdir is $package_home/library.so
+  --bindir is $package_home/command
+  --sbindir is also $package_home/command (slashpackage differentiates
+root-only binaries by their Unix rights, not their location in the
+filesystem)
+  --libexecdir is also $package_home/command (slashpackage does not
+need a specific directory for internal binaries)
+  --libdir is $package_home/library
+  --includedir is $package_home/include
+
+ --prefix is pretty much ignored when you use --enable-slashpackage.
+You should probably not use both --enable-slashpackage and --prefix.
 
  When using slashpackage, two additional Makefile targets are
 available after "make install":