On 19 April 2013 15:39, Robert P. J. Day wrote:
>
> i think i'll just leave this to the rpi folks. :-)
>
I'm building for raspberrypi so I'll add this to my queue of things to look at.
--
Paul Barker
Email: p...@paulbarker.me.uk
htt
7; as aliases for localhost,
which I don't see the purpose of myself.
So I'd recommend dropping these from meta-raspberrypi completely. Just
my opinion though, anyone else got any thoughts on this?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
_
On 20 April 2013 21:35, Andrei Gherzan wrote:
> On Sat, Apr 20, 2013 at 4:05 PM, Paul Barker wrote:
>>
>> So I'd recommend dropping these from meta-raspberrypi completely. Just
>> my opinion though, anyone else got any thoughts on this?
>>
>
> Hello guy
Dropped raspberrypi modifications to hosts and interfaces files as they are
unnecessary.
Signed-off-by: Paul Barker
---
recipes-core/netbase/netbase-5.0/raspberrypi/hosts |2 --
recipes-core/netbase/netbase-5.0/raspberrypi/interfaces | 15 ---
recipes-core/netbase
he build?
Also what's the exact error message? I'm wondering if this is somehow
being ran in a shell that isn't bash. With an unknown command 'abcd',
bash gives me "abcd: command not found" and dash gives me "dash: 1:
abcd: not found".
Using eg
hed patch I get:
Patch format detection failed.
Are you using 'git send-email'?
However, I can apply this after fixing the attached patch file by
hand, giving it a test now.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
_
On 25 April 2013 13:51, Seth Bollinger wrote:
> On Thu, Apr 25, 2013 at 7:38 AM, Paul Barker wrote:
>>
>> '[[' should be a bash builtin. What host OS are you using for the build?
>
> I'm using debian. I'll check what the default shell is. You're
On 25 April 2013 13:57, Seth Bollinger wrote:
> On Thu, Apr 25, 2013 at 7:51 AM, Paul Barker wrote:
>>
>> Trying to apply this email I get:
>>
>> Applying: sdcard_image-rpi.bbclass: Copy startup files required
>> for 16MB GPU operation.
>> fatal
or re-writing rpi-first-run-wizard to use something
else. I can write a patch for the former, the latter isn't really my
area of expertise.
Thoughts?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing
On 27 April 2013 18:21, Khem Raj wrote:
>
> rm -rf tmp/
> configurations are kept outside. tmp/
You may also need to get rid of 'pseudodone' (as pseudo is kept under
'tmp' and will need rebuilding), 'cache' and 'sstate-cache'.
the rootfs to
fill the SD card it's on without prompts. Should be easy to do with a
postinst script and fdisk. Would be great if it worked as an option
that could go in IMAGE_FEATURES. It also might be applicable to other
devices such as the Beagleboard. I'll take a look when I get chanc
gt;
> AFAIK grep or awk is the only way.
I think this patch probably does make sense.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 1 May 2013 20:19, Andrei Gherzan wrote:
>
> Aa... I just can't make it work. My advice is to use git send-email too.
>
You can cherry-pick it from my repository at the moment
(https://bitbucket.org/betafive/meta-raspberrypi), but yes, git
send-email is the way forward.
ers, IP addresses, etc
> - this tools also sets up the bootloader (if required)
Sounds great though it may take a long time to copy files to an SD
card (I noticed a similar opinion at
http://www.raspbian.org/RaspbianInstaller). May be quicker to generate
an image file with the correct size
Package names shouldn't contain capital letters.
Signed-off-by: Paul Barker
---
.../python/RPi-GPIO/don-t-install-setuptools.patch | 16
recipes-devtools/python/RPi-GPIO_0.2.0.bb | 21 -
.../python/rpi-gpio/don-t-install-setuptools.patch
ms to depend on meta-oe and meta-networking,
both within the meta-openembedded group of layers.
Hope this helps,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
addresses but it's a start, such features could be added later.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Package names shouldn't contain capital letters.
Signed-off-by: Paul Barker
---
.../python/{RPi-GPIO => rpi-gpio}/don-t-install-setuptools.patch | 0
recipes-devtools/python/{RPi-GPIO_0.2.0.bb => rpi-gpio_0.2.0.bb} | 0
2 files changed, 0 insertions(+), 0 deletions
On 7 May 2013 12:45, Andrei Gherzan wrote:
> Could you please resend it with - M?
>
Done, still not entirely used to git format-patch and git send-email.
Will try putting it in my config as the default.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker
e to keep it we need to refactor it. And raspi-config would be my
> choice.
>
For my current builds I've removed this recipe completely. I think if
someone wants a script like this it makes more sense to start from
scratch or from raspi-config rather then from this script. I can send
a p
h
http://www.paulbarker.me.uk/yocto/20130510_poky-raspberrypi_userland/patches/meta-raspberrypi/0004-bootfiles-vc-graphics-use-archive-rather-than-git.patch
Though I'm currently just looking for comments on the general idea,
not ready to submit the patches for merging just yet.
--
Paul Barker
E
ilds. Copying in yocto@ and Andrei as
this is raspberrypi related.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
o generate a common SDK archive and then
archives of just the machine-specific bits. Has anyone else tried
producing SDKs for multiple target machines and if so do you have any
thoughts on this?
Thanks,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
__
bake` give any output?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
lf that throws the error then? Could
you try adding 'inherit externalsrc' to the top of your recipe, that
class is there to prevent do_fetch, do_unpack etc being called which
may be failing as there isn't a SRC_URI set.
--
Paul Barker
Email: p...@paulbarker.me.u
On 21 May 2013 11:35, Paul Barker wrote:
> On 21 May 2013 11:12, Zafrullah Syed wrote:
>> I sourced oe-init-build-env and ran bitbake helloworld from build directory.
>> Then i get this error. previously, i ran bitbake core-image-minimal and was
>> successful. No idea w
ex/recipes/?q=devmem
Does your bblayers.conf point to the relevant layers?
I'm just guessing here, I'd advise including the beginning of your
bitbake output in any error report as that tells us what layers and
versions your using, what the target and host platforms are,
Pi logo, on
qemuarm I see the Yocto Project logo.
Signed-off-by: Paul Barker
---
conf/machine/raspberrypi.conf | 3 +++
recipes-core/psplash/psplash_git.bbappend | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/conf/machine/raspberrypi.conf b/conf/machine
need to
fetch but it does make it easier to override the firmware source to a local
clone or an archive. If there's no need for vc-graphics any more and the
userland recipe satisfies everyone's use cases maybe this is redundant and
vc-graphics should just be removed?
Paul Barker (2):
The existing first run script is inappropriate for a board support layer. It is
also full of references to OpenPandora and is not portable across all distros
which may use meta-raspberrypi.
Signed-off-by: Paul Barker
---
recipes-extra/startup/rpi-first-run-wizard.bb | 37 ---
recipes
a prefix for S
in bcm2835-bootfiles.bb and vc-graphics.inc as different subdirectories are
referenced in each recipe.
Signed-off-by: Paul Barker
---
recipes-bcm/bootfiles/bcm2835-bootfiles.bb | 6 +-
recipes-bcm/common/firmware.inc| 3 +++
recipes-bcm/vc-graphics/vc-graphics.inc
On 8 May 2013 10:06, Paul Barker wrote:
> Package names shouldn't contain capital letters.
>
> Signed-off-by: Paul Barker
> ---
> .../python/{RPi-GPIO => rpi-gpio}/don-t-install-setuptools.patch | 0
> recipes-devtools/python/{RPi-GPIO_0.2.0.bb => rpi-gpi
les -f" to rebuild modules. It's the "-f" that
causes the task to be forced.
Is this any help? It doesn't solve exactly the question you asked but
might be what you need.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
r.html
> for important disclosures regarding this electronic communication.
> ===
>
May be worth noting that yocto@yoctoproject.org is a public mailing
list with a public archive.
--
Paul Barker
Ema
eral kernel versions and haven't found any issues (yet).
>
Just to point out - this is pretty common across linux distros as
well, otherwise all your software would have to be re-built every time
you updated the kernel.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbark
ay that sounds excellent. Will this contain a
known-working make as well for those with a broken make 3.82?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
se case for the pre-compiled vc-graphics recipes
within OpenEmbedded/Yocto.
Does anyone else who's worked with meta-raspberrypi agree with this?
If so I'll throw together patches to achieve this.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
On 8 July 2013 10:01, Tomas Frydrych wrote:
> On 06/07/13 12:22, Paul Barker wrote:
>>
>> Does anyone else who's worked with meta-raspberrypi agree with this?
>> If so I'll throw together patches to achieve this.
>
> vc-graphics is the original package be
h capital letters is that opkg rejects .ipk files with capital
letters. I didn't have any problems with it when producing .deb files.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yoc
stemd mount unit that handles it, so it must be some other
> part of the system.
>
Look in /etc/udev on the image, this is handled by udev.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
do one of the following:
a) Modify PV (or LINUX_VERSION) in the bbappend to reflect the correct version?
b) Bump the git commit hash used for beagleboard to 3.2.32?
I know 3.2 is old, but the APIs I'm using for my kernel driver were
ditched in the 3.3 kernel release and 3.2 has a p
On 13 July 2013 15:52, Bruce Ashfield wrote:
> On 13-07-13 10:27 AM, Paul Barker wrote:
>>
>> The commit hash 40bde7a43ef3cd85729ab02464a7ecdf71e522a6 is set in
>> .../poky/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> and checking the git log for
The KERNEL_VERSION set by linux-yocto_3.2.bb in openembedded-core is 3.2.32 but
the SRCREVs in the bbappend in meta-yocto-bsp referred to version 3.2.18. These
SRCREVs are updated to the correct values.
Signed-off-by: Paul Barker
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.2.bbappend
As very recently discussed with Bruce Ashfield.
This isn't intended for the master branch as linux-yocto_3.2 isn't present
there.
I'm going to build for Beagleboard this evening and give it a spin tomorrow on
my board but that's about the extent of the testing I can do.
Paul
On 13 July 2013 16:19, Paul Barker wrote:
> The KERNEL_VERSION set by linux-yocto_3.2.bb in openembedded-core is 3.2.32
> but
> the SRCREVs in the bbappend in meta-yocto-bsp referred to version 3.2.18.
> These
> SRCREVs are updated to the correct values.
>
> Signed-off-b
might
show something else. The other place to look is in the output of
'dmesg'.
Does un-plugging and re-plugging the network cable (without running
'ifup' or 'ifdown') make any difference?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
d Poky. How often would you have to test Arch Linux when
major package updates can occur on any given day?
Don't get me wrong, I love Arch and use it on my desktop for all
development work. But for builds I want to be known-good, I push them
off to a Ubuntu Server virtual machine.
quot;supported" doesn't
mean no-one cares about it. When the sanity check for a broken make
3.82 was added to OE, I put in a bug report to Arch
(https://bugs.archlinux.org/task/35968) and it got fixed.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
__
the support for this will be in? I'm
wondering whether it's in meta-yocto, meta-intel or something
Angstrom-specific.
Cheers,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing lis
e former as it is a version of opkg not a separate fork.
Is there a convention for this or should I just make my own decision?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 3 August 2013 11:52, Paul Barker wrote:
> Should I call this:
>
> "opkg_testing.bb"
> set PREFERRED_VERSION_opkg = "testing" to use
>
Martin has just commented elsewhere that having this recipe in a meta-opkg layer
will always override the recipe in
On 3 August 2013 12:17, Martin Jansa wrote:
>
> This should be discussed on oe-core ML rather then yocto ML.
>
I still get confused over which mailing list to post certain questions
to. I'll start a fresh discussion on oe-core once I've had another
think about this.
--
Pa
on my emails. I'm
guessing they probably go to this list or someone on this list. So I'm
also going to propose adding a README file to opkg-utils with info on
who's maintaining it and where to send patches.
I now seem to be the de-facto maintainer of opkg itself so it would
make sen
Image files will typically contain lots of null blocks and should compress well.
This will help with distribution of images over slow network links.
Signed-off-by: Paul Barker
---
classes/sdcard_image-rpi.bbclass | 18 ++
1 file changed, 18 insertions(+)
diff --git a/classes
custom patches and the fact that you just need to ensure that
'make' is called then copy the resulting binary and man page.
Have you written your own recipes before?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
On 20 August 2013 18:11, Andrei Gherzan wrote:
> On Fri, Aug 16, 2013 at 1:48 PM, Paul Barker wrote:
>>
>> +# Compression method to apply to SDIMG after it has been created. May be
>> "none",
>> +# "gzip", "bzip2" or "xz". Setti
this as an alternative kernel version,
even if we keep the default as is.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 21 August 2013 23:41, Andrei Gherzan wrote:
> On Wed, Aug 21, 2013 at 11:12 PM, Paul Barker wrote:
>>
>> Setting it to one of the other listed values will cause the SDIMG to
>> be re-named. I think the code is as I intended, the documentation
>> comment n
.setVar('PROVIDES', ' '.join(new_provides))
> +
> +# We are now machine specific
> +d.setVar('PACKAGE_ARCH', d.getVar('MACHINE_ARCH'))
> +}
This really needs to check whether MACHINE="raspberrypi" before
changing anything.
so not entirely sure on which protocols github does and doesn't
support.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
eck if you add the
'-M' option to catch renames. I always forget to add it so I did "git
config --global diff.renames copy" to catch all renames and copies
whenever I do format-patch.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
the distro name, list of architectures and
the URLs, but the structure is fine.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
a 3.8.y series kernel - I'll post the patch
to add that recipe once it's confirmed working.
Paul Barker (2):
sdcard_image-rpi.bbclass: Allow optional compression
README: Fix IMAGE_FSTYPES example
README | 4 +++-
classes/sdcard_image-rpi.bbclass | 20
Image files will typically contain lots of null blocks and should compress well.
This will help with distribution of images over slow network links.
Signed-off-by: Paul Barker
---
README | 2 ++
classes/sdcard_image-rpi.bbclass | 20
2 files
The SD image is always created with the extension "rpi-sdimg" and this cannot be
changed by editing IMAGE_FSTYPES.
Signed-off-by: Paul Barker
---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README b/README
index 6f947c7..8fdfdd2 100644
--- a/README
++
Upstream commit d996a1b91b2bf3dc06f4f4f822a56f4496457aa1, dated 2013-08-07.
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi_3.8.13.bb | 35
1 file changed, 35 insertions(+)
create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
diff
Build and boot tested.
Andrei: I'm unsure if you want this to be the new preferred kernel version, I'll
leave that up to you.
Paul Barker (1):
linux-raspberrypi: Add version 3.8.13
recipes-kernel/linux/linux-raspberrypi_3.8.13.bb | 35
1 file changed, 35
enefit marine conservation! (If anyone else is, I'd definitely like
to hear from them)
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
eta-raspberrypi states that you need meta-openembedded
as well (specifically, the meta-oe layer). I'm not sure that this is
the cause of your error though.
What branches of the different layers are you using? I just want to
make sure they're all the same. Also, what ver
nembedded-core again. Could you post your full bblayers.conf?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 5 September 2013 09:08, JC wrote:
> On 05/09/2013 10:04, Paul Barker wrote:
>> The log you've attached shows paths for poky as well as
>> openembedded-core. Poky is basically a combination of
>> openembedded-core, meta-yocto and bitbake so you don't want to
gt; Am 03.09.2013 14:26, Paul Barker wrote:
>> +PR = "r6"
>
> I guess this does not matter, but would r1 not be more natural?
We can probably drop PR completely.
>> +UDEV_GE_141 ?= "1"
>
> This is already part of linux.inc, is it necessary here again
ts. If you're cloning poky that's all you
need. If you're cloning openembedded-core, bitbake and meta-yocto
separately you should use the '1.18' branch of bitbake as that matches
with the 'dylan' branch of the other repositories.
--
Paul Bar
7 files changed, 140 insertions(+), 149 deletions(-)
> create mode 100644 recipes-kernel/linux/linux-raspberrypi.inc
> create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.11.0.bb
> create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.13.bb
>
> --
> 1.8.1.4
ypi
There's also a README file at the root of this layer, that should
contain the instructions you need. If you have any problems with it
let us know.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
On 11 September 2013 08:29, Paul Barker wrote:
> On 10 September 2013 23:36, wrote:
>> From: Philipp Wagner
>>
>> Hi,
>>
>> as follow-up to the discussion in
>> [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Add version 3.8.13
>> I've re
ypi. libcurl5
RECOMMENDS curl-certs, it does not DEPEND on this. Sounds like the
smart package manager isn't so smart.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ld be a
good time to quickly review them and ensure they're still relevant.
Any comments about the organisation of janitorial/newbie friendly
tasks in general are also welcome.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
_
e.
>
Currently it's both as both can be seen from the YP wiki page.
> For the wiki task list, maybe add an "Assignee:" line, so that someone knows
> if the task is being worked on? Would be frustrating to work on a task only
> to find someone else did the same thing.
&
gt;
> So how do we pack it as non striped one ??
>
It's likely in -dbg (so probably valgrind-dbg). Try
adding that to your IMAGE_INSTALL variable.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing l
On 24 August 2013 01:02, Andrei Gherzan wrote:
> On Fri, Aug 23, 2013 at 3:26 PM, Martin Jansa
> wrote:
>> On Fri, Aug 23, 2013 at 11:59:10AM +0100, Paul Barker wrote:
>> >
>> > This really needs to check whether MACHINE="raspberrypi" before
>>
On 2 September 2013 21:11, Paul Barker wrote:
> I've incorporated the changes recommended by Andrei against the first version
> of
> the patch. Whilst editing the README file I noticed that the IMAGE_FSTYPES
> example didn't make sense (or include a closing double-quote)
On 13 September 2013 18:06, Paul Barker wrote:
> On 11 September 2013 08:29, Paul Barker wrote:
>> On 10 September 2013 23:36, wrote:
>>> From: Philipp Wagner
>>>
>>> Hi,
>>>
>>> as follow-up to the discussion in
>>> [yocto]
e
Yocto Project may be able to help us with this. I've got a few
questions on how this would work if we can do it. Is there anyone in
particular I need to talk to or should we just discuss this on list?
Thanks,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://
be good to meet a couple of other OpenEmbedded developers as well!
Thanks,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
hotos anyway and bring those along.
Thanks,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
raspberrypi"
>
> -SRCREV = "d2c9f912da389c23ed27e81e940be3540f64fc59"
> +SRCREV = "6da40ffd91f2b3c2aa8471195813322ae5d0cb0d"
> SRC_URI =
> "git://github.com/raspberrypi/userland.git;protocol=git;branch=master \
>"
&g
octo Project Brand Guidelines" link on
https://www.yoctoproject.org/about/trademark-policy points to the page
https://www.yoctoproject.org/ecosystem/branding-compliance-guidelines.
That page doesn't seem to contain any info.
Cheers,
--
Paul Barker
Email: p...
o you definitely want
all this in one package and not separate packages for the firmware and
such?
A lot of recipes have to customise the install function and add extra
directories to FILES_*, don't worry about that.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
_
On 6 February 2014 15:22, Edward Vidal wrote:
> Hello All,
> In Dec 13 I used meta-oe on a dylan branch and x264 was included as part of
> meta-oe/meta-oe/recipes-multimedia/x264.
Looks like it's moved to oe-core:
http://layers.openembedded.org/layerindex/branch/dora/recipes/?q=
This sounds like a question about whatever the default OS is for the
Galileo not about opkg. I could tell you how to add feeds to opkg but
I can't tell you what URL you'd need for each feed.
Do you know what the default Linux distribution is? If so I might be
able to point you in the
n3
installed with the python standard library (as the standard library
already includes all the tests). This may be a good option for adding
ptest support to the python3 recipe - it'd just be a single 50-line
'run-ptest' script written in python.
Does that sound interesting
On 21 February 2014 16:08, Randy MacLeod wrote:
> On 14-02-18 04:27 PM, Paul Barker wrote:
>>
>> I've just thrown together a couple of things which may be useful.
>> They're currently slightly hackish but I could improve them and share
>> them/submit them as p
l allowed
to be infront of the 'control.tar.gz' file in the archive? Other than
that question, the change looks good at first glance.
If any of that doesn't work for you, let me know and I'll try to help out.
Thanks,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.pa
27;ll merge this to the main opkg-utils
repository and update the recipe in openembedded-core to use the new
commit.
Cheers,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 1 March 2014 14:29, Paul Barker wrote:
> On 25 February 2014 20:26, Thilo Cestonaro wrote:
>> With a change from last august in dpkg-deb, the packages generated by
>> opkg-build will not be accepted by dpkg-deb anymore.
>> The change disallows that the data.tar.gz is pa
uot; selector to whatever
version of The Yocto Project you're using.
Hope this helps,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
earch link I posted.
You won't find '-devel' packages though, I think the OE convention is
to use '-dev' instead. The recipe index doesn't show them, but most
packages offer '-dbg', '-dev', etc as appropriate.
Thanks,
--
n if that compatibility isn't
necessary.
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 3 March 2014 09:02, Paul Barker wrote:
> On 1 March 2014 14:29, Paul Barker wrote:
>> On 25 February 2014 20:26, Thilo Cestonaro wrote:
>>> With a change from last august in dpkg-deb, the packages generated by
>>> opkg-build will not be accepted by dpkg-deb anymor
1 - 100 of 355 matches
Mail list logo
