then mosquitto will build properly.
> Regards,
>
> On Mon, Jan 28, 2019 at 6:19 PM Edward Wingate
> wrote:
>
>> The first time I did a build, my mosquitto recipe worked. Then I did
>> a 'bitbake -ccleanall mosquitto', and now when I do 'bitbake
>&
Thank you. I must have based the recipe on one that downloaded a
tarball, and didn't notice until now the checksums never had to be
changed.
On Mon, Jan 28, 2019 at 11:25 AM Burton, Ross wrote:
>
> On Mon, 28 Jan 2019 at 19:23, Lukasz Zemla wrote:
> > Checksums were introduced to ensure data co
I have a recipe that has a SRC_URI retrieving from a mercurial repo:
SRC_URI = "hg://server/project;module=name;rev=tip"
SRC_URI[md5sum] = "xxx"
SRC_URI[sha256sum] = "yyy"
I changed the SRC_URL to retreive from a specific revision instead of tip:
SRC_URI = "hg://server/project;module=name;rev=1234
The first time I did a build, my mosquitto recipe worked. Then I did
a 'bitbake -ccleanall mosquitto', and now when I do 'bitbake
mosquitto', I get this error:
DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: SITE files ['endian-littl
I understand that a Linux distribution created with Yocto is composed
of various packages, each with their own license, and the obligations
of the licenses must be met. But are there any
restrictions/obligations on the distribution itself when created with
Yocto? Or is the license of a Linux distr
I have configured Yocto to build a jethro distribution that I've been
using for the past 3 years. I want to duplicate this configuration on
another computer as a backup build machine. I could just copy over
the poky directory and all my layers, but I think this would copy over
unnecessary files (
My system has a USB-SSD drive and I added this to my fstab:
/dev/sda1 /mnt/driveauto defaults,nonempty 0 0
But it doesn't get mounted on start-up. I can use "mount -a" after
start-up and it mounts successfully.
Everything else in fstab gets mounted on boot. Does anyone know why
my new e
I don't have any video or display hardware on my system, but I want to
install an X server and window manager in order to VNC in. Is this
possible? Would using the matchbox-* recipes allow me to do this?
Would I also need any x11 recipes? Thanks for any suggestions.
--
_
On Thu, Mar 3, 2016 at 8:27 AM, Mark Hatle wrote:
> At some point during product development a lead/architect needs to make the
> decision to 'freeze' development and at that point everything is
> tagged/branched
> and only backports are used from them on. (If the number of backports gets
> to
On Mon, Jul 25, 2016 at 1:27 AM, Nicolas Dechesne
wrote:
> hmm. you shouldn't set DISTRO in conf/layer.conf, that doesn't sound
> right. DISTRO needs to be set in local.conf (or any of the other build
> specific conf files).
I agree, I don't know why I had it in conf/layer.conf. Just
beginner's
On Sun, Jul 24, 2016 at 7:38 AM, Khem Raj wrote:
> On Sun, Jul 24, 2016 at 12:34 AM, Edward Wingate wrote:
>> Ah, I found it. I had inadvertently deleted one line
>> (DISTRO="mydistro") from my layer's conf/layer.conf.
>>
>> Am I doing this right th
t seems redundant to put it in mydistro.conf
as well.
On Sun, Jul 24, 2016 at 12:04 AM, Edward Wingate wrote:
> On Sat, Jul 23, 2016 at 11:05 PM, Khem Raj wrote:
>> Move these DISTRO settings above require conf/distro/poky.conf
>
> That didn't change anything. And it had bee
On Sat, Jul 23, 2016 at 11:05 PM, Khem Raj wrote:
> Move these DISTRO settings above require conf/distro/poky.conf
That didn't change anything. And it had been working like that for a
long time now. Just a few days ago, it stopped taking effect and
reverting back to poky. I have not been able
This is in my layer's conf/distro/mydistro.conf file:
require conf/distro/poky.conf
DISTRO = "mydistro"
DISTRO_NAME = "MyDistro"
These variables took effect before, but now bitbake is reverting back
to DISTRO="poky" and DISTRO_NAME = "Poky (Yocto Project Reference
Distro)" (used for /
Thanks all! Was having a fit trying to get it to work until
Christopher's advice to set S to ${WORKDIR}/git.
On Thu, Jun 9, 2016 at 9:59 AM, Christopher Larson wrote:
>
> On Thu, Jun 9, 2016 at 9:03 AM, Burton, Ross wrote:
>>
>> On 9 June 2016 at 16:58, Edward Winga
Does anyone have an example of a recipe that installs a python module
from a git repo? There is a python module that is not regularly
updated on PyPI, but its git repo is up to date. All the examples of
python module recipes I can find uses PyPI:
http://git.openembedded.org/meta-openembedded/tree
On Wed, Jun 8, 2016 at 1:58 AM, Oleksandr Poznyak
wrote:
> Hi, Edward.
> Your approach is valid. But RREPLACES is not enough.
>
> You should define that your package and original ones are conflicting and
> that it provides the same as original one for other packages.
>
> So in your recipe:
>
> RPR
On Tue, Jun 7, 2016 at 1:47 PM, Paul Eggleton
wrote:
>
> So what this will give you is alternative packages to be installed instead of
> sysvinit-inittab in your image.
I was under the (mistaken) impression that my recipe will run in
addition to, not instead of, sysvinit-inittab (occurring after
On Tue, Jun 7, 2016 at 3:20 AM, Paul Eggleton
wrote:
> Let's clarify that for the benefit of others reading along - you absolutely
> *can* have multiple bbappends per recipe. To answer the original question
> though, no you cannot have bbappends conditionally applied based on what image
> is being
On Mon, Jun 6, 2016 at 3:06 PM, Edward Wingate wrote:
> It seems I cannot just append to inittab using the echo statements
> because /etc/inittab is not part of this recipe. Must I duplicate
> inittab first in my imageX-inittab.bb recipes?
I modified the recipes to include their ow
On Mon, Jun 6, 2016 at 2:10 PM, Oleksandr Poznyak
wrote:
> Hi,
> Unfortunately You can't have two *.bbappend files per one package (recipe).
>
> You can create two new recipes where You'll install what You need and plus
> add sysvinit-inittab to DEPENDS variable in those recipes. This will help to
On Wed, Jun 1, 2016 at 7:15 PM, Diego wrote:
>
> Hi Oleksandr,
>
> your approach is really interesting, but I'm unsure how to proceed with
> step 2) of your list.
>
> I've added the following in the bbappend:
>
> python do_package_prepend() {
> d.setVar('PACKAGES', "${PACKAGES} ${PN}-fstab-reg
The first time I used mosquitto_1.3.4.bb from
meta-intel-iot-middleware a few months ago, it worked and I've been
using it in my build since. Today, I created a new yocto build
directory and having trouble getting mosquitto to build now.
The directory
/yocto/poky/build/tmp/work/cortexa9-vfp-neon
On Fri, Oct 30, 2015 at 8:10 AM, Daniel. wrote:
> I saw that REMOTEPROC is selected by other *_REMOTEPROC config
> options. It seems a driver to handle another process on same board,
> right?
> It seems also that other architetures select REMOTEPROC, so if you're
> creating a new board with a remo
On Thu, Oct 29, 2015 at 6:10 AM, Bruce Ashfield
wrote:
> That's the kernel's configuration subsystem at play, it still has to
> process the the defconfig (which was placed as .config before starting
> the kernel build). Invalid options are removed, others are selected
> by Kconfigs, etc. So what y
On Tue, Oct 27, 2015 at 5:36 AM, Daniel. wrote:
> I suggest that you do an "bitbake -fc configure YOUR_KERNEL" and
> inspect the .config WORKDIR folder. Is that yours .config?
I'm not sure if this is the WORKDIR I'm suppose to be looking at, but
after I ran that bitbake command, I found my defcon
On Mon, Oct 26, 2015 at 1:03 AM, Paul Eggleton
wrote:
> Kernel modules are packaged separately and typically not included in the image
> by default; if you wish to include them you have two choices:
>
> 1) Install the kernel-module- package(s) individually for the
> module(s) you wish to use
>
> 2
On Sat, Oct 24, 2015 at 1:43 PM, Edward Wingate wrote:
> I am using fido release and this is my
> linux-wandboard_3.14.28.bbappend file, just 2 lines:
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> SRC_URI += "file://defconfig"
>
> I'm trying t
ention on any "*.bb*" file for fido release of poky, but...
>
> I've used .bbappend for kernel recipes, selecting custom modules based on
> MACHINE and they worked fine... Can you share poky release and the .bbapend
> file?
>
> Cheers,
>
> 2015-10-19 4:37 GMT-02:0
I created a linux-wandboard_3.14.28.bbappend that just specifies a new
defconfig. I see my defconfig being used to generate a .config. But
then something renames .config to .config.old and replaces it with
another .config that no longer has the configurations I want. I can't
find what is doing t
I'm sorry, I posted this to the wrong list. Meant to post to u-boot list.
On Fri, Sep 25, 2015 at 10:12 AM, Edward Wingate wrote:
> I have been using u-boot with CONFIG_SPI_FLASH_MTD. This has allowed
> me to use MTD/UBI/UBIFS with SPI flash. I now want to use
> CONFIG_ENV_
I have been using u-boot with CONFIG_SPI_FLASH_MTD. This has allowed
me to use MTD/UBI/UBIFS with SPI flash. I now want to use
CONFIG_ENV_IS_IN_UBI, but after enabling this, u-boot can't read the
environment on start-up:
===
U-Boot 2015.07 (Sep 24 2015 - 17:10:41 -0700)
Model: Zynq Zed Developm
How can I create an empty directory in my root FS? I want to create
/mnt/sd to use as a mount point. I put "install -d ${D}/mnt/sd" in
do_install() of one of my recipes, but I get:
ERROR: QA Issue: my-recipe: Files/directories were installed but not shipped
/mnt
/mnt/sd [installed-vs-shipped
Typo in last email, I used "mem=256M", not "mem=256MB"
On Tue, Jun 9, 2015 at 9:03 AM, Edward Wingate wrote:
> Thanks, Nathan, for your help. It worked, with a little oddity I don't
> understand.
>
> In my uEnv.txt, I set both fdt_high and initrd_high t
to reflect 256MB? Changing it to "reg =
<0x0 0x1000>" didn't seem to have any effect. The mem bootarg
seems to be the thing that actually works to limit the amount of
memory Linux sees.
On Mon, Jun 8, 2015 at 9:45 PM, Nathan Rossi wrote:
> On Tue, Jun 9, 2015 at 4:06 A
I am using Yocto with meta-xilinx layer to create a distribution for a
custom Zynq 7000 board with 512MB RAM. In my uEnv, I'm loading the
kernel to 0x0010_, device tree to 0x0190_ and ramdisk image to
0x0210_.
Later in the boot process, I see this:
Loading Kernel Image ... OK
L
> From: Gary Thomas
> To: yocto@yoctoproject.org
> Date: Fri, 14 Nov 2014 12:04:23 -0700
>
> On 2014-11-14 11:52, Edward Wingate wrote:
>>
>> On Fri, Nov 14, 2014 at 9:39 AM, > <mailto:yocto-requ...@yoctoproject.org>> wrote:
>>
>> From: Gary
On Fri, Nov 14, 2014 at 9:39 AM, wrote:
> From: Gary Thomas
>
> On 2014-11-14 10:10, Edward Wingate wrote:
> >
> > The ramdisk image ballooned to 22MB though. It's expected, but due to
> flash size constraints, Python may not be an option in this case.
>
&g
On Fri, Nov 14, 2014 at 12:13 AM, Maciek Borzecki <
maciej.borze...@open-rnd.pl> wrote:
> On czw, 2014-11-13 at 23:12 -0800, Edward Wingate wrote:
> > I've been trying to get an existing python flask application running
> > on an embedded linux distro (Poky).
I've been trying to get an existing python flask application running on an
embedded linux distro (Poky). The web app was originally deployed on a
Debian distro. I need to move the application to a less heftier board
and wanted to try a distro created by Yocto, rather than try to pare down
Debian.
40 matches
Mail list logo
