All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Scott Garman <scott.a.garman@intel.com>
Subject: Re: [PATCH 1/1] ncurses: fix packaging of moved libraries
Date: Wed, 14 Mar 2012 07:57:56 -0700	[thread overview]
Message-ID: <4F60B1F4.4040705@linux.intel.com> (raw)
In-Reply-To: <78b7df910bf1d5d25f5cc637a15c8e867d7bd712.1331684953.git.scott.a.garman@intel.com>



On 03/13/2012 05:31 PM, Scott Garman wrote:
> The recent move of some of the ncurses libraries to base_libdir
> does not work with our automatic library packaging, so this
> explicity creates packages for libncurses, libncursesw, and
> libtinfo.
> 
> Signed-off-by: Scott Garman <scott.a.garman@intel.com>
> ---
>  meta/recipes-core/ncurses/ncurses.inc |   18 ++++++++++++++++--
>  1 files changed, 16 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-core/ncurses/ncurses.inc
> index e450868..155c0bd 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = "file://ncurses/base/version.c;beginline=1;endline=27;md5=cbc
>  SECTION = "libs"
>  DEPENDS = "ncurses-native"
>  DEPENDS_virtclass-native = ""
> -INC_PR = "r5"
> +INC_PR = "r6"
>  
>  inherit autotools binconfig multilib_header
>  
> @@ -220,6 +220,9 @@ pkg_prerm_ncurses-tools () {
>  BBCLASSEXTEND = "native nativesdk"
>  
>  PACKAGES += " \
> +  ${PN}-libncurses \
> +  ${PN}-libncursesw \

This one needs to be dependent on ENABLE_WIDEC

> +  ${PN}-libtinfo \
>    ${PN}-tools \
>    ${PN}-terminfo \
>    ${PN}-terminfo-base \
> @@ -231,7 +234,18 @@ FILES_${PN} = "\
>    ${bindir}/ncurses5-config \
>    ${bindir}/ncursesw5-config \
>    ${datadir}/tabset \
> -  ${base_libdir}/* \
> +"
> +
> +FILES_${PN}-libncurses = "\
> +  ${base_libdir}/libncurses.so.* \
> +"
> +
> +FILES_${PN}-libncursesw = "\
> +  ${base_libdir}/libncursesw.so.* \
> +"

This file doesn't exist if !ENABLE_WIDEC (which is the case with
poky-tiny for example).

> +
> +FILES_${PN}-libtinfo = "\
> +  ${base_libdir}/libtinfo.so.* \
>  "
>  
>  # This keeps only tput/tset in ncurses

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



  reply	other threads:[~2012-03-14 15:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  0:31 [PATCH 0/1] ncurses packaging fix Scott Garman
2012-03-14  0:31 ` [PATCH 1/1] ncurses: fix packaging of moved libraries Scott Garman
2012-03-14 14:57   ` Darren Hart [this message]
2012-03-14 15:00     ` Martin Jansa
2012-03-14 15:07       ` Paul Eggleton
2012-03-14 15:18         ` Darren Hart
2012-03-14 15:20           ` Paul Eggleton
2012-03-14 15:12       ` Darren Hart
2012-03-14 15:22         ` Paul Eggleton
2012-03-14  7:51 ` [PATCH 0/1] ncurses packaging fix Martin Jansa
2012-03-14 16:49   ` Scott Garman
2012-03-14  8:22 ` Koen Kooi
2012-03-14 16:26   ` Scott Garman
  -- strict thread matches above, loose matches on Subject: below --
2012-03-14 16:36 [PATCH 0/1] ncurses packaging fix [v2] Scott Garman
2012-03-14 16:36 ` [PATCH 1/1] ncurses: fix packaging of moved libraries Scott Garman
2012-03-14 16:53   ` Koen Kooi
2012-03-14 17:09     ` Scott Garman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F60B1F4.4040705@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.a.garman@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.