All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Ncurses and --disable-static
Date: Mon, 30 Aug 2010 10:14:54 +0200	[thread overview]
Message-ID: <87wrr8y0sh.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4C7B4E69.7080105@hydrix.com> (Ian's message of "Mon, 30 Aug 2010 16:23:37 +1000")

>>>>> "Ian" == Ian  <reg-ian.ridley-buildroot@hydrix.com> writes:

 Ian> A little question for anyone out there:
 Ian> The makefile for ncurses contains the following:


 Ian>     ifneq ($(BR2_PACKAGE_NCURSES_TARGET_HEADERS),y)
 Ian>     NCURSES_CONF_OPT += --disable-static
 Ian>     endif

 Ian> but BR2_PACKAGE_NCURSES_TARGET_HEADERS is no longer defined in the ncurses'
 Ian> Config.in, this was removed in a change to using BR2_HAVE_DEVFILES to decide to
 Ian> install headers in the target (see commit 58508f3 by Peter Korsgaard).

 Ian> Now as a result of this ncurses is now always configured with
 Ian> --disable-static, even when BR2_HAVE_DEVFILES is set to "y".

Thanks for informing us.

 Ian> So my question is should "--disable-stable" be added to NCURSES_CONF_OPT:

 Ian>  1. always,
 Ian>  2. never, or
 Ian>  3. when BR2_HAVE_DEVFILES is "y" (instead of using
 Ian>     BR2_PACKAGE_NCURSES_TARGET_HEADERS).

Either always or never. We have a mix of enable/disable-static in the
tree, so we don't have a clear winner, but as we have been using always
for almost 1 year now, and it cuts down on compilation time I'm going to
go with "always".

Thanks.
-- 
Bye, Peter Korsgaard

      reply	other threads:[~2010-08-30  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  6:23 [Buildroot] Ncurses and --disable-static Ian
2010-08-30  8:14 ` Peter Korsgaard [this message]

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=87wrr8y0sh.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 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.