From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] advice on makefile
Date: Thu, 10 Apr 2008 20:59:44 +0200 [thread overview]
Message-ID: <871w5d8rj3.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1207851468.6817.498.camel@nigel-x60> (Nigel Kukard's message of "Thu\, 10 Apr 2008 18\:17\:48 +0000")
>>>>> "Nigel" == Nigel Kukard <nkukard@lbsd.net> writes:
Hi,
Nigel> OMW!! ..... after looking over autotools .... I think it should rather
Nigel> be improved and everything converted to autotools ... most of the stuff
Nigel> is standardized then. It would just be a small task of catching some
Nigel> specifics and adding a few more features...
>>
>> Yes, I also think that's the best long term solution (similar to how
>> it's done in openwrt, openembedded, ...).
Nigel> I think it needs a bit more magic though ...
;)
Nigel> I'll convert some of the things I've done so far to beecrypt,
Nigel> make files reduce from 100+ lines down to +- 10 ... its
Nigel> amazing!
Nigel> Do we have a wiki where this can be documented? would also
Nigel> suggest we not accept any patches with manual makefiles?
Nigel> unless there is a very good reason autotools cannot handle it,
Nigel> in which case autotools should be fixed not complexity added.
No, but we have docs/ ;)
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-10 18:59 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
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 [this message]
-- 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=871w5d8rj3.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