[meta-xilinx] Busybox options on 2016.2 meta-xilinx/meta-petalinux

[Oleg K Dzhimiev]

Hi,

"${@plnx_enable_busybox_package('dos2unix',d)}" should output
"busybox-dos2unix".
So, you probably need to include the package "busybox-dos2unix" to your
rootfs image.

To make sure the binaries are in that package - they should be in the
busybox's workdir/packages-split/busybox-dos2unix/...

Regards,
Oleg

On Fri, Jan 12, 2018 at 2:37 PM, <kfoote at prairiepointdesign.com> wrote:

> Hello,
>
>
>
> I have a question about Busybox as it pertains to meta-petalinux layer /
> meta layer in the Xilinx/Yocto 2016.2 code.
>
>
>
> I am using Petalinux 2016.2, and I have downloaded the Yocto source for
> this as per
>
>
>
> http://www.wiki.xilinx.com/Getting+Started+With+Yocto+
> using+Repo+to+build+RPM+Packages
>
>
>
> I’m trying to build packages to use for the package feed for my Petalinux
> roofs.  To this point, I’ve built a couple of new packages (pax, tcpdump,
> nodejs) and I have been able to pull them into my rootfs in Petalinux.  I
> see them in the rootfs configuration and have enabled them.
>
>
>
> But now I need to turn on an additional feature in busybox and I am
> struggling.  I do not seem to be able to change any options with the
> busybox located in the Petalinux 2016.2 tools, so I am trying to enable
> this in the Yocto source and hoping to pull in that package to use.
>
>
>
> However, I am specifically having trouble enabling dos2unix in busybox for
> the Xilinx/Yocto 2016.2 release.  It seems that whatever I do, during the
> do_compile stage of busybox building, I see this snippet in the logs:
>
>
>
> redefined by fragment .config.disable.apps:
>
>
>
> and even when I have (via menuconfig) previously set dos2unix to y, both
> dos2unix and unix2dos are being unset and are not available in the rootfs
> after it is built.
>
>
>
> Can anyone list the steps that I should be doing in order to enable a new
> function in Coreutils in Busybox, as it appears to be more involved than
> just using menuconfig and / or the steps below.
>
>
>
> Here are the things I have tried in addition to “bitbake -c menuconfig
> busybox; bitbake busybox; bitbake petalinux-image”:
>
>
>
> Adding a .cfg file with CONFIG_DOS2UNIX and CONFIG_UNIX2DOS both set to
> =y, this .cfg file is included in a SRC_URI_append in a .bbappend file in
> the meta-petaliux layer.  This file does show up in the work directory
> after I build, so it seems it is being included.
>
>
>
> In the meta-petalinux layer, I have added the following lines to
> busybox_%1.bbappend:
>
> PACKAGES =+ "${@plnx_enable_busybox_package('dos2unix', d)}"
>
> INITSCRIPT_PACKAGES =+ "${@plnx_enable_busybox_package('dos2unix', d)}"
>
>
>
> INITSCRIPT_NAME_${PN}-dos2unix = "dos2unix.${PN}"
>
> INITSCRIPT_PARAMS_${PN}-dos2unix = "start 67 S ."
>
>
>
> And at the end of
>
> def plnx_features_to_busybox_settings(d):
>
>     pkgfeatures = {
>
>
>
> I have added:
>
>         "busybox-dos2unix" : [
>
>             "CONFIG_DOS2UNIX", \
>
>             "CONFIG_UNIX2DOS", \
>
>         ],
>
>
>
>
>
> But it isn’t working.  Busybox builds, but still no dos2unix.
>
>
>
> I must be doing something wrong, or missing a step somewhere, so any help
> or point out another example to look at is much appreciated!
>
>
>
> Thanks,
>
> Katie
>
> --
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180112/7f4d2bab/attachment.html>