| 1 | Building Syslinux |
|---|
| 2 | |
|---|
| 3 | From Syslinux 6.0 onwards there is support for three different |
|---|
| 4 | firmware backends, BIOS, 32-bit EFI and 64-bit EFI. To allow users the |
|---|
| 5 | flexibility to build only the firmware they need the Syslinux make |
|---|
| 6 | infrastructure has become more complex. |
|---|
| 7 | |
|---|
| 8 | The Syslinux make infrastructure understands the following syntax, |
|---|
| 9 | |
|---|
| 10 | make [firmware[,firwmware]] [target[,target]] |
|---|
| 11 | |
|---|
| 12 | If no firmware is specified then any targets will be applied to all |
|---|
| 13 | three firmware backends. If no target is specified then the 'all' |
|---|
| 14 | target is implicitly built. |
|---|
| 15 | |
|---|
| 16 | For example, to build the installers for BIOS, 32-bit EFI and 64-bit |
|---|
| 17 | EFI type, |
|---|
| 18 | |
|---|
| 19 | make installer |
|---|
| 20 | |
|---|
| 21 | TO build the BIOS and 64-bit EFI installers type, |
|---|
| 22 | |
|---|
| 23 | make bios efi64 installer |
|---|
| 24 | |
|---|
| 25 | To delete all object files and build the installer for 32-bit EFI |
|---|
| 26 | type, |
|---|
| 27 | |
|---|
| 28 | make efi32 spotless installer |
|---|
| 29 | |
|---|
| 30 | |
|---|
| 31 | ++++ THE OBJECT DIRECTORY ++++ |
|---|
| 32 | |
|---|
| 33 | A custom top-level object directory can be specified on the make |
|---|
| 34 | command-line by using the O= variable, e.g. |
|---|
| 35 | |
|---|
| 36 | make O=/tmp/syslinux-obj efi32 |
|---|
| 37 | |
|---|
| 38 | will build the 32-bit object files under /tmp/syslinux-obj/efi32. If |
|---|
| 39 | no object directory is specified then object files will be written to |
|---|
| 40 | an 'obj' directory in the top-level of the Syslinux source. |
|---|
