summaryrefslogtreecommitdiffhomepage
path: root/MULTI
diff options
context:
space:
mode:
Diffstat (limited to 'MULTI')
-rw-r--r--MULTI19
1 files changed, 7 insertions, 12 deletions
diff --git a/MULTI b/MULTI
index 4e49f08..a50e30e 100644
--- a/MULTI
+++ b/MULTI
@@ -3,29 +3,24 @@ 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).
+code between the various parts.
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
+To compile the multi-binary, first "make clean" (if you've compiled
+previously), then
-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).
+make PROGRAMS="programs you want here" MULTI=1
To use the binary, symlink it from the desired executable:
ln -s dropbearmulti dropbear
+ln -s dropbearmulti dbclient
+etc
then execute as normal:
./dropbear <options here>
-"make install" doesn't currently work for multi-binary configuration, however
+"make install" doesn't currently work for multi-binary configuration, though
in most situations where it is being used, the target and build systems will
differ.