Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] package/ncurses: fixup wide support for static targets
Date: Wed, 20 Aug 2014 14:22:38 +0200	[thread overview]
Message-ID: <20140820142238.404d0c48@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LXsfoHafOY9cdVfP1waNcaWkrM8xMgyiqswE4LHX56wMA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Tue, 19 Aug 2014 21:47:55 +0200, Thomas De Schampheleire wrote:

> Here you could also do something like
> ifeq ($(BR2_PREFER_STATIC_LIB),y)
> NCURSES_LIB_EXT = .a
> else
> NCURSES_LIB_EXT = .so
> endif
> define NCURSES_LINK_LIBS
>        for lib in $(NCURSES_LIBS-y); do \
>                ln -sf $${lib}$(NCURSES_LIB_SUFFIX)$(NCURSES_LIB_EXT) \
>                        $(1)/usr/lib/$${lib}$(NCURSES_LIB_EXT); \
>        done
> endef
> to avoid duplicating the hook content.

Except that for now, the semantic is:

 * BR2_PREFER_STATIC_LIB=y -> install only static libraries

 * BR2_PREFER_STATIC_LIB undefined -> install *both* static and shared
   libraries.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-08-20 12:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 18:48 [Buildroot] [PATCH 0/4] Ncurses wide support Gustavo Zacarias
2014-08-19 18:48 ` [Buildroot] [PATCH 1/4] package/ncurses: Allow building wide char support Gustavo Zacarias
2014-08-19 18:48 ` [Buildroot] [PATCH 2/4] package/ncurses: fixup wide support for static targets Gustavo Zacarias
2014-08-19 19:47   ` Thomas De Schampheleire
2014-08-20 12:22     ` Thomas Petazzoni [this message]
2014-08-20 12:34       ` Thomas De Schampheleire
2014-08-20 12:39         ` Gustavo Zacarias
2014-08-19 18:48 ` [Buildroot] [PATCH 3/4] nano: enable ncursesw support Gustavo Zacarias
2014-08-19 18:48 ` [Buildroot] [PATCH 4/4] httping: enable ncurses support Gustavo Zacarias

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=20140820142238.404d0c48@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox