From d8b34aeff227ec8439cdf5d25db81252415fc113 Mon Sep 17 00:00:00 2001 From: Timothy Gu Date: Wed, 27 Nov 2013 14:40:31 -0800 Subject: [PATCH] Whitespace Signed-off-by: Timothy Gu --- How-MXE-builds-its-package.md | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/How-MXE-builds-its-package.md b/How-MXE-builds-its-package.md index b4a700e..3ad72d2 100644 --- a/How-MXE-builds-its-package.md +++ b/How-MXE-builds-its-package.md @@ -3,21 +3,23 @@ MXE is a set of Makefiles that is used to mimic a mini Linux distribution. ## Building packages When a person runs `make`, MXE does the following things: -1. It checks whether the requirements are met. If successful, it `touch`es a file in `usr/installed` to - prevent MXE from chacking that every time you run `make`. -2. It parses `index.html` to get a list of available packages. -3. It `include`s all the Makefiles in `src/`. -4. It solves dependency of packages to find the deepest depended package. -5. It starts building the deepest dependended package. -6. It downloads the `$($(PKG)_FILE)` and checks it against `$($(PKG)_CHECKSUM)`. The activities are logged - in `log/$(PKG)-download`. -7. From this point on, all activities are logged in `log/$(PKG)`. -8. It extracts the tarball or zip file using the appropriate command. -9. It applies any patch that matches `src/$(PKG)-*.patch`. +1. It checks whether the requirements are met. If successful, it `touch`es a + file in `usr/installed` to prevent MXE from chacking that every time you run + `make`. +2. It parses `index.html` to get a list of available packages. +3. It `include`s all the Makefiles in `src/`. +4. It solves dependency of packages to find the deepest depended package. +5. It starts building the deepest dependended package. +6. It downloads the `$($(PKG)_FILE)` and checks it against `$($(PKG)_CHECKSUM)`. + The activities are logged in `log/$(PKG)-download`. +7. From this point on, all activities are logged in `log/$(PKG)`. +8. It extracts the tarball or zip file using the appropriate command. +9. It applies any patch that matches `src/$(PKG)-*.patch`. 10. It calls macro specified in the package Makefile. - 1. If `$(PKG)_BUILD_$(TARGET)` macro exists, then it will call that macro. - 2. If it doesn't, then it calls `$(PKG)_BUILD` macro to build the package. - 3. Sometimes, it will also build a test program to make sure that the library works. -11. It `touch`es an empty file in `usr/$(TARGET)/installed/` with the name of the package, signifying that - the package is built successfully. + 1. If `$(PKG)_BUILD_$(TARGET)` macro exists, then it will call that macro. + 2. If it doesn't, then it calls `$(PKG)_BUILD` macro to build the package. + 3. Sometimes, it will also build a test program to make sure that the library + works. +11. It `touch`es an empty file in `usr/$(TARGET)/installed/` with the name of + the package, signifying that the package is built successfully. 12. It continues to build the next package.