More standard cross-compilation support (only --host, no --enable-cross needed)

1 files changed, 25 insertions, 16 deletions

diff --git a/INSTALL b/INSTALL
index b6fe232..199b252 100644
--- a/INSTALL
+++ b/INSTALL
@@ -37,23 +37,30 @@ before the "make install" phase. It will shave a few bytes off them.
 
  Controlling a build process via environment variables is a big and
 dangerous hammer. You should try and pass flags to configure instead;
-nevertheless, the standard environment variables are recognized.
+nevertheless, a few standard environment variables are recognized.
 
- The value of the CROSS_COMPILE environment variable will prefix the
-building tools' names. The --enable-cross option is preferred, see
-"Cross-compilation" below.
- 
  If the CC environment variable is set, its value will override compiler
-detection by configure.
+detection by configure. The --host=HOST option will still add a HOST-
+prefix to the value of CC.
 
  The values of CFLAGS, CPPFLAGS and LDFLAGS will be appended to flags
 auto-detected by configure. To entirely override the flags set by
-configure, use make -e.
+configure instead, use make variables.
 
- The value of LDLIBS will be appended by make to command lines that link
-an executable, even without the -e option.
 
- The Makefile supports the DESTDIR convention for staging.
+* Make variables
+  --------------
+
+ You can invoke make with a few variables for more configuration.
+
+ CC, CFLAGS, CPPFLAGS, LDFLAGS, LDLIBS, AR, RANLIB, STRIP, INSTALL and
+CROSS_COMPILE can all be overridden on the make command line. This is
+an even bigger hammer than running ./configure with environment
+variables, so it is advised to only do this when it is the only way of
+obtaining the behaviour you want.
+
+ DESTDIR can be given on the "make install" command line in order to
+install to a staging directory.
 
 
 * Static binaries
@@ -76,13 +83,15 @@ to static linking, for instance musl: http://musl-libc.org/)
 cross-compilation in one place: skalibs. Once you have
 cross-compiled skalibs, the rest is easy.
 
- Use the --enable-cross=PREFIX option to configure, or simply
---enable-cross if your default toolchain is a cross-compiling
-toolchain. And make sure to use the correct version of skalibs
-for your target, and the correct sysdeps directory, making use
-of the --with-include, --with-lib, --with-dynlib and --with-sysdeps
+ * Use the --host=HOST option to configure, HOST being the triplet
+for your target.
+ * Make sure your cross-toolchain binaries (i.e. prefixed with HOST-)
+are accessible via your PATH environment variable.
+ * Make sure to use the correct version of skalibs for your target,
+and the correct sysdeps directory, making use of the
+--with-include, --with-lib, --with-dynlib and --with-sysdeps
 options as necessary.
- 
+
 
 * The slashpackage convention
   ---------------------------