Mercurial > dropbear
comparison MULTI @ 4:fe6bca95afa7
Makefile.in contains updated files required
author | Matt Johnston <matt@ucc.asn.au> |
---|---|
date | Tue, 01 Jun 2004 02:46:09 +0000 |
parents | |
children | 9597c2e3b9d4 |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 4:fe6bca95afa7 |
---|---|
1 Multi-binary compilation | |
2 ======================== | |
3 | |
4 To compile for systems without much space (floppy distributions etc), you | |
5 can create a single binary. This will save disk space by avoiding repeated | |
6 code between the three components (dropbear, dropbearkey, dropbearconvert). | |
7 If you are familiar with "busybox", it's the same principle. | |
8 | |
9 To use the multi-purpose binary, firstly enable the "#define DROPBEAR_MULTI" | |
10 line in options.h | |
11 | |
12 Then enable which of the binaries you want to compile, also in options.h | |
13 (by default these are all enabled). | |
14 | |
15 You should then "make clean" (if you compiled previously), then | |
16 | |
17 "make dropbearmulti" | |
18 | |
19 ("make dropbearmultistatic" will make a static binary). | |
20 | |
21 To use the binary, symlink it from the desired executable: | |
22 | |
23 ln -s dropbearmulti dropbear | |
24 | |
25 then execute as normal: | |
26 | |
27 ./dropbear <options here> | |
28 | |
29 "make install" doesn't currently work for multi-binary configuration, however | |
30 in most situations where it is being used, the target and build systems will | |
31 differ. |