t; acceptable method is to have a simple way of ensuring that a certain
> file is converted to that symlink.
This is normally done by a manual inspection / addition of bbappend
file.
Cheers,
Anders
--
Anders Darander, Senior System Archite
ng up the demo). I ran "bitbake -c populate_sdk test-image"
> and I expected the file usr/lib/test-lib to be present in the SDK, but
> it is not.
Ah, a small test example? Perfect!
Could you add it the bug above? It would likely make it easier to debug.
Cheers
Anders
--
Anders Darander,
ject.org <mailto:yocto@yoctoproject.org>
> > > https://lists.yoctoproject.org/listinfo/yocto
> > <https://lists.yoctoproject.org/listinfo/yocto>
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/yocto
> > <https://lists.yoctoproject.org/listinfo/yocto>
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
* Riko [170815 07:42]:
> Do you mean this one ?
Yes.
> Build Configuration:
> BB_VERSION= "1.34.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE = "beaglebone"
> DISTRO= "poky"
> DIST
required static libraries in the image
> before building SDK - eg: for glibc static development libraries:
> IMAGE_INSTALL_append = " glibc-staticdev"
Why install it to the image?
TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"
would be better, as it'll only
quire a few smaller python applications.
You'd be welcome to suggest that people try to install the complete
pyhton(3)-modules package, as that makes it easier for everyone with
large eMMC's and SD-cards, though.
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm A
dk/ to install the
> sdk, I can see that the library is not installed in the sdk sysroot. The
> header is there, but the static library is not.
> I also tried adding this to local.conf:
> EXTRA_IMAGE_FEATURES += "staticdev-pkgs"
> but that also didn't insta
d read "machine.conf"? because i have no
> idea what "bsp_name.conf" refers to as it is.
Yes, that's the machine.conf...
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
I changed my [task] dependencies to match what you've quoted and everything
> works as before. !Thanks!
I'd still recommend doing as little as possible in each recipe, and
leverage the standard modules.
Cheers,
Anders
--
Anders Darander, Senior System Architect
Char
gt; {YOCTO_BUILD_DIR}//tmp//deploy/image/{TARGET}/*rootfs.tar.bz2 to the export
> dir
> - takes additional time.. Not good.
This is the right way to do it.
If it takes to much time, create a script that runs bitbake and then
untars the rootfs.
Cheers,
Anders
--
Anders Darander, Seni
I want that
> the generated data should be in ${S}.
> Is there a way to tell do_configure to use ${S} and not ${WORKDIR}/build.
Sure set
B = "${S}"
Though, I'd rather suggest trying to get the library to build
out-of-tree. If you can get that going, it'll be better
d:
> pkg_postinst_AAA() {} - OK
> pkg_postinst_AAA_append() {} - OK
> pkg_postinst_BBB() {} - NG
> pkg_postinst_BBB_append() {} - NG
A recipe can't influence another recipe, thus this isn't going to work.
However, a single recipe can build multiple packages, eg AAA and
AAA-fo
y platform developers will 'git clone'
my_git_repo/yocto_git/... <-- yocto framework
my_git_repo/meta-openembedded
Well, I'm using bitbake and openembedded-core repos directly instead of
yocto, but that doesn't really matter.
Cheers,
Anders
--
Anders Darander, Senior S
I'm pretty sure that this is the point Philip was after, that it really
doesn't make sense for Poky.
LTS branches in oe-core and bitbake, OTOH, makes sense, and would be
appreciated by quite some.
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB /
. stop 01 0 1 6 ."
> INITSCRIPT_NAME = "can_if"
> CONFFILES_${PN} += "${sysconfdir}/init.d/can_if"
If this is the complete recipe, you never install can_if...
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Fri, 26 Feb 2016, 03:54 Khem Raj wrote:
> Go ahead
>
Yes, go ahead.
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ccount.
>
Yes, that's right.
If the rest of the patches in that series is non-controversial, could we
have them applied? Otherwise, could we have Khem's patch applied, and
the other series rebased upon that?
We've had the master branch non-building for quite a while now..
_OUTPUT}
> +${STAGING_DIR_NATIVE}${libexecdir}/mkknlimg --dtok
> ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}
> fi
> fi
> }
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
If we have a machine specific defconfig 'defconfig' in our meta-data, the
install
command fails. OTOH, in that case it's not necessary to copy it into twe WORKDIR
either.
Signed-off-by: Anders Darander
---
recipes-kernel/linux/linux-raspberrypi.inc | 4 +++-
1 file changed, 3 i
* Andy Hung(洪翊桓_Pegatron) [151202 10:49]:
> Hi Anders,
> Thanks for your help, pls see updates below,
> > Message: 2
> > Date: Tue, 24 Nov 2015 14:25:14 +0100
> > From: Anders Darander
> > To: yocto@yoctoproject.org
> > Subject: Re: [yocto] Header files in /
* Andy Hung(洪翊桓_Pegatron) [151125 11:53]:
> Message: 2
> Date: Tue, 24 Nov 2015 14:25:14 +0100
> From: Anders Darander
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] Header files in /usr/include of rootfs
> Message-ID: <20151124132514.gb2...@ad.chargestorm.se>
&g
ave a dependency on the kernel
headers? Do you have anything in your IMAGE_FEATURES?
> Why are there .debug in the package folder, it should only be in package –dbg
> folder, right?
Where are the .debug directories located? You should add them to:
FILES_${PN}-dbg += "/.debug"
Che
ith read-only root file
> systems? Anybody here who did something similar?
Well, it depends.
For consistency, I'm in the camp that prefers to do image-based
upgrades. I.e. rewrite the whole rootfs; though that normallly requires
that you're either switching between two alternativ
on used for normal operation.
How flexible to you intend to make this system? Allow everything that
swupdate supports? Or a specific subset?
Cheers,
Anders
--
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
* Andre McCurdy [151103 11:34]:
> On Mon, Nov 2, 2015 at 11:05 PM, Anders Darander
> wrote:
> > * Andre McCurdy [151102 20:35]:
> >> See the "IMAGE_TYPES" variable for a list of rootfs types which are
> >> supported. There's support for creatin
fs.
No, avoid doing this. The reasons are the same as why you shouldn't
unpack the tarball using a new image type; you're not allowed to set the
correct owner, group, and permissions on files, nor are you allowed to
create device nodes.
Cheers,
Anders
--
Anders Darander
ChargeStorm A
ook at that line, you'll find the following link:
http://www.openembedded.org/wiki/Bitbake_World_Status_Setup, which
basically tells you what the world status builds are doing.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
opbear" *in image recipe*.*
> Can i able to change dropbear.service file before creating final image.
Sure, add a bbappend-file in your layer, and add your own versions of
those two service-files in your layer.
Cheers,
Anders
--
Anders Darander
C
everyone unacceptable pain.
It's going to give a lot of us a huge support nightmare again...
If the checksums can be guaranteed to be stable, then, yes, such a
change can be looked upon.
Shallow clones is in this case a lot more likely to be usefull, though,
implementing that might have
installed the files under /opt, though there's nothing that
tells the system in which package these files should be installed.
Add a line:
FILES_${PN} += "/opt/we_remote"
to your recipe. This should tell the packaging step that all files under
/op
Thinking of temporary network issues
together with something stalling).
> Can anyone point me in the right direction?
Just a couple of questions.
Does the log.do_fetch reveal anything?
If you enable the debug flags for bitbake, do you get anything that
makes sense when re-running the fetch task
it's
> a strictly embedded installation.
That shouldn't really matter, I'm running systemd in headless setups.
I'd guess that you're getting some errors earlier than this in the
bootlog? Could you paste them?
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 17 Apr 2015 16:30, "Paul Eggleton" wrote:
>
> I have sent an additional patch to the bitbake list to try to protect
against
> future instances of this issue, at least for bb.utils.prunedir() and
> bb.utils.remove():
>
>
http://lists.openembedded.org/pipermail/bitbake-devel/2015-April/005664.htm
> source directory.
Unless the buildprocess heavily modifies the config file, I wouldn't
create a patch to patch it in the source tree. I'd rather just add the
complete config file to FILES +=... and then replace the one from the
source package with my copy in a do_install_appen()
""
def_destsuffix = "git/"
---
Probably, the first issue could be solved by replacing subdir with
subdir.strip('/') on the line above that.
Though I might be missing something...
I've only looked for a moment on the patch above,
erces-c/3.1.1-r0/xerces-c-3.1.1/src/xe
> and so on
Well, xervces is installing lots of files to /usr/src/debug... So you
have to choices:
1) Remove those files. Add a do_install_append where you're running
`rm -rf ${D}/usr/src`
2) Package those file in either one of the curr
Hi,
* Barros Pena, Belen [150331 18:00]:
> On 31/03/2015 10:39, "Anders Darander" wrote:
> >I don't know if this is the right thread but a couple of other things
> >that we really would need in order to fully be able to utilize this.
> >1) Some way of g
dle
toaster/build logs from different YP releases? Normally we've at least
one active release branch, and possibly a master (or master-next) branch
that's going to the next YP release. If possible, I'd like to visualize
all this in the same Toaster instance.
Apart from that, I th
kg2 = "..."
etc
points to which files you want packaged in which package.
> 3. Also avoid calling do_compile() as there is no makefile its plain
> file repo which need to be packaged.
Just create an empty do_compile(). Or you could remove do_package() from
the task list for this re
{sbindir}/.debug \
> > ${libexecdir}/.debug \
> > ${libdir}/.debug \
> > /bin/.debug \
> > /sbin/.debug \
> > /lib/.debug \
> > ${libdir}/${PN}/.debug"
> > But I am not getting how the source for such file will be determine a
https:// URL should
look like https://git.yoctoproject.org/git/poky/...
When `repo sync` works for me, I'm still getting the git:// URLs.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
n't. i'm sure no one is terribly worried about that particular
> script, but it does seem to show an example of this.
But that's checking *recipe* names, not layer names...
Thus, you'll have to look for another example. ;)
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
res today.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
* matthias.he...@atlas-elektronik.com
[141210 11:48]:
> > -Ursprüngliche Nachricht-
> > Von: Anders Darander [mailto:and...@chargestorm.se]
> > Gesendet: Mittwoch, 10. Dezember 2014 11:24
> > An: Heise, Matthias
> > Cc: j...@spectralogic.com; yocto@yo
d directory.
Thus, you really should be using the tarball when you want to run an
nfsroot.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
looking at this issue next week, though any pointer
that will help me will be much appreciated.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
* Matt Schuckmann [141126 18:22]:
> Yes you are correct I want a small number of files into to reside in a
> writeable partition with links in the root file system to point to
> them. I guess I latched on to the volatiles mechanism because it seems
> close to meeting my needs.
The volatile-binds
On 25 November 2014 17:13:17 CET, "peterengcomau...@adam.com.au"
wrote:
>My original problem is that the image built in 1.6.1 does not build in
>1.7. Paul indicated this is probably because of the -foreign issue as
>referred to in the reference manual Section 5.6.3 when upgrading.
>
>
>What I
t;Creating patches with diff"
section on http://jungels.net/articles/diff-patch-ten-minutes.html.
If you think you might need to add multiple patches, rework them etc.
I'd recommend using git.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
__
b64 or
something else, especially in a multilib-build. However, the firmware
files are always searched for in /lib/firmware.
Cheers,
Anders
> do_install() {
> install -d ${D}/${libdir}/firmware/zd1211
> install -m 0555 ${WORKDIR}/zd1211_*${D}/${libdir}/firmware/zd1211/
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
eck out the volatile-binds
recipe in oe-core.
Otherwise, check out https://github.com/MentorEmbedded/meta-ro-rootfs,
which is were volatile-binds originates from.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto ma
CKAGES that can grab a file will do that...
Hopefully this will help you...
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
_append's will just be appended one after
each other.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
but also inside that expression. Try to change " to '.
You should also use bitbake -e to check that EXTRA_OECONF
looks OK.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
> and it worked in this example, however, our internal enterprise github only
> supports http and ssh URIs.
No, the protocol is specified by adding protocol=xxx.
> SRC_URI =
> "git://github.com/GraphicsEmpire/gridvisualization.git;branch=master”
Cheers,
Anders
--
Anders Darand
to create a standard bitbake recipe and just install those files into
the rootfs.
If it's something else, I think you need to explain it a little bit
more.
Cheers,
Anders
> Any suggestions?
--
Anders Darander
ChargeStorm AB / eStorm AB
--
__
Though, this should
likely have been handled by
inherit python3native
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
conf.
The image.bb file is far to late to change the distro configuration.
The better, long term solution would be to define your own distro. Which
really isn't that hard.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
--
___
* Hans Beckérus [140121 13:12]:
> On Tue, Jan 21, 2014 at 12:10 PM, Hans Beckérus
> wrote:
> > On Tue, Jan 21, 2014 at 11:23 AM, Anders Darander
> > wrote:
> >> * Hans Beckérus [140121 11:05]:
> >>> Things looked ok for a while, /dev was populated prop
ould be fine.
Regarding your other questions on mdev, it's been a little while since I
used mdev. Let us know if the ideas above is enough, or if you want to
dig more into mdev.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
_
Jack wrote:
>Anders Darander writes:
>
>Thanks Anders,
>
>But I have this problem not only for GPIOs, but also for other
>registers.
Well, my comment about dereferencing physical addresses using *-only, wasn't
restricted to GPIO's only. It was regarding p
7e0060
>faulting instruction address: 0xf107e05c
>Oops: Kernel access of bad area, sig: 11 [#1]
>..
>.
>
>
>How can I solve this problem?
>
>
>___
>yocto mailing list
>yocto@yoctop
you might have configured.
I won't be able to run any tests on my own until early next week. If necessary,
I hope that someone else might be able to help you until then.
Cheers,
Anders
>
>This is taken from build confriguation.
>
>
>Thanks
>
>Amit.
>
>
&
-gnueabi/openssh/6.1p1-r3/packages-split,
do you see openssh-sftp there, or which packages do you have there?
Which version of Yocto / Poky are you using? What layers do you have enabled?
Cheers,
Anders
>Thanks
>
>Amit
>
>
>
>
>
>On Tue, Oct 1, 2013 at 6:56 PM,
t it??
It's already being installed to a package named openssh-sftp. Thus, it
should be enough to add openssh-sftp to your image.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Paul Eggleton wrote:
>On Wednesday 18 September 2013 10:47:56 Anders Darander wrote:
>> * Brad Litterell [130917 21:20]:
>> > I have a number of QT components that have qmake style .pro files.
>> >
>> > In my recipe I inherit both externalsrc & qmak
"
You shouldn't need to use :=, I was required to do that as I needed to
use THISDIR (and thus I need the expansion to occur immediately).
Just setting S wasn't enough for me, I needed to also define B. Note,
though, that this means that you can't build your recipe for
Time flies fast, and the travel schedules for fall will likely need to
be set soon...
Are there any plans for a YP Dev.Day in Edinburgh, and if so, any dates
set?
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
do using the useradd class. See
http://cgit.openembedded.org/openembedded-core/tree/meta-skeleton/recipes-skeleton/useradd/useradd-example.bb
for more info
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yo
in a .bbappend
for the kernel recipe in question.
> But neither worked.
That should make it work.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
versions have been upgraded in either OE-Core or
meta-oe. Thus, you need to update the bbappends in meta-gumstix to match the
current versions.
Cheers,
Anders
>
>i hope i am not annoying you. Thank You for your time and patience.
--
Anders Darander
ChargeStorm AB Tel: +46 702
"Hans Beckérus" wrote:
>On Mon, Apr 22, 2013 at 9:47 AM, Anders Darander
> wrote:
>> Hi,
>>
>> "Hans Beckérus" wrote:
>>
>>>Hello. I wish to bring in gnupg to our system but from what I can
>tell
>>>gnupg is not part
t.
Cheers,
Anders
>Hans
>___
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
--
Anders Darander
ChargeStorm AB Tel: +46 702 44 84 36
Laxholmstorget 3 Email: and...@chargestorm.se
602
t
interested in. All the supplied images are there for some use-case, be
it demoing stuff, test, etc.
If you want to customize an image more, I'd recommend you to create your
own image. A first step might be to just copy one of the image recipes
to a layer of your own, and then modify it
r won't cause the added recipes to be built and
deployed.
If you have added samba to the image, could you share the image recipe
and build logs?
Can you build samba manually? (Calling bitbake samba, (though I don't
know if that's the correct name, as I haven't check the meta-oe-la
creation, to allow for images like this by setting some extra flag
or EXTRA_IMAGE_FEATURE...
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
enzil was very convenient.
Indeed, and also to be able to create a next branch halfway between
denzil and danny, to be able to port / adapt some recipe that required
bigger changes at about the same time those occured in poky-master (or
oe-core master).
Thus, I'm pretty satisfied with our struc
Will the GA start at 17:00, or shouldn't we start it after the closing session
finishes?
Cheers,
Anders
Philip Balister wrote:
Non-members are welcome to come to the meeting. If you are interested in
becoming a member of the eV
(http://www.openembedded.org/wiki/Organization), talk to a member
> IMAGE_PREPROCESS_COMMAND += "echo "${@print_layers_version(d)}" > /
> ${IMAGE_ROOTFS}/etc/build; "
Ah, nice solution!
That might be something to add to my own /etc/build. You can never get
too much info if some issues tur
ll give me
all info I need.
Cheers,
Anders
> Regards,
> Marc
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Anders Darander
ChargeStorm AB / eStorm AB
__
Engineer - Yocto Project
> >> Intel Open Source Technology Center
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> >
> >
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Anders Darander
ChargeStorm AB / eStorm AB
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
* Paul Eggleton [08 17:23]:
> On Monday 07 November 2011 10:18:51 Anders Darander wrote:
> > We have found a problem with upgrading packages on our own image.
> > (Hopefully it'll show up to an error from our side).
> > After upgrading system packages, like bus
more alternatives
exist for it
update-alternatives: removing //usr/bin/xz as no more alternatives exist
for it
update-alternatives: removing //usr/bin/yes as no more alternatives
exist for it
update-alternatives: removing //bin/zcat as no more alte
83 matches
Mail list logo
