Date   

Re: Remove a recipe's do_install_append() function in an append file

Khem Raj
 

On Thu, Mar 23, 2017 at 3:28 PM, Cody Piersall <cody@...> wrote:
Hello,

I am building zsh from meta-oe layer, and it has a do_install_append()
function defined like this:

do_install_append () {
rm -fr ${D}/usr/share
}

which gets rid of lots lots of useful functionality, like
context-aware autocompletion. Can a bbappend file get rid of that
function, or do I need to edit the actual recipe? I've attempted
defining an empty do_install_append() { : } but it didn't work.
if its in a bbappend, there is not much you can do about undoing it except
to not apply the bbappend or modify it directly.

So you can send a patch to meta-oe to convince that its a good idea to keep
/usr/share for zsh, or you can carry a local patch to meta-oe where you undo it


Thanks,
Cody
--
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: how to enable c++11 support in yocto

Burton, Ross <ross.burton@...>
 


On 27 March 2017 at 05:58, Vadalasetti Sivanageswararao <vsivanagulu@...> wrote:
cc1plus: warning: include location "/usr/local/include" is unsafe for cross-compilation [-Wpoison-system-directories]

Your build is referring to host files so this is likely the problem.  This is a bug in your sources, or recipe.

Ross


Re: Remove a recipe's do_install_append() function in an append file

Matthew McClintock
 

On Thu, Mar 23, 2017 at 5:28 PM, Cody Piersall <cody@...> wrote:
Hello,

I am building zsh from meta-oe layer, and it has a do_install_append()
function defined like this:

do_install_append () {
rm -fr ${D}/usr/share
}

which gets rid of lots lots of useful functionality, like
context-aware autocompletion. Can a bbappend file get rid of that
function, or do I need to edit the actual recipe? I've attempted
defining an empty do_install_append() { : } but it didn't work.
We hit this sometime so curious if anyone has better suggestions. But
you can add a do_install_prepend to save the data somewhere, and an
append to put it back. Also, you can use the priority of your layer
could come into play here.

-M


Re: Questions

Hofemeier, Ulf <ulf.hofemeier@...>
 

Hi Arun,

 

You need to add poky manager support to Poky and install it by adding the following line to your build/conf/local.conf file.

 

https://wiki.yoctoproject.org/wiki/How_do_I

 

For the conf/local.conf entry please add this: IMAGE_INSTALL_append = " package"

 

After that you have to bitbake a new image that contains your package.


Thanks,

Ulf

 

From: <yocto-bounces@...> on behalf of Arun Maha <2233arunkumar@...>
Date: Tuesday, March 28, 2017 at 2:14 AM
To: "yocto@..." <yocto@...>
Subject: [yocto] Questions

 

Hi,

How to install a command (pmount) in poky distribution. What are the steps to follow?

 

Thanks,

ARUNKUMAR K


Re: Unpack hierarchy - jethro vs. krogoth

Colin Helliwell <colin.helliwell@...>
 

On 28 March 2017 at 11:33 colin.helliwell@... wrote:

Is there a change to recipe parsing and/or variables between jethro and
krogoth?
I'm migrating from the former to the latter and have hit a patch failure.
Looking at the unpacked source, jethro has the relevant file at
build/tmp/work/XXX-poky-linux-gnueabi/linmux/3.0.2-r0/driver/
whereas krogoth has it at
build/tmp/work/XXX-poky-linux-gnueabi/linmux/3.0.2-r0/driver/driver/

Indeed, all the sources have been unpacked under an additional 'driver'
directory level .e.g.
src/driver/* -> 3.0.2-r0/driver/driver/
src/config/* -> 3.0.2-r0/driver/config/
instead of
src/driver/* -> 3.0.2-r0/driver/
src/config/* -> 3.0.2-r0/config/

The recipe includes
SRC_URI = "file://driver/*.c \
file://driver/*.h \
file://Makefile \
file://COPYING \
"
FILESEXTRAPATHS_prepend := "${BSPDIR}/../Apps/MyDriver/src:"
S = "${WORKDIR}"

As I say, it works on jethro...!
Can't spot a reason, even in the bbclass's, why it's unpacking differently.
log.do_unpack reports:
DEBUG: Searching for driver/*.c in paths:
....
DEBUG: Searching for driver/*.c in path: /home/colin/100051-krogoth/fsl-community-bsp/../Apps/MyDriver/src/.
NOTE: Unpacking /home/colin/100051-krogoth/fsl-community-bsp/../Apps/MyDriver/src/. to /home/colin/100051-krogoth/fsl-community-bsp/build/tmp/work/wg2xx_tx6s-poky-linux-gnueabi/linmux/3.0.2-r0/

which suggests it should've ended up in the 'right' place?


Re: Current situation with gobject introspection? (off-topic)

Mike Looijmans
 

On 28-03-17 10:39, Burton, Ross wrote:

Krogoth (2.1) isn't the latest, that's Morty (2.2) released in October 2016
and next month Pyro (2.3) is being released.
So what happened to the missing two walker bots?

:-)



Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@...
Website: www.topicproducts.com

Please consider the environment before printing this e-mail


Re: Copying Static library to libdir of YOCTO

Burton, Ross <ross.burton@...>
 


On 28 March 2017 at 12:02, Surya <surya.n@...> wrote:
I can see those libraries in the  "usr/lib" directory of that particular package which is generated in "tmp/work" folder . But somehow these libraries are not copied to rootfs "/usr/lib" directory.

Static libraries are part of the ${PN}-staticdev package, so won't be installed if you just install the ${PN}-dev package.

Ross


host sysroot

Ran Shalit <ranshalit@...>
 

Hello,

I am trying to understand what's the purpose of host sysroot (in
/build/tmp/sysroots/) ?
I see it contains a set of libraries too. But for cross compiling an
application in host isn't all we need is toolchain and target sysroot
? If so, than what's the purpose of host sysroot ?

Thank you,
Ran


Re: package managers

Ran Shalit <ranshalit@...>
 

On Tue, Mar 28, 2017 at 1:25 PM, Burton, Ross <ross.burton@...> wrote:

On 28 March 2017 at 11:00, Ran Shalit <ranshalit@...> wrote:

I understand from this that in target it will be possible to install a
package, using the other package manager.

Why would you want to do this?

You'll need to install the package management tooling, and the database of
the one you install after the rootfs creation won't know about anything that
is already in the rootfs.

It's a lot easier to just pick a package manager and use it consistently.
Ok, Thank you !

Ross


Copying Static library to libdir of YOCTO

Surya <surya.n@...>
 

Hello ,

I am facing some issues , when trying to copy static libraries like libaccess.a & liblang.a to ${libdir} of rootfs.

I can see those libraries in the "usr/lib" directory of that particular package which is generated in "tmp/work" folder . But somehow these libraries are not copied to rootfs "/usr/lib" directory.

I am using below instructions:

install -d ${D}${libdir}/
install -m 0755 ${S}/accesslib_new/libaccess.a ${D}${libdir}

install -d ${D}${libdir}/
install -m 0755 ${S}/WebServices_LanguageLibrary/liblang.a ${D}${libdir}


Any suggestion...


Thanks & regards
Surya


Unpack hierarchy - jethro vs. krogoth

colin.helliwell@...
 

Is there a change to recipe parsing and/or variables between jethro and
krogoth?
I'm migrating from the former to the latter and have hit a patch failure.
Looking at the unpacked source, jethro has the relevant file at
build/tmp/work/XXX-poky-linux-gnueabi/linmux/3.0.2-r0/driver/
whereas krogoth has it at
build/tmp/work/XXX-poky-linux-gnueabi/linmux/3.0.2-r0/driver/driver/

Indeed, all the sources have been unpacked under an additional 'driver'
directory level .e.g.
src/driver/* -> 3.0.2-r0/driver/driver/
src/config/* -> 3.0.2-r0/driver/config/
instead of
src/driver/* -> 3.0.2-r0/driver/
src/config/* -> 3.0.2-r0/config/


The recipe includes
SRC_URI = "file://driver/*.c \
file://driver/*.h \
file://Makefile \
file://COPYING \
"
FILESEXTRAPATHS_prepend := "${BSPDIR}/../Apps/MyDriver/src:"
S = "${WORKDIR}"

As I say, it works on jethro...!


Re: package managers

Burton, Ross <ross.burton@...>
 


On 28 March 2017 at 11:00, Ran Shalit <ranshalit@...> wrote:
I understand from this that in target it will be possible to install a
package, using the other package manager.

Why would you want to do this?

You'll need to install the package management tooling, and the database of the one you install after the rootfs creation won't know about anything that is already in the rootfs.

It's a lot easier to just pick a package manager and use it consistently.

Ross


Re: package managers

Ran Shalit <ranshalit@...>
 

On Tue, Mar 28, 2017 at 12:21 PM, Burton, Ross <ross.burton@...> wrote:

On 28 March 2017 at 10:09, Ran Shalit <ranshalit@...> wrote:

Is it possible to configure more than one package manager in yocto ?
Does it mean it will create install package for both ?

This is explained in the documentation:

http://www.yoctoproject.org/docs/2.2.1/ref-manual/ref-manual.html#var-PACKAGE_CLASSES

Ross
Hi,
Thanks a lot for the reference.

It is said: "The build system uses only the first argument in the list
as the package manager when creating your image or SDK. However,
packages will be created using any additional packaging classes you
specify"

I understand from this that in target it will be possible to install a
package, using the other package manager.

Regards,
Ran


multiple, different kernel images in one rootfs

Richard Leitner
 

Hi,
I'm currently using Jethro and like to include multiple, different
kernel (fit)images (with different source branches/versions) in one
RootFS. When booting such a system the bootloader (U-Boot) will decide
which kernel to load.

I've already done some searches on the Internet, but found only Bug
6945, which seems to be something similar. But I'm unable to find any
documentation on it, and the commits linked to the bugzilla [1] aren't
very helpful.

Furthermore a similar question on the mailing list in 2015 [2] wasn't
answered.

So does anybody of you know how to implement that or where/how I might
get started?

Thanks & regards,
Richard L

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=6945
[2] https://lists.yoctoproject.org/pipermail/yocto/2015-May/025031.html


Re: package managers

Burton, Ross <ross.burton@...>
 


On 28 March 2017 at 10:09, Ran Shalit <ranshalit@...> wrote:
Is it possible to configure more than one package manager in yocto ?
Does it mean it will create install package for both ?

This is explained in the documentation:

Ross


Questions

Arun Maha <2233arunkumar@...>
 

Hi,
How to install a command (pmount) in poky distribution. What are the steps to follow?

Thanks,
ARUNKUMAR K


package managers

Ran Shalit <ranshalit@...>
 

Hello,

Is it possible to configure more than one package manager in yocto ?
Does it mean it will create install package for both ?

Thank you,
Ran


Re: Current situation with gobject introspection?

Colin Helliwell <colin.helliwell@...>
 

On 28 March 2017 at 09:39 "Burton, Ross" <ross.burton@...> wrote:

On 28 March 2017 at 09:05, <colin.helliwell@...> wrote:

So I wondered what the latest [krogoth] situation is – am I likely to be able to get this package to build, and where/how might I get started?
Krogoth (2.1) isn't the latest, that's Morty (2.2) released in October 2016 and next month Pyro (2.3) is being released.
Yeah, sorry - I meant 'the latest situation w.r.t Krogoth', rather than Krogoth being the latest version :)

Krogoth has support for gobject-introspection, and is covered in the documentation:

http://www.yoctoproject.org/docs/2.2.1/dev-manual/dev-manual.html#enabling-gobject-introspection-support
Thanks guys, I'll get moved over to Krogoth and take it from there.


Re: Current situation with gobject introspection?

Jussi Kukkonen <jussi.kukkonen@...>
 

On 28 March 2017 at 11:05, <colin.helliwell@...> wrote:
>
> I’m currently using Jethro (though about to move to Krogoth), and have an external package which need gobject introspection. I’m building on 64-bit x86, for ARM iMX6 target.
>
> I’ve been searching around to work out if this is possible under Yocto, but not sure which of the info I’ve found is up-to-date.
>
> So I wondered what the latest [krogoth] situation is – am I likely to be able to get this package to build, and where/how might I get started?
>
> Thanks

Hi Colin,

Alexander can give you the gory details if needed but the summary is: Krogoth has full gobject-introspection support (for architectures that qemu supports), jethro does not.

There is a distro feature but it is backfilled by default so no action should be needed. For many libraries you only need to inherit the class, but do read the fine manual just in case: http://www.yoctoproject.org/docs/2.1/dev-manual/dev-manual.html#enabling-gobject-introspection-support
 
Jussi


Re: Current situation with gobject introspection?

Burton, Ross <ross.burton@...>
 


On 28 March 2017 at 09:05, <colin.helliwell@...> wrote:

So I wondered what the latest [krogoth] situation is – am I likely to be able to get this package to build, and where/how might I get started?


Krogoth (2.1) isn't the latest, that's Morty (2.2) released in October 2016 and next month Pyro (2.3) is being released.

Krogoth has support for gobject-introspection, and is covered in the documentation:


Ross