diff options
author | Matt Johnston <matt@ucc.asn.au> | 2004-06-01 02:46:09 +0000 |
---|---|---|
committer | Matt Johnston <matt@ucc.asn.au> | 2004-06-01 02:46:09 +0000 |
commit | 674a60748884dc55ee7091b7c23a41240e75f73c (patch) | |
tree | 3b5a173c356f867b94df3873b57ff36d33129ea7 /MULTI |
Makefile.in contains updated files required
--HG--
extra : convert_revision : cc8a8c49dc70e632c352853a39801089b08149be
Diffstat (limited to 'MULTI')
-rw-r--r-- | MULTI | 31 |
1 files changed, 31 insertions, 0 deletions
@@ -0,0 +1,31 @@ +Multi-binary compilation +======================== + +To compile for systems without much space (floppy distributions etc), you +can create a single binary. This will save disk space by avoiding repeated +code between the three components (dropbear, dropbearkey, dropbearconvert). +If you are familiar with "busybox", it's the same principle. + +To use the multi-purpose binary, firstly enable the "#define DROPBEAR_MULTI" +line in options.h + +Then enable which of the binaries you want to compile, also in options.h +(by default these are all enabled). + +You should then "make clean" (if you compiled previously), then + +"make dropbearmulti" + +("make dropbearmultistatic" will make a static binary). + +To use the binary, symlink it from the desired executable: + +ln -s dropbearmulti dropbear + +then execute as normal: + +./dropbear <options here> + +"make install" doesn't currently work for multi-binary configuration, however +in most situations where it is being used, the target and build systems will +differ. |