| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These are necessary so that the build action for depthcharge can
locate the correct configuration for veyron targets in the
depthcharge source repository.
Prior, the build action was looking for 'veyron' instead of
'veyron_minnie' or 'veyron_speedy', causing it to fail.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In order to avoid additional, fragile, complexity for building
depthcharge, libpayload must be built for the minnie/speedy veyron
subtargets; this is the simplest way to avoid making special cases in
either the depthcharge scripts or the libpayload scripts with respect
to ensuring the depthcharge build action can locate the proper
libpayload build directory.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
'config' was renamed to 'config_name' to better convey its purpose.
Additionally, 'config_path' had its associated string value modified
to contain the correct path to the libpayload configuration file.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Helps keep complexity down as well as making scripts easier to
maintain if each project only builds itself.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It seems like 'project_action_arguments' was the intended function to
use, as 'project_action' does not actually /carry out/ the action
given as its first argument.
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Makes things easier to maintain if a project only builds itself--less
moving parts, etc.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The prefix action is a quality-of-life addition which helps a user
locate the relevant compiler binaries for a given target once built.
This change simply extends it for the i386 target.
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's possible that a compilation failure will occur if there's a
difference in major versions between the host GCC compiler and the one
being built. To avoid this, bootstrapping can be used. The method
for bootstrapping is simply passing the '-b' flag to Make; the
Makefile takes care of the rest.
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'project_action' was used instead of the intended
'project_action_arguments' function, I presume, as project_action does
not actually carry out the argument action--contrary to what the name
may seem to imply.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Helps keeps things more modular if each project only builds itself
rather than, for example, Coreboot's build action also building
crossgcc and an embedded controller firmware; this makes it possible
to rebuild only one project if its compilation fails.
|
|\ \ \ |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a continuation of the last set of commits removing braces from
parameter expressions which do not require them. The main script was
overlooked when applying the previous changes, which this commit aims
to correct.
Also, one parameter expansion in libs/common was corrected as it was
overlooked as well.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* projects/seabios/seabios
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* projects/memtest86plus/memtest86plus
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* projects/grub/grub
* projects/grub/grub-helper
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* projects/fontconfig/fontconfig
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* projects/dejavu-fonts/dejavu-fonts
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* projects/bucts/bucts
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* tools/dependencies/dependencies
* tools/dependencies/dependencies-helper
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* libs/tool
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* libs/project
ditto
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* libs/git
ditto
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
* libs/common
Makes it easier to read as well as cutting down on performance hits
caused by the use of braces in parameter expansions.
|
| | |
| | |
| | |
| | | |
PR not needed for this. Just a simple fix
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
Necessary to satiate shellcheck.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
It makes things easier if the makefiles fetch the default payload from
its build directory, which should have a stable name.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
There is a separate vboot project, so those revision files related to
it should be placed in its configs directory instead.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The new build system simply uses 'revision' to refer to the git
revision that should be used.
|
| | | |
| | | |
| | | |
| | | | |
The new build system uses the shortened version: arch
|
| | | | |
|
|/ / / |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Dumps CBMEM console log to stdout; this is useful for
development/troubleshooting purposes.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
As of right now setting/unsetting the variable does nothing as this
functionality will be added later.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The grub.cfg to be included in the GRUB image is located in each
target's directory in 'projecs/grub/configs' now, which means
'projects/grub/configs/grub.cfg' no longer has any use.
Ditto with 'projects/grub/configs/modules-install' and
'projects/grub/configs/modules-preload'
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The bootorder file should be handled by the Coreboot scripts in
projects/coreboot/coreboot* instead for better tailoring to a given
target.
|