From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] advice on makefile
Date: Sat, 12 Apr 2008 19:25:10 +1000 [thread overview]
Message-ID: <20080412092510.GB15915@cloud.net.au> (raw)
In-Reply-To: <1207839098.6817.444.camel@nigel-x60>
On Thu, Apr 10, 2008 at 02:51:38PM +0000, Nigel Kukard wrote:
>
> > Nigel> What is going on in libxml2.mk? I need to add libxml as one of the
> > Nigel> deps :)
> >
> > That's the new autotools autotargets stuff. I don't know much about
> > it, but take a look at package/Makefile.autotools.in.
> >
> > The problem is going to be that the automatic rules uses
> > $BUILD_DIR/package-<version>/.stamp_staging_installed, so you'll have
> > to hardcode the version and it'll break when the version is bumped.
> >
> > Maybe we should rather add a .stamp_<package>_<whatever> directly in
> > BUILD_DIR?
>
> At present I nuke .root and root in my build_xxx/uclibc dir and do a
> make and everything is installed again. Maybe its just my luck ...
>
> If we add .stamp_xxx to the build dir ... I guess my luck will run
> out ;)
Yep, that really sucks. Please, depend on files in the target dir rather
than on stamp files elsewhere. Unless you use external toolchain I think
nuking the root is already unsafe :-(
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-04-12 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 11:32 [Buildroot] advice on makefile Nigel Kukard
2008-04-10 11:56 ` Peter Korsgaard
2008-04-10 14:11 ` Nigel Kukard
2008-04-10 14:35 ` Peter Korsgaard
2008-04-10 14:51 ` Nigel Kukard
2008-04-12 9:25 ` Hamish Moffatt [this message]
2008-04-12 13:16 ` Peter Korsgaard
2008-04-10 17:28 ` Nigel Kukard
2008-04-10 17:30 ` Nigel Kukard
2008-04-10 18:09 ` Peter Korsgaard
[not found] ` <1207851468.6817.498.camel@nigel-x60>
2008-04-10 18:59 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2008-04-10 7:52 Nigel Kukard
2008-04-10 8:37 ` 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=20080412092510.GB15915@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox