From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] make output of compiling a bit less verbose to make warnings more visible
Date: Wed, 03 Sep 2008 12:37:28 +0200 [thread overview]
Message-ID: <1220438248.4164.41.camel@fz.local> (raw)
In-Reply-To: <ca0f59980809030137p7922dafbj6faf687f2ed06d8c@mail.gmail.com>
Am Mittwoch, den 03.09.2008, 16:37 +0800 schrieb Bean:
> However, I don't like that it uses ruby to generate makefiles. Ruby is
> not a standard component, so there is a chance that user don't install
> it. I guess perl would be better.
I had somehow already the impression that this ruby based build system
isn't really well maintained ;)
I looked now even a bit over the automake[0] documentation.
For me personally it just looks easier to get into that, because it is
just made for Makefile's instead of some perl/python/ruby script which
generates them.
If automake isn't enough maybe we could use a combination of it with a
small perl script or so?
Though I don't know any perl/python/ruby at all.
I'm willing to really look into this automake stuff if there are no
strong objections against it, in the hope that in the end the build
system is clean, easily understandable and can be well maintained :)
Though this will probable take a little while so I still think Colin's
way would be a good short term solution and for long term we remake the
whole build process with that idea integrated from the beginning.
[0] http://www.gnu.org/software/automake/manual/automake.html
--
Felix Zielcke
next prev parent reply other threads:[~2008-09-03 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 16:43 [RFC] make output of compiling a bit less verbose to make warnings more visible Felix Zielcke
2008-09-02 17:10 ` Felix Zielcke
2008-09-02 19:27 ` Robert Millan
2008-09-02 19:43 ` Vesa Jääskeläinen
2008-09-02 20:47 ` Colin D Bennett
2008-09-03 6:59 ` Felix Zielcke
2008-09-03 8:37 ` Bean
2008-09-03 10:37 ` Felix Zielcke [this message]
2008-09-02 17:30 ` Javier Martín
2008-09-03 7:05 ` Hans Lambermont
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=1220438248.4164.41.camel@fz.local \
--to=fzielcke@z-51.de \
--cc=grub-devel@gnu.org \
/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.