To: Matt Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] CMake based recipes and defining CMAKE_BUILD_TYPE
On Wed, Feb 6, 2019 at 11:53 PM Andreas Müller wrote:
>
> On Wed, Feb 6, 2019 at 11:24 PM Andreas Müller
> wrote:
> >
> > On Wed, Feb 6, 2019 at 11:05 PM Matt
Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] CMake based recipes and defining CMAKE_BUILD_TYPE
On Wed, Feb 6, 2019 at 7:39 PM Matt Schuckmann
wrote:
>
> I'm trying to understand why the cmake.bbclass doesn't make any attempt to
> set CMAKE_BUILD_TYPE and what the design philosop
I'm trying to understand why the cmake.bbclass doesn't make any attempt to set
CMAKE_BUILD_TYPE and what the design philosophy behind that is?
On the surface I would expect that the default build type would be Release but
I can see how that might not always be the right choice. I'm really
If you are using systemd you can simply create a separate writeable partition
and then use the volatile_binds.bb recipe to map files or directories from the
read only rootfs to the writable partition via bind mounts.
If you are not using systemd you can do the same thing with sysVinit you'll
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Thursday, April 23, 2015 5:20 PM
To: Matt Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Strange error trying to use externalsrc
On Thursday 23 April 2015 12:37:30 Matt Schuckmann
http://www.yoctoproject.org/docs/1.4/dev-manual/dev-
manual.html#buildi
ng-so
ftware-from-an-external-source
https://github.com/openembedded/oe-
core/blob/dylan/meta/classes/extern
alsrc
.bbclass
Ah, right, dylan - yes things were a bit different in that version.
It's possible it
I'm trying to use the externalsrc class to make it easier build an application
under active development.
I'm working off of the Dylan branch.
If I add the following 2 lines to my site.conf
INHERIT += externalsrc
S_pn-keypadd = /home/dev/builds/zanzibar/keypadd
I get the following error when
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Craig McQueen
Sent: Monday, April 20, 2015 10:23 PM
To: yocto@yoctoproject.org
Subject: [yocto] U-Boot with a different default device tree, for
BeagleBone-similar system
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Monday, April 20, 2015 7:52 AM
To: Matt Schuckmann; Yocto Project
Subject: Re: [yocto] Problems enabling systemd
On 04/20/2015 04:43 AM, Anders Darander wrote:
* Matt Schuckmann matt.schuckm
I'd guess that you're getting some errors earlier than this in the
bootlog? Could you paste them?
Cheers,
Anders
Anders, below is a more complete boot log
Thanks for the help
Matt S.
Starting kernel ...
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version
I've got an image for a AM3352 system based on Dylan and Arago and I'm trying
to switch to systemd for init.
So far I haven't had much luck.
First off I'm getting different results depending on where I turn it on.
I'm turning it on via the following 2 lines:
DISTRO_FEATURES_append =
The v4l-utils recipe defines VIRTUAL-RUNTIME_ir-keytable-keymaps and the
ir-keytable package appears to RDEPENDS on its value.
I want to define my own key map so I think that I should create a new package,
called my-rc-keymaps, for now it simple installs a file in
/lib/udev/rc_keymaps
In my
I find myself in the situation where my project is currently using
meta-openembedded from the Dylan branch but I want to use a recipe from the
current master.
Is it better for me to copy the recipe into my own branch off of Dylan or to
copy the recipe into my own meta-layer?
What works out
I've run into this a couple times now and I still don't get it so please help
me understand.
I'm trying to understand how to include just the ir-keytable package of the
v4l-utils_1.6.2.bb recipe.
At first I was getting a lot of Nothing PROVIDES or Nothing RPROVIDES error
messages when I tried
I've been fighting a problem where bitbake can't find the php package
during the do_rootfs task and I've determined that it has something to
do with the bbappend file I added to my layer for php.
It's funny how once you give up and post a question to a message board new
insights pop into
I've been fighting a problem where bitbake can't find the php package during
the do_rootfs task and I've determined that it has something to do with the
bbappend file I added to my layer for php.
The problem is with my bbappend file (php_5.4.14.bbappend) no ipk package gets
created for the
I I'm trying to understand this snippet from the php recipe
do_install_append_class-target() {
install -d ${D}/${sysconfdir}/
if [ -d ${D}/${STAGING_DIR_NATIVE}/${sysconfdir} ];then
mv ${D}/${STAGING_DIR_NATIVE}/${sysconfdir}/* ${D}/${sysconfdir}/
fi
rm -rf ${D}/${TMPDIR}
I'm looking for some tips on debugging package install problems.
Recently I've had a problem where edits to a pkg_postinst function in one of my
recipes was not getting run when rebuilding my image. The only way I could get
the pkg_postinst() function to run was to wipe out my complete
Mat,
I'm fairly new to OpenEmbedded (4 months now and I still feel like a noobi but
I'm trying to give back while the pain is still fresh in my mind)
For something like u-boot it kind of depends on what your changing. If you need
to change the u-boot code and the changes are small then
I'm going nuts on this, I can't figure what magic incantation is to ensure that
my changes to a recipe getting applied to the image I'm building.
I'm working off the Dylan branch (IT amsdk 7.0)
Here is my current work flow,
Make some small edit to a file in a recipe in my layer, say a
-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Matt Schuckmann
Sent: Thursday, December 04, 2014 6:24 PM
To: yocto@yoctoproject.org
Subject: [yocto] How to force bitbake to install a package
I'm going nuts on this, I can't figure what magic incantation
(if you use a persistent overlay).
On 11/26/2014 08:51 AM, Matt Schuckmann wrote:
I've been investigating the support for read only root file systems
and trying to suss out how to support persistent writeable files in my
image where the root file system is read only, this seems like a very
Syed,
Your problem sounds similar to a problem I had getting my own headers and
static library included in the SDK.
Check out this thread to see if it helps.
https://lists.yoctoproject.org/pipermail/yocto/2014-September/021678.html
Matt S.
--
I've been investigating the support for read only root file systems and trying
to suss out how to support persistent writeable files in my image where the
root file system is read only, this seems like a very common thing for an
embedded Linux system to need but I'm not seeing the support for
-Original Message-
From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
Sent: Thursday, October 30, 2014 6:52 AM
To: Matt Schuckmann
Cc: Yocto Project
Subject: Re: [yocto] Help me understand Openembedded variable expansion
On Tue, 2014-10-28 at 10:11 -0700, Matt
Matt S.
Sent from my pocket
On Oct 28, 2014, at 12:03 AM, Isak Lichtenstein
isak.lichtenst...@kistler.com wrote:
Hi Matt,
I'm working on including the u-boot fw utility tools in my image,
specifically
fw_printenv and fw_setenv.
For these to work the file fw_env.config needs to be
So there is something I just don't get about how variables get created,
expanded, interpreted, etc in Bitbake
For example I'm trying to copy some of the techniques in the Poky Tiny
distribution to reduce my image size and build time.
One of the fragments is this one.
# The mtrace script
I'm working on including the u-boot fw utility tools in my image, specifically
fw_printenv and fw_setenv.
For these to work the file fw_env.config needs to be placed at
/etc/fw_env.config.
I can see in oe-core/meta/recipes-bsp/u-boot/u-boot.inc there is a test that if
fw_env.config is in the
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Chris Tapp
Sent: Tuesday, October 21, 2014 1:54 PM
To: Yocto Project
Subject: [yocto] Ubuntu 14.04 as a build host for danny
I'm currently building with danny under
I'm pretty confused about what is the best way to go on this.
I realize that there are several paths that I could take but I really don't
know which is the best way to go.
We are creating a new board largely based off the beaglebone design but
customized to our needs.
I'm basing my software
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Tuesday, September 23, 2014 2:10 AM
To: Matt Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to include static library and headers in sdk
On Monday 22 September 2014 18:57:03 Matt
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Tuesday, September 23, 2014 9:54 AM
To: Matt Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to include static library and headers in sdk
On Tuesday 23 September 2014 09:43:55 Matt
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Tuesday, September 23, 2014 10:26 AM
To: Matt Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to include static library and headers in sdk
On Tuesday 23 September 2014 10:21:44
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Tuesday, September 23, 2014 11:12 AM
To: Matt Schuckmann
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to include static library and headers in sdk
On Tuesday 23 September 2014 10:57:21
I've got a custom image and 2 custom recipes both very simple libraries that
use cmake.
I included the libraries into my image by adding
EXTRA_IMAGEDEPENDS += simple1
EXTRA_IMAGEDEPENDS += simple2
To my image recipe.
When I build my image (i.e. bitbake custom-image ) I can see that the
I guess the problem is kernel related. Maybe the kernel configuration for
linux-yocto-tiny lacks something.
Please open a bug in bugzilla, if convenient.
https://bugzilla.yoctoproject.org
Thank you, I created a bug in bugzilla,
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6353.
I
I'm trying to come to grips with Yocto and poky and a minimal image so I'm
trying to build boot and modify poky-tiny and having no luck booting it in qemu.
I'm following instructions here
https://wiki.yoctoproject.org/wiki/Poky-Tiny#Some_information_about_the_running_system
but when I run the
37 matches
Mail list logo
