From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gorm Hansen Subject: Re: inclusion of figlet source Date: Mon, 03 Jan 2005 06:40:19 +0100 Message-ID: <41D8DAC3.1060007@diku.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Keir Fraser Cc: Adam Heath , xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org 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