From: Ian <reg-ian.ridley-buildroot@hydrix.com>
To: buildroot@busybox.net
Subject: [Buildroot] Ncurses and --disable-static
Date: Mon, 30 Aug 2010 16:23:37 +1000 [thread overview]
Message-ID: <4C7B4E69.7080105@hydrix.com> (raw)
A little question for anyone out there:
The makefile for ncurses contains the following:
ifneq ($(BR2_PACKAGE_NCURSES_TARGET_HEADERS),y)
NCURSES_CONF_OPT += --disable-static
endif
but BR2_PACKAGE_NCURSES_TARGET_HEADERS is no longer defined in the
ncurses' Config.in, this was removed in a change to using
BR2_HAVE_DEVFILES to decide to install headers in the target (see commit
58508f3 by Peter Korsgaard).
Now as a result of this ncurses is now always configured with
--disable-static, even when BR2_HAVE_DEVFILES is set to "y".
So my question is should "--disable-stable" be added to NCURSES_CONF_OPT:
1. always,
2. never, or
3. when BR2_HAVE_DEVFILES is "y" (instead of using
BR2_PACKAGE_NCURSES_TARGET_HEADERS).
Regards,
Ian.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100830/a6627f69/attachment.html>
next reply other threads:[~2010-08-30 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 6:23 Ian [this message]
2010-08-30 8:14 ` [Buildroot] Ncurses and --disable-static Peter Korsgaard
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=4C7B4E69.7080105@hydrix.com \
--to=reg-ian.ridley-buildroot@hydrix.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