From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/ncurses
Date: Sat, 24 Jan 2009 07:33:05 +0100 [thread overview]
Message-ID: <87ocxxi57i.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090123230218.44A1376564@busybox.osuosl.org> (ulf@uclibc.org's message of "Fri\, 23 Jan 2009 23\:02\:17 +0000 \(UTC\)")
>>>>> "ulf" == ulf <ulf@uclibc.org> writes:
ulf> Author: ulf
ulf> Date: 2009-01-23 23:02:15 +0000 (Fri, 23 Jan 2009)
ulf> New Revision: 24992
ulf> Log:
ulf> Fix static lib dep for ncurses
ulf> Changeset:
ulf> Modified: trunk/buildroot/package/ncurses/ncurses.mk
ulf> ===================================================================
ulf> --- trunk/buildroot/package/ncurses/ncurses.mk 2009-01-23 21:06:05 UTC (rev 24991)
ulf> +++ trunk/buildroot/package/ncurses/ncurses.mk 2009-01-23 23:02:15 UTC (rev 24992)
ulf> @@ -130,7 +130,9 @@
ulf> -$(STRIPCMD) $(STRIP_STRIP_UNNEEDED) $@
ulf> touch -c $@
ulf> -$(TARGET_DIR)/usr/lib/libncurses.a: $(STAGING_DIR)/lib/libncurses.a
ulf> +$(NCURSES_DIR)/lib/libncurses.a: $(NCURSES_DIR)/lib/libncurses.so.$(NCURSES_VERSION)
ulf> +
ulf> +$(TARGET_DIR)/usr/lib/libncurses.a: $(NCURSES_DIR)/lib/libncurses.a
That looks odd. Why not simply always install the development stuff to
target, and simply rely on the BR2_HAVE_DEVFILES setting to clean it
up if it isn't desired?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-24 6:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 23:02 [Buildroot] svn commit: trunk/buildroot/package/ncurses ulf at uclibc.org
2009-01-24 6:33 ` Peter Korsgaard [this message]
2009-01-25 10:07 ` Thomas Lundquist
2009-01-25 20:56 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-03-01 22:35 jacmet at uclibc.org
2009-01-22 22:58 ulf at uclibc.org
2009-01-12 7:44 ulf at uclibc.org
2009-01-11 13:33 thomasez at uclibc.org
2008-07-01 19:24 jacmet at uclibc.org
2008-04-10 8:17 nkukard at uclibc.org
2008-04-10 5:14 nkukard at uclibc.org
2008-04-09 11:38 nkukard at uclibc.org
2008-04-09 22:35 ` Hamish Moffatt
2008-04-10 5:14 ` Nigel Kukard
2008-04-10 7:06 ` Peter Korsgaard
2008-04-10 9:10 ` Hamish Moffatt
2008-03-31 14:44 jacmet at uclibc.org
2008-03-07 13:57 ninevoltz at uclibc.org
2008-03-07 14:03 ` Peter Korsgaard
2008-03-06 18:19 ninevoltz at uclibc.org
2008-03-07 13:30 ` Peter Korsgaard
2007-07-23 8:33 ulf at uclibc.org
2007-06-25 16:56 aldot at uclibc.org
2007-06-25 16:35 aldot at uclibc.org
2007-06-25 15:38 aldot at uclibc.org
2007-06-23 13:56 aldot at uclibc.org
2007-03-07 14:46 aldot at uclibc.org
2007-01-30 17:47 aldot at uclibc.org
2007-01-22 23:52 andersen at uclibc.org
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=87ocxxi57i.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox