not sure if this is the right list (oe/poky/yocto?), but since it
involves yocto docs, i'll ask here.
there seem to be some (admittedly minor) inconsistencies in both the
docs and code for checking the sanity of a build environment (i'm
basing this off the current yocto docs and the current
more pedantry -- reading both the bitbake user manual and the yocto
reference manual variable glossaries:
http://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#ref-variables-glossary
i'm sure i asked this once before, but is there any long-term plan
for more carefully marking up the yocto docs semantically? as in, most
things that represent filenames or variables or commands or code are
simply tagged as filename, even when this is not really appropriate.
to be
Hello,
I've been working on creating a recipe for the library mongoose for use
in a custom layer in Yocto. The library provides a .so in /usr/lib and a
.h in /usr/include and is depended (DEPENDS=libmongoose) on in another
recipe for a my main application. When trying to bitbake my image
It seems that 585324fee380109acd9986388f857f413a60b896 is no
longer there in git and it has been rewritten to
ffc3ad4945da69f3caa2b40e4eed715a9a8d9526
Change-Id: I9ffe8bd9bcef0d2dc5e6f6d3a6e4317bada8f4be
(From OE-Core rev: b193c7f251542aa76cb5a4d6dcb71d15b27005eb)
(From OE-Core rev:
Hi
I guess the file should be named libmongoose_5.3.bb and not
libmongoose-5.3.bb
Tirsdag den 17. juni 2014 12:30:36 skrev Henric Eriksson:
Hello,
I've been working on creating a recipe for the library mongoose for use
in a custom layer in Yocto. The library provides a .so in /usr/lib and
I could look at this... low on the priority list right now though but good
point.
Thanks,
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
Sent: Tuesday, June 17, 2014 5:51 AM
To: Yocto discussion list
These two glossaries are not replicates of each other by design. You might
notice also that some definitions for the same variable differ as well. The
intent is to have the variables in ref-manual be specific (if possible) for YP
and the ones in bitbake-user-manual to be specific for that
Søren Holm skrev:
Hi
I guess the file should be named libmongoose_5.3.bb and not
libmongoose-5.3.bb
My bad. Typo in the email, the actual file is called libmongoose_5.3.bb.
Tirsdag den 17. juni 2014 12:30:36 skrev Henric Eriksson:
Hello,
I've been working on creating a recipe for the
Hi Patrick,
On Tuesday 17 June 2014 09:36:05 Patrick Doyle wrote:
It seems that 585324fee380109acd9986388f857f413a60b896 is no
longer there in git and it has been rewritten to
ffc3ad4945da69f3caa2b40e4eed715a9a8d9526
FYI I sent a similar patch for dora to the OE-Core list a week ago;
Attendees: Armin, Corneliu, Stephen, Melissa, Darren, Cristian, Tom, Saul,
Michael, Paul, Nitin, Mathew, David,
* Opens collection - 5 min (Stephen)
* Yocto 1.7 status - 5 min (Stephen/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status
Thanks Paul,
I hope I didn't step on any toes with this. I'm still confused about
what parts of the project are Yocto and what parts are OE.
Do you have any guesses as to when this might show up in the official
dora branch?
I am asking because we have a development flow here (I'm still not
sure
Hello,
I would like to have yocto generate two copies of busybox, one
statically-linked and one dynamically linked. So I try to make a copy of
the busybox recipe and give it a new name like busybox-s_x.bb
But my knowlege of yocto comes up short and I get lots of errors.
Is there a way
Hi,
I have two kernels for my device: one is current mainline kernel and
one is an older kernel that supports magic proprietary hardware
acceleration blobs. Some developers want the modern kernel, others
need the hardware acceleration which means they need the older kernel
plus a bunch of
On 06/17/2014 11:31 PM, Patrick Doyle wrote:
Thanks Paul,
I hope I didn't step on any toes with this. I'm still confused about
what parts of the project are Yocto and what parts are OE.
The oe-core is a part of yocto project, which is the meta layer in
poky.
Do you have any guesses as to
On Tue, Jun 17, 2014 at 5:41 PM, Brian Smucker b...@bsmucker.eu.org wrote:
Hello,
I would like to have yocto generate two copies of busybox, one
statically-linked and one dynamically linked. So I try to make a copy of the
busybox recipe and give it a new name like busybox-s_x.bb
But my
On Tuesday 17 June 2014 23:56:58 Robert Yang wrote:
Do you have any guesses as to when this might show up in the official
dora branch?
I've resend it oe-core, and will ping RP sooner.
Thanks.
@Paul,
I'm sorry, seems that I missed your email, but I still can't find it
when I searched
Andrea,
Thanks for your reply.
In my case, the difference in the two recipes is quite minimal: a
different defconfig and a modified busybox.inc.
Generating the altered recipe is not my question.
My question is, now that I have two overlayed recipes for busybox, the
standard and the custom,
On Tuesday 17 June 2014 11:31:52 Patrick Doyle wrote:
Thanks Paul,
I hope I didn't step on any toes with this.
No, not at all; I just wanted to let you know we are working on the issue.
I'm still confused about what parts of the project are Yocto and
what parts are OE.
Right, I know it's
Hi Andrea and all,
So I am using your suggestion to make another variant of busybox:
busybox-static, and I add the static.bblcass file.
So when I try to do bitbake busybox-static, it ends up unpacking to
busybox-static-1.20.2-r2/busybox-1.20.2 (which does not correspond to
the S variable).
Just add my few cents of using Yocto.
Since yocto is tailored towards embedded system, normally it includes
light weight (strip-down version/flavor) software and servers, such as
sysklogd instead of syslogd and busybox cron instead of crond.
Which is not a bad thing at all, as this make sure
All,
We usually want to block shell access for the product that we release,
but want to have a way to log in for debugging and troubleshoot.
I want to ask how other developers are doing this.
So two main questions:
1. how to change the default password of root?
2. how to block shell access
On 17 June 2014 21:23, Insop Song insop.s...@gmail.com wrote:
2. how to block shell access but to open for debugging access
For this, I could think of that we could block ssh access and only open
console.
Or opening ssh for a hidden port only.
The Raumfeld multi-room audio system has a neat
On 14-06-12 02:32 AM, rebecca.swee.fun.ch...@intel.com wrote:
From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
Hi Bruce and all,
This patchset is for rebasing the valleyisland-io-1.0 feature branch.
I recently received a notification from Greg that the Baytrail SMBUS
back-porting
From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
Hi all,
Valley Island I/O feature branch was recently rebased to new
version and I would like to push this patch into meta branch
so that we can merge the new feature branch with standard/base.
This patch is about updating the scc
From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
Valley Island feature branch was rebased recently and its
scc file need update in order to merge new feature branch,
valleyisland-io-2.0.
Signed-off-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
---
26 matches
Mail list logo
