BuildingDinner » History » Version 3
Matthieu Herrb, 2018-08-01 13:35
| 1 | 1 | Matthieu Herrb | h1. BuildingDinner |
|---|---|---|---|
| 2 | |||
| 3 | The Dinner project is interesting from the build and packaging point of view. |
||
| 4 | |||
| 5 | * *dinnerd* is a simple standalone application, which has no dependencies (beyond libc and running on a Unix like system) |
||
| 6 | 2 | Matthieu Herrb | * *libdinner* is a simple library, with no dependencies. |
| 7 | 1 | Matthieu Herrb | * *hungryhacker* is a standalone application that depends on libdinner. So one can experiment with separate build and runtime depencies. |
| 8 | There is also a sample shell script in the sources, that can be installed as part of the package. |
||
| 9 | * *vdinner* is a standalone application that also has external dependencies (GLUT). |
||
| 10 | 2 | Matthieu Herrb | |
| 11 | h2. Project repositories |
||
| 12 | |||
| 13 | The project is split in 4 different git repositories. This also allows to setup an exercise on using git submodules to manage the whole project. |
||
| 14 | |||
| 15 | h2. Build tools |
||
| 16 | |||
| 17 | Depending on the choice of the build tools, one need to add a mechanisme to be able to find libdinner as a build-time and run-time dependency for hungryhacker and vdinner. |
||
| 18 | |||
| 19 | 3 | Matthieu Herrb | h2. Packaging tools |
| 20 | 2 | Matthieu Herrb | |
| 21 | The project can also be used to show challenges in builing binary packages for various systems. libdinner packages can be split into runtime and development sub-packages. |