| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
The project's scripts were never sourced before calling usage(),
causing project_action() to fail.
project_action_usage() should be used only when a project's
scripts have not yet been sourced otherwise its call to
project_include() would be redundant.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Removing the check function allows dependencies() to be executed,
printing the list of dependencies. It was not executed before due to
the way check functions are handled; check functions are executed
before functions with the same name (minus the "_check" suffix) in
order to determine whether calling the function is necessary.
|
| | |
| |
| |
| |
| | |
Whenever project_include() is called, it should be done within a
subshell in order to avoid clobbering function definitions.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The specified action will be taken on each of the dependencies
returned by project_dependencies() where $project is the first
argument to the meta-target, e.g.
./libreboot download libreboot-dependencies coreboot x200
The above command would download only the minimum projects necessary
for building all x200 image configurations.
To then build those dependencies:
./libreboot build libreboot-dependencies coreboot x200
And to get the final images:
./libreboot build coreboot x200
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Dependencies for any project can be determined by calling
project_dependencies() with a given project and (optional)
arguments. This is the function you will almost always want to call
when you're wanting to collect a list of dependencies. The output of
the topological sort is only one possible ordering of those
dependencies.
'dependencies' files may now contain any number of spaces or tabs
between each argument.
|
| |\ |
|
| |/
|
|
|
|
|
|
|
|
| |
Helper functions, such as "arguments", provided by one project should
be callable from another project for more flexibility. Metaprojects in
particular could use this functionality.
In order for this to work, project_include() is used to create the
necessary environment separation (so defined functions are not
clobbered by the helper function).
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
The updated regex catches more instances where '-pie' would be
enabled. Parabola's gcc is built with a spec string which causes
issues when building gmp (as part of the crossgcc build process)
using the old build system.
|
| | |
| |
| |
| |
| |
| |
| | |
The mirror for the version of libelf needed is down, preventing
crossgcc from being built using the old build system.
Resolves issues #664, #672
|
| |\ \
| |/
|/| |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
The driver is free software and contains no code to load any nonfree
firmware, so if it has been blacklisted it might not be because
of freedom issues, but probably because of reliability issues.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
| |\| |
|
| | | |
|
| | |
| |
| |
| | |
coreboot wiki is frozen now so it's a good idea to keep it up here
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| | |
verbose flashrom doesn't provide anything more when simply probing for
chips, insteads it spams user with info about what chips flashrom
supports
|
| |\| |
|
| | | |
|
| | | |
|
| |\ \ |
|
| |/ /
| |
| |
| | |
Minor Changes
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since we're doing a simple check to see if a function exists in a
given project's scripts we should only source those files into a
subshell (so any changes to the environment are discarded once the
subshell exits).
|
| |\ \ \
| |/ /
|/| /
| |/ |
|
| | |
| |
| |
| | |
It only hides actually useful output of flashrom
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
project_sources_patch() is the equivalent to git_patch() when working
with non-git sources. It should not be used with sources under a
version control system.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If a path is not supplied to project_sources_patch_recursive() or
git_project_patch_recursive() then it will attempt to apply the set of
patches located at $PROJECTS/$project/$PATCHES (the top-level patches
directory) twice. Checking to see if $path is of non-zero length
avoids this issue.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The method in which project sources are prepared from either extracted
non-git source archives or sources under $PROJECTS/$project/$SOURCES
are comparable to preparing git sources. This makes knowledge of the
source preparation process mostly transferable across the build
system regardless whether git is involved or not.
|
| |\ \ \
| |/ /
|/| /
| |/ |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
SSH access to a BBB has changed as of Debian 9, with the user needing to
login to the debian account instead of root. Furthermore, the addition
of the config-pin utility has simplified spidev setup considerably,
with the device tree overlay files no longer being needed. References to
the BBB screwdriver have also been removed, since it appears to no
longer be maintained.
|
| |\ \
| |/
|/| |
|
| | | |
|
| | | |
|
| |\ \ |
|
| |/ /
| |
| |
| | |
Minor Changes
|
| | | |
|
| |\ \ |
|
