From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Makefile.autotools.in stamp files breaks multiple projects
Date: Mon, 8 Sep 2008 23:43:12 +1000 [thread overview]
Message-ID: <20080908134312.GA11819@cloud.net.au> (raw)
In-Reply-To: <20080908153954.5ad16cc0@atmel.com>
On Mon, Sep 08, 2008 at 03:39:54PM +0200, Hans-Christian Egtvedt wrote:
> On Fri, 5 Sep 2008 14:30:47 +1000
> Hamish Moffatt <hamish@cloud.net.au> wrote:
>
> > On Thu, Sep 04, 2008 at 12:50:35PM +1000, Hamish Moffatt wrote:
> > > 2. The .stamp_install files could be put somewhere under
> > > $(TARGET_DIR) instead of $(BUILD_DIR); they'd need to be stripped
> > > out by the various generators in target/.. though.
> >
> > Here's my patch to move the target-installed and post-install-hook
> > stamps to $(PROJECT_BUILD_DIR)/.stamp/$(PKG)_xyz instead of
> > $(BUILD_DIR)/$(PKG)/.stamp_xyz, so that these actions will be repeated
> > for each project.
> >
> > Any comments before I commit it?
> >
>
> I think it sounds nice, I did not look into the patch in detail but the
> solution seems good. The stamp directory could even be visible IMHO.
That's true, I might rename it to $(PROJECT_BUILD_DIR)/autotools-stamps.
Thanks for your feedback. I'll commit tomorrow.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-09-08 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 2:50 [Buildroot] Makefile.autotools.in stamp files breaks multiple projects Hamish Moffatt
2008-09-04 4:02 ` [Buildroot] Makefile.autotools.in stamp files breaks multipleprojects Ulf Samuelsson
2008-09-04 14:35 ` Hamish Moffatt
2008-09-05 4:30 ` [Buildroot] Makefile.autotools.in stamp files breaks multiple projects Hamish Moffatt
2008-09-08 13:39 ` Hans-Christian Egtvedt
2008-09-08 13:43 ` Hamish Moffatt [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=20080908134312.GA11819@cloud.net.au \
--to=hamish@cloud.net.au \
--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.