From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Adam Heath <doogie@brainfood.com>, xen-devel@lists.sourceforge.net
Subject: Re: inclusion of figlet source
Date: Mon, 03 Jan 2005 06:40:19 +0100 [thread overview]
Message-ID: <41D8DAC3.1060007@diku.dk> (raw)
In-Reply-To: <E1CjZeB-0003a7-00@mta1.cl.cam.ac.uk>
Keir Fraser wrote:
> Using autoconf/automake would make sense for a highly portable
> application that must compile on many platforms with many different
> environments and compilers. For Xen I think it'll just complicate
> things. We only support one arch at the moment -- as others are
> incorporated they will extend compile.h manually for their own
> compilation environment if it isn't GCC. The main thing that autoconf
> does of course is shield you from environment differences (e.g. sysv
> vs. bsd) -- but Xen never includes system headers so this is also a
> non-issue.
If anyone is thinking of changing the build system, I can highly
recommend Jam. It handles stuff like dependency scanning and
multi-directory builds much better than Make does, allows more portable
build specifications, and unlike other modern Make-replacements it does
not need a full language runtime (like Ant or Scons do) to run.
Jacob
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
prev parent reply other threads:[~2005-01-03 5:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 5:27 inclusion of figlet source Adam Heath
2004-12-29 8:57 ` Keir Fraser
2004-12-29 22:17 ` Adam Heath
2005-01-03 5:40 ` Jacob Gorm Hansen [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=41D8DAC3.1060007@diku.dk \
--to=jacobg@diku.dk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=doogie@brainfood.com \
--cc=xen-devel@lists.sourceforge.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.