On Saturday, January 7, 2017 10:23:50 AM PST Mike Looijmans wrote:
> On 06-01-17 18:17, Rudolf J Streif wrote:
> > Hi Colin,
> >
> > The correct way of doing this is a package postinstallation script that is
> > run by the package manager after the package containing your application
> > is
colleague wants to know how one stays up to date with security
alerts related to YP releases, i checked out the yocto-security
mailing list:
https://lists.yoctoproject.org/pipermail/yocto-security/
but that looks like a very dead mailing list. are there other options?
rday
--
Please suggest me the solution for compiling
Openjdk 8 for arm adding support for any jit compiler like shark or jamvm
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Dear Yocto specialists
I have one question.
When building the kernel module and install to rootfs with Yocto, I got the
kernel module without debug information.
Investigating a little bit revealed that it seems do_package process remove the
debug information from binary,
as the file size
Hi, since it's roughly two weeks, I just wanted to bump this patch again (yes,
I know many people were on vacations).
But actually, I would already be glad to hear whether I sent the patch to the
right list.
Cheers,
Andreas
On Monday, December 26, 2016 2:41:49 PM CET Andreas Cord-Landwehr
On 06-01-17 18:17, Rudolf J Streif wrote:
Hi Colin,
The correct way of doing this is a package postinstallation script that is run
by the package manager after the package containing your application is
installed on the target system.
You add to your recipe:
pkg_postinst_${PN}() {
#!/bin/sh
