Mercurial > dropbear
comparison MULTI @ 389:5ff8218bcee9
propagate from branch 'au.asn.ucc.matt.ltm.dropbear' (head 2af95f00ebd5bb7a28b3817db1218442c935388e)
to branch 'au.asn.ucc.matt.dropbear' (head ecd779509ef23a8cdf64888904fc9b31d78aa933)
| author | Matt Johnston <matt@ucc.asn.au> |
|---|---|
| date | Thu, 11 Jan 2007 03:14:55 +0000 |
| parents | 9597c2e3b9d4 |
| children | 93e04b9ff676 |
comparison
equal
deleted
inserted
replaced
| 388:fb54020f78e1 | 389:5ff8218bcee9 |
|---|---|
| 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 various parts. | |
| 7 If you are familiar with "busybox", it's the same principle. | |
| 8 | |
| 9 To compile the multi-binary, first "make clean" (if you've compiled | |
| 10 previously), then | |
| 11 | |
| 12 make PROGRAMS="programs you want here" MULTI=1 | |
| 13 | |
| 14 To use the binary, symlink it from the desired executable: | |
| 15 | |
| 16 ln -s dropbearmulti dropbear | |
| 17 ln -s dropbearmulti dbclient | |
| 18 etc | |
| 19 | |
| 20 then execute as normal: | |
| 21 | |
| 22 ./dropbear <options here> | |
| 23 | |
| 24 "make install" doesn't currently work for multi-binary configuration, though | |
| 25 in most situations where it is being used, the target and build systems will | |
| 26 differ. |