| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
This is the result of automated script (0.9.0) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
| |
|
|
| |
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HOSTTOOLS and HOSTTOOLS_NONFATAL are global variables that being
handled in base_eventhandler, so they must be defined in config files
or in INHERIT classes or classes being inherited by base.bbclass, or
else we might run into the following problems:
```
$ bitbake pkgname
$ bitbake imgname
```
the HOSTTOOLS and HOSTTOOLS_NONFATAL in the above image recipe, for
instance, 'repo python' in image_repo_manifest.bbclass, they would not
be copied to HOSTTOOLS_DIR.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In 25a17f0346ab05b3212bb280e4a8b622bcf99bce, poky sets
reproducible_build by defaults. However, it is quite complex as it tries
to compute a plausible timestamp from source files, in a reproducible
ways.
Setting the timestamps to 0, just like ostree, is probably safer in our
case, so let's switch to our old behavior.
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use reproducible builds by default. OSTree sets mtime to 0 at
commit time anyway. This makes sure that all mtime timestamps
are 0 already at build time. This is relevant for programs
which relies on mtime of deployed artifacts at runtime.
Python for instance writes the mtime of the source file into
bytecode files (pyc) at build time. When OSTree then clears
the mtime Python considers all bytecode files as stale.
Reproducible binaries also avoid unnecessary differences
between two OSTree commits. E.g. if the sstate cache is
cleared between two OSTree commits OpenEmbedded might create
slightly different binaries.
Note however that not all all recipe generate reproducible
binaries at this time.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
| |
|
|
|
|
|
|
|
| |
OSTree needs UsrMove to be implemented, meaning that everything
should be in /usr. OpenEmbedded has a distro feature usrmerge which
implements exactly that, and makes sure that no package install
anything in /bin, /sbin or /lib. Make use of it.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Pull the common lines from the poky-sota.conf and poky-sota-systemd.conf
example distributions into a separate include file that can be pulled into
other environments.
This might be by including it in a user's own custom distro, or by directly
including it in local.conf (e.g. AGL).
require conf/distro/sota.conf.inc
|
| |
|
|
|
|
| |
They are more flexible and allow tricks like conditionally inheriting
machine-related classes from the main one which makes things easier
for external users like AGL
|
| | |
|
| |\
| |
| | |
Merge changes required by AGL
|
| | | |
|
| |/
|
|
|
|
| |
Setting the default DISTRO to include systemd means that the rvi-sota-client
starts by default, making it work 'out of the box'. image-prelink seems to be
broken at the moment, so I've disabled it by default.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
