select installation packages

select installation packages

[Andre Bella]

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

Hello 
 I had used buildroot in the pass and I like it cause is very easy to use, but I'm moving to yocto cause it has more applications than buildroot, in buildroot you can select the packages you want to add by going to menuconfig, how do I select the packages I wan to add in yocto, for example if I wan to add nano or gstreamer, from the guide I seen you just type bitbake -b nano, but is there a menuconfig on yocto where you can select the package you want to add before you build the image?
thanks,

[-- Attachment #2: Type: text/html, Size: 635 bytes --]

Re: select installation packages

[Rudolf Streif]

[-- Attachment #1.1: Type: text/plain, Size: 1625 bytes --]

Hi Andre,

There actually is no recipe for building the nano editor in YP by default.
Unless you added one,

bitbake -b nano

would result in this output

ERROR: Unable to find any recipe file matching 'nano'

I have attached a recipe for you to build nano and a patch to handle a
configuration mistake configure.ac causing do_configure to fail.

If you add that recipe you can run bitbake nano. You can also include into
your image by adding

IMAGE_INSTALL_append = " nano"

to your conf/local.conf file.

:rjs



On Thu, Feb 14, 2013 at 8:02 AM, Andre Bella <scancool@yahoo.com> wrote:

> Hello
>  I had used buildroot in the pass and I like it cause is very easy to use,
> but I'm moving to yocto cause it has more applications than buildroot, in
> buildroot you can select the packages you want to add by going to
> menuconfig, how do I select the packages I wan to add in yocto, for example
> if I wan to add nano or gstreamer, from the guide I seen you just type
> bitbake -b nano, but is there a menuconfig on yocto where you can select
> the package you want to add before you build the image?
> thanks,
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
-- 
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation

rudolf.streif@linux.com
Phone: +1.619.631.5383
Skype: rudolfstreif
PGP: RSA 2048/2048 D6E7D28B

Linux Foundation Events Schedule:  events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org

[-- Attachment #1.2: Type: text/html, Size: 3718 bytes --]

[-- Attachment #2: nano_2.3.1.bb --]
[-- Type: application/octet-stream, Size: 1181 bytes --]

SUMMARY = "GNU nano - an enhanced clone of the Pico text editor"

DESCRIPTION = "GNU nano - an enhanced clone of the Pico text editor"

AUTHOR = "Chris Allegretta <chris@asty.org>, \
David Lawrence Ramsey <pooka109@gmail.com>, \
Jordi Mallach <jordi@gnu.org>, \
Adam Rogoyski <rogoyski@cs.utexas.edu>, \
Robert Siembarski <rjs@andrew.cmu.edu>, \
Rocco Corsi <rocco.corsi@sympatico.ca>, \
David Benbennick <dbenbenn@math.cornell.edu>, \
Mike Frysinger <vapier@gentoo.org>"

HOMEPAGE = "http://www.nano-editor.org"
BUGTRACKER = "https://savannah.gnu.org/bugs/?group=nano"

SECTION = "console/utils"
PRIORITY = "optional"

PROVIDES += "editor/nano"

LICENSE = "Nano GPLv3"
LIC_FILES_CHKSUM = "file://COPYING;md5=f27defe1e96c2e1ecd4e0c9be8967949"

DEPENDS = "ncurses"
PR = "r0"

PV_MAJOR = "${@bb.data.getVar('PV',d,1).split('.')[0]}.${@bb.data.getVar('PV',d,1).split('.')[1]}"

SRC_URI = "http://www.nano-editor.org/dist/v${PV_MAJOR}/nano-${PV}.tar.gz \
           file://ncursesw.patch"
SRC_URI[md5sum] = "af09f8828744b0ea0808d6c19a2b4bfd"
SRC_URI[sha256sum] = "b7bace9a8e543b84736d6ef5ce5430305746efea3aacb24391f692efc6f3c8d3"

inherit autotools gettext

RDEPENDS_${PN} = "ncurses"

[-- Attachment #3: ncursesw.patch --]
[-- Type: application/octet-stream, Size: 543 bytes --]

--- nano-2.2.6.orig/configure.ac	2012-03-07 19:13:30.196063086 -0800
+++ nano-2.2.6/configure.ac	2012-03-07 19:07:46.876071285 -0800
@@ -442,7 +442,7 @@
     AC_CHECK_HEADERS(ncurses.h)
 
     if test x$enable_utf8 != xno; then
-	AC_CHECK_LIB(ncursesw, get_wch, [CURSES_LIB="-lncursesw" CPPFLAGS="-I/usr/include/ncursesw $CPPFLAGS" CURSES_LIB_NAME=ncursesw CURSES_LIB_WIDE=yes])
+	AC_CHECK_LIB(ncursesw, get_wch, [CURSES_LIB="-lncursesw" CURSES_LIB_NAME=ncursesw CURSES_LIB_WIDE=yes])
     fi
 
     if eval "test x$CURSES_LIB_NAME = x"; then

Re: select installation packages

[Andre Bella]

[-- Attachment #1: Type: text/plain, Size: 6198 bytes --]

HI Rudolf, 
I was able to build nano:
but my question is there a menuconfig to select what to build like in buildroot?

andre@linux:~/fsl-community-bsp/build$ bitbake -b nano
WARNING: Buildfile specified, dependencies will not be handled. If this is not what you want, do not use -b / --buildfile.

OE Build Configuration:
BB_VERSION        = "1.15.2"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "imx53qsb"
DISTRO            = "poky"
DISTRO_VERSION    = "1.2.2"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta              
meta-yocto        = "(nobranch):6caa7d1d6c122d084ed01d1f5e1dae0bf259f854"
meta-oe           = "(nobranch):c0117f5ad7d1fe18d149bda426c7134ff24daae8"
meta-fsl-arm      = "(nobranch):debea1a3c80227b33a3bbaa21c51435db1b3f5d7"
meta-fsl-arm-extra = "(nobranch):6710df97df3d96776c598330e1bd2c63a9450030"
meta-fsl-demos    = "(nobranch):02186c594a782c9c5f5a2df1d0dbb3a91fd1e929"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 1 of 12 (ID: 4, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_fetch)
NOTE: package nano-2.2.5-r2.0: task do_fetch: Started
NOTE: package nano-2.2.5-r2.0: task do_fetch: Succeeded
NOTE: Running task 2 of 12 (ID: 0, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_unpack)
NOTE: package nano-2.2.5-r2.0: task do_unpack: Started
NOTE: package nano-2.2.5-r2.0: task do_unpack: Succeeded
NOTE: Running task 3 of 12 (ID: 1, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_patch)
NOTE: package nano-2.2.5-r2.0: task do_patch: Started
NOTE: package nano-2.2.5-r2.0: task do_patch: Succeeded
NOTE: Running task 4 of 12 (ID: 6, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_configure)
NOTE: Running task 5 of 12 (ID: 10, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_populate_lic)
NOTE: package nano-2.2.5-r2.0: task do_populate_lic: Started
NOTE: package nano-2.2.5-r2.0: task do_configure: Started
NOTE: package nano-2.2.5-r2.0: task do_populate_lic: Succeeded
NOTE: package nano-2.2.5-r2.0: task do_configure: Succeeded
NOTE: Running task 6 of 12 (ID: 7, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_compile)
NOTE: package nano-2.2.5-r2.0: task do_compile: Started
NOTE: package nano-2.2.5-r2.0: task do_compile: Succeeded
NOTE: Running task 7 of 12 (ID: 2, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_install)
NOTE: package nano-2.2.5-r2.0: task do_install: Started
NOTE: package nano-2.2.5-r2.0: task do_install: Succeeded
NOTE: Running task 8 of 12 (ID: 9, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_package)
NOTE: Running task 9 of 12 (ID: 3, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_populate_sysroot)
NOTE: package nano-2.2.5-r2.0: task do_package: Started
NOTE: package nano-2.2.5-r2.0: task do_populate_sysroot: Started
NOTE: package nano-2.2.5-r2.0: task do_populate_sysroot: Succeeded
NOTE: package nano-2.2.5-r2.0: task do_package: Succeeded
NOTE: Running task 10 of 12 (ID: 11, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_package_write_rpm)
NOTE: package nano-2.2.5-r2.0: task do_package_write_rpm: Started
NOTE: package nano-2.2.5-r2.0: task do_package_write_rpm: Succeeded
NOTE: Running noexec task 11 of 12 (ID: 8, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_package_write)
NOTE: Running noexec task 12 of 12 (ID: 5, /home/andre/fsl-community-bsp/sources/meta-openembedded/meta-oe/recipes-support/nano/nano_2.2.5.bb, do_build)
NOTE: Tasks Summary: Attempted 12 tasks of which 0 didn't need to be rerun and all succeeded.

Summary: There was 1 WARNING message shown.
andre@linux:~/fsl-community-bsp/build$ 


--- On Thu, 2/14/13, Rudolf Streif <rstreif@linuxfoundation.org> wrote:

From: Rudolf Streif <rstreif@linuxfoundation.org>
Subject: Re: [yocto] select installation packages
To: "Andre Bella" <scancool@yahoo.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Date: Thursday, February 14, 2013, 10:10 AM

Hi Andre,
There actually is no recipe for building the nano editor in YP by default. Unless you added one,
bitbake -b nano

would result in this output
ERROR: Unable to find any recipe file matching 'nano'

I have attached a recipe for you to build nano and a patch to handle a configuration mistake configure.ac causing do_configure to fail.

If you add that recipe you can run bitbake nano. You can also include into your image by adding
IMAGE_INSTALL_append = " nano"

to your conf/local.conf file.
:rjs


On Thu, Feb 14, 2013 at 8:02 AM, Andre Bella <scancool@yahoo.com> wrote:

Hello 
 I had used buildroot in the pass and I like it cause is very easy to use, but I'm moving to yocto cause it has more applications than buildroot, in buildroot you can select the packages you want to add by going to menuconfig, how do I select the packages I wan to add in yocto, for example if I wan to add nano or gstreamer, from the guide I seen you just type bitbake -b nano, but is there a menuconfig on yocto where you can select the package you want to add before you build the image?

thanks,

_______________________________________________

yocto mailing list

yocto@yoctoproject.org

https://lists.yoctoproject.org/listinfo/yocto





-- 
-- 
Rudolf J. StreifDirector of Embedded Solutions
The Linux Foundation
rudolf.streif@linux.com
Phone: +1.619.631.5383Skype: rudolfstreifPGP: RSA 2048/2048 D6E7D28B

Linux Foundation Events Schedule:  events.linuxfoundation.org

Linux Foundation Training Schedule: training.linuxfoundation.org






[-- Attachment #2: Type: text/html, Size: 9626 bytes --]

Re: select installation packages

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

On 14 February 2013 17:31, Andre Bella <scancool@yahoo.com> wrote:

> but my question is there a menuconfig to select what to build like in
> buildroot?
>

Hob has a UI, but if you're using the commandline bitbake then you'll have
to edit packagegroups, images, or your local.conf manually.

Ross

[-- Attachment #2: Type: text/html, Size: 571 bytes --]

Re: select installation packages

[Trevor Woerner]

On Thu, Feb 14, 2013 at 11:02 AM, Andre Bella <scancool@yahoo.com> wrote:
> is there a menuconfig on yocto where you can select the package you want to add before you build the image?

I would suggest giving hob a try:

<checkout the yocto project from git>
$ source poky/oe-init-build-env
$ bitbake -u hob

Bitbake will compile need to download and compile up a bunch of stuff
(just like menuconfig) but it'll take a bit longer. Eventually a UI
will come up from which you can start selecting things like your
machine, packages, etc.

Re: select installation packages

[Andre Bella]

[-- Attachment #1: Type: text/plain, Size: 825 bytes --]

Thanks but I'm not sure if you understood, with hob you can only uninstall
after the image has been build , were you able to select what to install before building the image? same as buildroot?

--- On Thu, 2/14/13, Burton, Ross <ross.burton@intel.com> wrote:

From: Burton, Ross <ross.burton@intel.com>
Subject: Re: [yocto] select installation packages
To: "Andre Bella" <scancool@yahoo.com>
Cc: "Rudolf Streif" <rstreif@linuxfoundation.org>, yocto@yoctoproject.org
Date: Thursday, February 14, 2013, 10:39 AM

On 14 February 2013 17:31, Andre Bella <scancool@yahoo.com> wrote:


but my question is there a menuconfig to select what to build like in buildroot?

Hob has a UI, but if you're using the commandline bitbake then you'll have to edit packagegroups, images, or your local.conf manually.


Ross

[-- Attachment #2: Type: text/html, Size: 1490 bytes --]

Re: select installation packages

[Trevor Woerner]

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

On Thu, Feb 14, 2013 at 12:44 PM, Andre Bella <scancool@yahoo.com> wrote:
> Thanks but I'm not sure if you understood, with hob you can only uninstall
> after the image has been build , were you able to select what to install before building the image? same as buildroot?

Yes.

Once you have selected your "machine" and "base image", if you click
on "Edit Image" (bottom right) you can add (or remove) packages before
building.

[-- Attachment #2: hob.png --]
[-- Type: image/png, Size: 51230 bytes --]

[-- Attachment #3: edit.png --]
[-- Type: image/png, Size: 356171 bytes --]

Re: select installation packages

[Andre Bella]

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

Thank you Trevor, great information!!!


--- On Thu, 2/14/13, Trevor Woerner <twoerner@gmail.com> wrote:

From: Trevor Woerner <twoerner@gmail.com>
Subject: Re: [yocto] select installation packages
To: "Andre Bella" <scancool@yahoo.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Date: Thursday, February 14, 2013, 11:00 AM

On Thu, Feb 14, 2013 at 12:44 PM, Andre Bella <scancool@yahoo.com> wrote:
> Thanks but I'm not sure if you understood, with hob you can only uninstall
> after the image has been build , were you able to select what to install before building the image? same as buildroot?

Yes.

Once you have selected your "machine" and "base image", if you click
on "Edit Image" (bottom right) you can add (or remove) packages before
building.

[-- Attachment #2: Type: text/html, Size: 1216 bytes --]