Hi Lucian / Alex,
Just a reminder, it looks like we still need to update SANITY_TESTED_DISTROS
to match the host distros we are testing against for 1.8.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yoc
Use PACKAGECONFIG to build a version of mono with or without X support in
function of x11 DISTRO_FEATURES.
Tested on qemux86 (mono using X) and imx6 board (mono without X)
Signed-off-by: Enric Balletbo i Serra
---
recipes-mono/mono/mono-native_3.12.1.bb | 8 ++--
recipes-mono/mono/mono_3.1
Hi all,
I write a recipe to build an JNI layer for my C library, the JNI library
gets compiled right, but no .rpm is generated besides -dev and -dbg. I
suspect that the rpm is getting empty.
Here is the recipe: http://pastebin.com/vqtaM1Fv
Looking on package directory I got the compiled .so's
[r
Hello,
it looks like that Amlogic based devices like the ODROID-C1 [1]
requires their u-boot compiled with an arm-none-eabi toolchain. The
rest kernel and rootfs is compiled with standard arm eabi toolchain. I
am wondering how to support this in yocto/openembedded.
With kind regrads,
Christian
Hey All:
I'm trying to switch a large project we've been working on for years from
TinyCore to yocto.
I've avoided dealing with this up until now, but it can't wait any longer.
I want to keep the yocto SDK that we distribute to our development team as lean
as possible so that we don't have to
Hilst:
You can specify what files get installed to what packages with
FILES_${PN}-
In your case, something like:
FILES_${PN} = "${libdir}/libDigital*"
FILES_${PN}-dbg = “"${libdir}/.debug/*"
would probably work fine.
I’d also recommend using “oe_runmake” instead of “make” in your build funct
On Wed, Mar 18, 2015 at 12:55 PM, Christian Ege wrote:
> Hello,
>
> it looks like that Amlogic based devices like the ODROID-C1 [1]
> requires their u-boot compiled with an arm-none-eabi toolchain. The
> rest kernel and rootfs is compiled with standard arm eabi toolchain. I
> am wondering how to s
Hello,
I'm using Yocto (dizzy) with meta-ti and the linux-ti-staging kernel 3.14.x to
build for BeagleBone Black.
I've written a custom char driver with several ioctl() calls, and I'm patching
that into the linux-ti-staging kernel. The driver adds a new UAPI header file
that goes in the kernel
I think I've answered my own question.
The existing files installed in the build root /usr/include/linux/... are put
there by the linux-libc-headers package.
According to a prominent comment in
meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc, I shouldn't try
to fiddle with those,
Hey All:
I'm trying to setup a local YUM repo using the RPMs in
/tmp/deploy/rpm/
I've added a .repo file to /etc/yum/repos.d with the following lines:
[local]
name=yocto-core2_32
baseurl=file:///home/ebolton/yocto/poky/build-max/tmp/deploy/rpm/core2_32
enabled=1
gpgcheck=0
and setup my mai
10 matches
Mail list logo