From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] The svn commit of LiTE highlights an issue in Makefile.autotools.in
Date: Tue, 26 Aug 2008 07:56:03 -0700 (PDT) [thread overview]
Message-ID: <19163684.post@talk.nabble.com> (raw)
Many packages don't install as well as we would like.
The Makefile.autotools.in helps us standardise the way things are done but
does not always help.
In the case of LiTE the make command installs some bits and not others,
So I use HOOK_POST_INSTALL to install all the necessary files.
However I think that a HOOK_POST_CLEAN is needed so that when you write a
HOOK_POST_INSTALL target you automatically write a HOOK_POST_CLEAN that
undoes the extra bits you put in.
Currently without this, cleaning up after usage of HOOK_POST_INSTALL is a
real pain.
What do people think?
Daniel Laird
--
View this message in context: http://www.nabble.com/-RFC--The-svn-commit-of-LiTE-highlights-an-issue-in-Makefile.autotools.in-tp19163684p19163684.html
Sent from the BuildRoot mailing list archive at Nabble.com.
reply other threads:[~2008-08-26 14:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19163684.post@talk.nabble.com \
--to=daniel.j.laird@nxp.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