From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master] xfont_font-util: convert to the autotools infrastructure
Date: Wed, 24 Feb 2010 21:46:16 +0100 [thread overview]
Message-ID: <87zl2y746f.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4B8589C4.5060206@gmail.com> (Paulius Zaleckas's message of "Wed, 24 Feb 2010 22:19:16 +0200")
>>>>> "Paulius" == Paulius Zaleckas <paulius.zaleckas@gmail.com> writes:
Hi,
>> Why? Isn't xfont-utils a bunch of programs to run on the target? Staging
>> is normally for libs.
>>
Paulius> Well now we have:
>> XFONT_FONT_UTIL_POST_INSTALL_STAGING_HOOKS += XFONT_FONT_UTIL_POST_INSTALL_FIXES
Paulius> Why do we need POST_INSTALL_STAGING hook when we installed
Paulius> only to TARGET?
True. The package used to only install into staging dir before Thomas'
commit, which also doesn't make much sense - Thomas?
>> $(eval $(call AUTOTARGETS,package/x11r7,xfont_font-util))
Paulius> Actually I believe it was installed in to staging for some reason...
Presumably yes, but I don't right away see why.
Paulius> I have ~200 patches (will post them soon :)) to update X.Org
Paulius> to 7.5 and I had to change post-install.sh script to new
Paulius> location for pkg-config or else it would fail building
Paulius> fonts... if I remember correctly.
Sounds good!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-02-24 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 20:27 [Buildroot] [git commit master] xfont_font-util: convert to the autotools infrastructure Thomas Petazzoni
2010-02-23 21:43 ` Paulius Zaleckas
2010-02-23 21:49 ` Peter Korsgaard
2010-02-24 20:19 ` Paulius Zaleckas
2010-02-24 20:46 ` Peter Korsgaard [this message]
2010-02-24 22:49 ` Will Wagner
2010-02-25 7:44 ` Thomas Petazzoni
2010-02-25 19:42 ` Paulius Zaleckas
2010-02-25 17:13 ` William Wagner
2010-02-25 19:08 ` Peter Korsgaard
2010-02-26 7:44 ` Thomas Petazzoni
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=87zl2y746f.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.