Hi Richard,
Let me do a quick explanation on what I intended to do with this script.
1. I don't have much lava knowledge but at a quick glance this may be ok, apart
from one of the file names which I've commented on below.
[Ans]: Basically this jinja template is mapped to lava.py module where
Is there any installer that I could download along with the .hddimg (or .iso)
image to the RAM, invoke the installer, so we could have a bootable image
installed on a SSD?
History:
I can already create USB live image with dd and .hddimg. I could also dd the
.hddimg onto SSD and make it
On Fri, Jul 6, 2018 at 2:10 PM, Giordon Stark wrote:
> Hi,
>
> So the good news is that this is at least the source code itself appears to
> be written in a packaged-up-manner which makes some things easier to deal
> with. It seems that all of the plugins are here:
>
On Fri, Jul 6, 2018 at 1:22 PM, Tim Hammer wrote:
>
> Thanks for the responses to my first email. I was able to get a working
> initramfs in my kernel image that allowed me to do the initial evaluation of
> my solution.
What was the issue? What was the fix?
> Now I am working to get all of the
Hi,
So the good news is that this is at least the source code itself appears to
be written in a packaged-up-manner which makes some things easier to deal
with. It seems that all of the plugins are here:
On Fri, Jul 6, 2018 at 1:28 PM, Giordon Stark wrote:
> Hi,
>
> Been struggling to understand the differences here. This is what the
> directory looks like
>
> kratsg@dc:/local/d4/gstark/poky/build$ ls
> tmp/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/
> total 4.3M
>
Hi,
Been struggling to understand the differences here. This is what the
directory looks like
kratsg@dc:/local/d4/gstark/poky/build$ ls
tmp/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/
total 4.3M
drwxr-xr-x 2 kratsg atlas 4.0K Jun 28 16:13 .
drwxr-xr-x 5 kratsg atlas
On Tue, Jul 3, 2018 at 2:02 PM, Tim Hammer wrote:
>
> ...
> Any help would be greatly appreciated.
>
Thanks for the responses to my first email. I was able to get a working
initramfs in my kernel image that allowed me to do the initial evaluation
of my solution.
Now I am working to get all of
externalsrc.bbclass?
In my current project we have a simplified version in a ”component.bbclass”.
It relies on a variable COMPONENT_DIR defined in our local.conf.
A recipe located in ”recipe-//_$PV.bb” doing
inherit component
will find its source code in $COMPONENT_DIR/, making the recipe
On Fri, Jul 6, 2018 at 11:20 AM, Simon Chamlian
wrote:
> Hi,
>
> Is there a way to keep the source code of a package to be able to modify
> it and then compile?
>
> For example, with LTIB ( Linux Target Image Builder ), it was possible
> with a command to extract the source code from a package,
Hi Simon,
> Is there a way to keep the source code of a package to be able to
modify it and then compile?
Yes, there is. devtool greatly simplifies this type of workflow. Please
refer to
https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#using-devtool-in-your-sdk-workflow
for
Hi,
Is there a way to keep the source code of a package to be able to modify it
and then compile?
For example, with LTIB ( Linux Target Image Builder ), it was possible with
a command to extract the source code from a package, make modifications and
then re-compile?
Thanks,
S
--
So the native recipe-sysroot-native is used for stuff that is actually
ran during the build, like Python, or gcc. The target recipe-sysroot
is target libraries.
Note how it started by saying it found jpeglib.h in /usr/include, you
certainly don't want that so this auto-detection is really badly
Am Fr., 6. Juli 2018 um 15:13 Uhr schrieb Burton, Ross <
ross.bur...@intel.com>:
> Move your DEPENDS up, as the inherits are setting up DEPENDS with
> python3-native python3-setuptools-native, and you're overwriting it.
>
> Put the DEPENDS after PYI_PACKAGE but before inherit.
>
> Ross
>
One
On Fri, 2018-07-06 at 17:15 +0800, Aaron Chan wrote:
> This patch is introduced as a feature in 2.6 M2 to support the
> extension of autobuilder to LAVA (Linaro Automated Validation
> Architecture).
> run-jinja2-parser loads lava config module and generates LAVA job
> config in a YAML format
On 6 July 2018 at 14:06, Oliver Westermann wrote:
> Of course, thats the reason I'm here ;)
>
> SUMMARY = "Pillow (The friendly PIL fork)"
> HOMEPAGE = "http://python-pillow.org/;
> LICENSE = "EPLv1"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=c6379001ecb47e2a0420c40177fc1125"
>
> SRC_URI[md5sum] =
Of course, thats the reason I'm here ;)
SUMMARY = "Pillow (The friendly PIL fork)"
HOMEPAGE = "http://python-pillow.org/;
LICENSE = "EPLv1"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c6379001ecb47e2a0420c40177fc1125"
SRC_URI[md5sum] = "52d93a34f4180abcff04876f23eaa9b9"
PYPI_PACKAGE = "Pillow"
What. You've got inherit setuptools3 so it should be using our own
python3 and have setuptools present. This makes no sense. :/
Can you share the recipe you're building?
Ross
On 6 July 2018 at 13:56, Oliver Westermann wrote:
> Am Fr., 6. Juli 2018 um 14:38 Uhr schrieb Burton, Ross
> :
>>
>>
Am Fr., 6. Juli 2018 um 14:38 Uhr schrieb Burton, Ross <
ross.bur...@intel.com>:
> That's very odd. I'd suggest maybe something really weird happened,
> what happens if you bitbake -cclean python3-pillow ; bitbake
> python3-pillow?
>
It fails with another error *dudum*
ERROR:
So I tried this myself and it worked, which makes me thing your work
dir got messed up somehow. It's trying to build here but failing as
there are missing dependencies (no jpeg DEPENDS, for example).
Ross
On 6 July 2018 at 13:38, Burton, Ross wrote:
> On 6 July 2018 at 13:32, Oliver Westermann
On 6 July 2018 at 13:32, Oliver Westermann wrote:
> This does not seem to work as expected. With option 1) and 2) it fails in
> do_compile:
>
> | DEBUG: Executing shell function do_compile
> |
>
Am Do., 5. Juli 2018 um 12:59 Uhr schrieb Burton, Ross <
ross.bur...@intel.com>:
> On 5 July 2018 at 08:26, Oliver Westermann wrote:
> > I'm fiddeling around with yocto. I want to move some python stuff onto an
> > embedded board and use the nxp mx8 yocto. Everything worked as expected
> > until
From: Mohamad Noor Alim Hussin
yocto-kernel-cache
branch: yocto-4.14
commit d64aec9793d558ff49993ff6076be6d4daf101c2
Signed-off-by: Mohamad Noor Alim Hussin
---
meta/recipes-kernel/linux/linux-yocto_4.14.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch is introduced as a feature in 2.6 M2 to support the
extension of autobuilder to LAVA (Linaro Automated Validation Architecture).
run-jinja2-parser loads lava config module and generates LAVA job config
in a YAML format before its triggers LAVA server to execute a task.
Signed-off-by:
> There is no standard distro feature called "ram". Perhaps this is
> something specific to your BSP layer?
Yeah, I noticed that. There is " nfs" parameter, but looks somehow
peculiar: not in line with initramfs creation.
I know that the whole line: DISTRO_FEATURES_append = " ram" looks
On 07/06/2018 01:28 PM, Paul Eggleton wrote:
Hi Robert
On Wednesday, 4 July 2018 7:52:05 PM NZST you wrote:
I'm sorry to say that I met layerindex' loaddata problems yesterday and
today,
I still didn't find the root cause. Have you tried dumpdata and loaddata
recently, please ?
What I did
26 matches
Mail list logo
