| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Removes an unnecessary subshell grouping and 'set' statement and
replaces it with a good ol' if/then/else construct. Also added a
message printed to stdout informing the user of the change from
extraction to downloading if source extraction fails.
|
|
|
|
|
|
|
| |
Located in libs/project, this array's elements are compared with actions
in PROJECTS_ACTIONS_GENERIC when libreboot_setup_project_actions() is
called. This makes it simpler to add/remove actions which
should/shouldn't have a corresponding check function in PROJECT_ACTIONS.
|
|
|
|
|
|
|
| |
Located in libs/tool, this array's elements are compared with actions
in TOOLS_ACTIONS_GENERIC when libreboot_setup_tool_actions() is
called. This makes it simpler to add/remove actions which
should/shouldn't have a corresponding check function in TOOL_ACTIONS.
|
| |
|
|
|
|
|
|
|
|
|
| |
The added function is a complement to
libreboot_setup_project_actions() which moves generation of the
TOOL_ACTIONS array out of libs/tool and into the main script for
greater malleability.
Notably, the proper elements are now included in the array.
|
|
|
|
|
|
|
| |
The added function is called after all files in libs/ have been
sourced and provides the correct action sequence for 'test'.
Importantly, this function avoids providing undefined 'usage_check'
and 'clean_check' actions.
|
|
|
|
|
|
| |
When PROJECT_ACTIONS changed from having a string to an array of
strings as its value that change was not reflected in the main
script. This commit addresses that issue.
|
|
|
|
|
|
|
|
| |
Local variables 'epoch_path' and 'rnd_seed_path' are moved from
libreboot_setup_variables() to
libreboot_setup_reproducible_builds_variables() in order to keep
things more-or-less lexical in the source code (local variables in
Bash are dynamic in scope).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Reproducibility-related variable assignments are moved to a separate
function in order to make libreboot_setup_variables() less busy.
|
|
|
|
|
|
|
| |
Arrays are just a better idea for storing multiple strings than relying
on word splitting. Consequently, several global variables in libs/*
were switched to arrays and any references to said variables modified
to expand to the arrays' elements.
|
|
|
|
|
|
|
| |
Replace brace expansions with extended globs in a couple of places where
brace expansions were erroneously used in place of actual pattern
matching. This avoids potential errors concerning nonexisting files
when patching sources.
|
| |
|
|
|
|
| |
i.e., source tarballs are (partially) supported
|
|
|
|
|
| |
This is mainly useful for being able to run these scripts on BSDs.
And for users who use a Bash not installed to /bin.
|
|
|
|
|
| |
This reverts part of pull request #217 which called the 'env'
binary for each printf invocation.
|
|
|
|
|
|
|
|
|
| |
All printf calls should now be properly formatted; prior, the
format specifier string was erroneously used for both the format
specifiers and the string to be printed. 'env' is now used to
locate the printf binary so as to avoid potentially using a shell
builtin. Lastly, all calls to 'echo' within the new build system
have been replaced with printf for consistency/portability purposes.
|
|
|
|
|
|
|
|
| |
All environment variables necessary for creating reproducible builds
should now be present. If libfaketime is not linked then the only
reproducibility-related variables SOURCE_DATE_EPOCH and RANDOM_SEED (gcc
flag -frandom-seed) will be used. -frandom-seed will be added in a
later commit.
|
| |
|
| |
|
|
|
|
|
|
|
| |
GNU Nano sucks. Vi is better. I'd tell the build system to use Vim, but that's
not guaranteed to be installed. Vi is installed on more systems by default,
compared to Nano, because Vi is the de facto standard text editor or unix and
unix-like systems.
|
|
|
|
| |
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|
This is the initial import of the Paper build system into Libreboot.
It was written as a flexible and painless replacement for the Libreboot
build system, allowing to support many different configurations.
It currently only supports the following CrOS devices:
* Chromebook 13 CB5-311 (nyan big)
* Chromebook 14 (nyan blaze)
* Chromebook 11 (HiSense) (veyron jerry)
* Chromebit CS10 (veyron mickey)
* Chromebook Flip C100PA (veyron minnie)
* Chromebook C201PA (veyron speedy)
The build system also supports building various tools and provides
various scripts to ease the installation on CrOS devices.
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|