| Age | Commit message (Collapse) | Author |
|---|
|
The image rootfs size is determined by the following algorithm
(from Yocto ref manual):
if (image-du * overhead) < rootfs-size:
internal-rootfs-size = rootfs-size + xspace
else:
internal-rootfs-size = (image-du * overhead) + xspace
Currently rootfs-size is set to 8 MB which essentially means that it
will never be used as it is considered as a minimum. By removing it
from the image, the weak default value (65536) will be used which is
defined in bitbake.conf.
The primary reason of removing it is to be able to set a custom value in
e.g local.conf which is currently not possible.
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
|
|
Various component don't compile well with the added so called "hardening
flags".
The FORTIFY_SOURCE feature requires optimization to be enabled (-O1 or
-O2 depending...) It seems it would be better to force optimization on,
than to disable the "hardening flags" for these, but disabling them
seems standard practice. (You are no worse off than before "hardening
flags" were added. And all other components benefit). See
c5db7bafd3c837e, but also note that poky distro includes disabling these
for many components already.
There is a remaining unused-variable warning=error, which can be
squelched for the moment. Later on, it ought to be restored.
I would think setting the right compiler flags should eventually be done
in the standard poky recipe (or possibly even, component upstream).
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
A patch was applied previously to make dbus 1.10 compile correctly in
the presence of the readdir_r call (and only for qemux86, 32-bit).
The update to poky/sumo now builds dbus 1.12 Between 1.10 and 1.12 the
code has moved and more importantly the readdir_r seems to have been
changed back to readdir, so the patch cannot apply. Let's try removing
the patch.
The single patch however mixed different things. Testing shows that
the signed/unsigned mismatch is still a problem (warning which is
treated as an error) but only on 32-bit compilation. This part of the
patch is therefore kept for now. I have not deeply analyzed the effect
of this cast, just keeping what was already there.
[BASE-63] master fails application of dbus patch for qemux86 target
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
vsomeip contains some RPATH's to the build directores on the build host
that are bad. Previously we handled it by removing them from the CMake
link.txt files but they are no longer used since CMake is now using
ninja as the underlying build system in yocto.
First off, remove all the make related code, swap over to ninja, then
run chrpath -d on all binaries in the -test package.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Some of the test scripts we install depends on bash, and recent
changes in yocto are failing the build since it's now able to detect
script dependencies as well. Add bash dependency.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Some of the test scripts we install depends on python3, and recent
changes in yocto are failing the build since it's now able to detect
script dependencies as well. Add python3-core dependency.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Add patch for compilation with boost 1.66. The current version of
vsomeip does not support boost 1.66 which is part of the yocto sumo
release. This patch fixes vsomeip with regards to this until vsomeip 3.0
is released.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Node startup controller depends on glib-2.0-native for gdbus-codegen
binary. Add dependency so it's available.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
The patch capi-dbus-add-support-for-custom-marshalling from the
capicxx-dbus-runtime has been bumped to work with newer versions of
dbus used in sumo release of yocto.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
This is causing build problems and negligibly faster builds. Removing it
to reduce maintenance of the package.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
The patch has been upstreamed from what I was able to conclude.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
This removes new warnings in sumo and are used to tell which yocto
project releases the current version of the layer is compatible with.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
The CI system will typically make shallow clones, and it might be set to
fetch a specific layer branch. In a transition period, when the README
specifies a new branch we might lack the requested commit hash, but
since the README lists the branch name, we can use it and make sure it
is fetched first.
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
Signed-off-by: Oleksandr Kravchuk <oleksandr.kravchuk@pelagicore.com>
|
|
Signed-off-by: Oleksandr Kravchuk <oleksandr.kravchuk@pelagicore.com>
|
|
Simply because there is nothing to put in it beside systemd
defaults and this might as well reside in the main
distribution file as it is quite thin now.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
There is only one provider for this package.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
libjpeg was removed between jethro and krogoth Yocto releases. Since
then there has not been multiple providers for jpeg and libjpeg-turbo is
the default since then.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
There is not a virtual target called arm-oe-linux-gnueabi-depmod and
nothing provides kmod-cross.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
The supported machines (qemux86, qemux86-64, qemuarm64 and vexpressa9)
already set XSERVER in respective machine configuration file.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
These overrides where part of an legacy BSP which is no longer used and
we do do not have a need to carry a PREFERRED_VERSION that simply points
the current version that is in oe-core.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
The poky-ivi-systemd.conf file is a copy of an outdated poky.conf.
Converted to actually include the poky.conf and instead override
desired values to create a custom distribution. This way we can follow
poky updates without much effort.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
|
|
Update to the current meta-gplv2 rocko branch head commit.
This fixes a coreutils build warning with meta-ivi. See commit message
for c47d8ec for details.
Short log:
f875c60 diffutils Make it build with compile time hardening enabled
125e5ff rsync: Make it build with compile time hardening enabled
de94e04 patch: Make it build with compile time hardening enabled
1bf9ef7 rxvt-unicode: Inherit pkgconfig
acfb500 rxvt-unicode: Make it build with C++11
3e40e7d README: Add Peter Kjellerstedt as co-maintainer
392b499 texinfo: Update a patch to avoid fuzz
fc99e81 gnupg: Update a patch to avoid fuzz
5fe7a92 dosfstools: Update a patch to avoid fuzz
3ed1fb3 sed: Update a patch to avoid fuzz
c47d8ec coreutils: Update a patch to avoid fuzz
c0a5943 coreutils: Avoid warnings due to update-alternatives for man pages
9809f69 bash: Provide /bin/{sh, bash} when usrmerge is used
Signed-off-by: Stephen Lawrence <stephen.lawrence@renesas.com>
|
|
Reorder the branch policy statements in (I think) a more logical order
- first principles (cherry-pick), then versioning, etc. Minor word
changes to make the text shorter and clearer. Add note about Yocto/Poky
upgrades, as introduction to the next point which talks about
-rocko/-sumo branch names. Remove vexpressa9 from list of tested
platforms. Add a note on how other hardware is supported.
In other sections, minor word changes and whitespace.
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
The release policy of the GENIVI Baseline will be changed and we want to
continue doing bi-annual releases in meta-ivi. These changes should
reflect that and further explain how our releases and branches relates
to the GENIVI Baseline.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Tolkien no longer maintains the meta-ivi layer, it has been moved to my
table. I've missed updating this file earlier.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
There is a git diff performed and stored in a text file. This is to
note in build results if there were any local conf changes. It was
wrong (based on GDP directory structure) and also syntactically wrong,
which caused the command to fail, and through the -e flag consequently a
script error exit as well.
The script also needs to exit with success if reaching the end (cleanup
function might report some other return code)
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
This is a really old dependency append it's causing issues in builds
relying on the meta-ivi layer. Removing it as it doesn't seem necessary.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
The script used to place build inside of meta-ivi, (a remnant
from GDP where the script is in a "parent" container project).
The right location ought to be the directory just above meta-ivi
layer directory.
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
There are some "fixed" locations for caching (downloads, sstate) used for
all builds by build agents. These used to be used by default, and could
be overridden to not be used. The logic is now reveresed to be better
optimized for end-user usage, and less optimized for CI.
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
|
|
Script used >& syntax but did not specify a shell that is guaranteed
to understand it (csh, bash, zsh). This triggers the message
"Syntax error: Bad fd number" on some build machines.
An alternative would be to use /bin/bash explicitly since ci-build
requires bash anyway, but maybe checkout might be used on its own.
This is just as easy.
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
Included new image target for build with sdk, similar to GDP
setup. The content of that file likely needs some adjustments.
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
This is a copy of ci-build.sh from genivi-dev-platform which is
*not yet adjusted* for meta-ivi build. This is to facilitate diffing
against the next commit to see what was changed.
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
|
|
The PREFERRED_VERSION of wayland-ivi-extension is not necessary as we only provide
one version of this anyways.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
These gcc flags are quite standard practice but not always applied by
each and every component default settings - hence each Linux distro does
it in their own packaging.
It was requested by Phong Tran in PR #98 for GDP. These flags are
applied to the whole distro however, which is why they are placed in
meta-ivi distro definition instead.
[GDP-754] Compiler Hardening Flags
Signed-off-by: Gunnar Andersson <gandersson@genivi.org>
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Get rid of disturbing changes that are not changes
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
dlt-daemon was bumped recently and needs to be upgraded in meta-ivi
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
All three layers have been bumped for testing and getting the latest updates.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Documentation for using meta-ivi-test was previously held in the public wiki.
Move the documentation into the meta-ivi-test layer to keep it version
controlled together with the main code that it describes.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
The PACKAGECONFIG to compile the bluez5-noinst-tools has changed with the
latest bump of poky. This commit fixes the configuration.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Adds various compilation and runtime fixes.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
The script uses syntaxes that are not POSIX sh compatible, but rather bash.
For this reason, the script is now using bash instead of sh.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
Our cross compilers lack the sanitizers options for our targets. This
patch disables the compiler options which causes compilation errors. In
the long run we should probably try and get the cross compiler compiled
with sanitizers enabled.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
|
The meta-poky layer was renamed to meta-yocto in rocko release.
Signed-off-by: Oscar Andreasson <oscar.andreasson@pelagicore.com>
|
Mirza Krak
Gunnar Andersson
Oscar Andreasson
Oleksandr Kravchuk
Mirza Krak
Stephen Lawrence