All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: "Ronald G. Minnich" <rminnich@lanl.gov>
Cc: Tobias Hunger <tobias@aquazul.com>, xen-devel@lists.sourceforge.net
Subject: Re: autotoolizing xen?
Date: Fri, 18 Feb 2005 11:20:48 -0800	[thread overview]
Message-ID: <42164010.7010805@diku.dk> (raw)
In-Reply-To: <Pine.LNX.4.58.0502180815070.21698@enigma.lanl.gov>

Ronald G. Minnich wrote:
> 
> On Fri, 18 Feb 2005, Tobias Hunger wrote:
> 
> 
>>I was wondering what the general opinion on autotoolizing xen is? I am
>>volunteering to do so, if there is interest in updating the build system
>>to use autoconf, automake and/or libtool.
> 
> 
> oh, please don't do this. I do not like those things at all. 

I agree, please do not go down that road. Look at 'GNU helloworld' for 
an (extreme) example of how horibbly bloated this will make your 
software. On my Gentoo box the configure scripts often take longer to 
run than the actual build of the software itself.

Instead, use a better build system. I am using Jam (which is public 
domain) for my stuff, and that works perfectly, and the build 
specifications are a lot simpler that the xen Makefiles.

For example, here is my Jamfile for tools/libxc:

--------------------------------------------
SubDir TOP tools libxc  ;

SubDirHdrs $(TOP) tools libxutil ;

Library libxc :
xc_atropos.c
xc_bvtsched.c
xc_domain.c
xc_evtchn.c
xc_io.c
xc_linux_build.c
xc_linux_restore.c
xc_linux_save.c
xc_misc.c
xc_physdev.c
xc_plan9_build.c
xc_private.c
xc_rrobin.c
;
--------------------------------------------

Contrast that with corresponding Makefile, and you will see how much 
simpler the Jamfile is. Jam also handles all the tedious stuff like 
header-dependencies without littering your tree with .dep files, and 
having it output target files to a separate build-directory (which once 
you've tried it you will never want to live without, saves you a lot of 
'make clean's) is trivial, just set a single variable at the top level.

Some really big commercial code bases use Jam. If you look at the 
'Jamming' mailing list archives you will find build-masters from very 
well known software companies on there. Personally I have used it to 
build a game which retailed more than 3 million copies, on four very 
different platforms.

Jacob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-02-18 19:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 13:26 autotoolizing xen? Tobias Hunger
2005-02-18 15:15 ` Ronald G. Minnich
2005-02-18 15:44   ` X86_64 status? Alvin Starr
2005-02-18 15:53   ` autotoolizing xen? Tobias Hunger
2005-02-18 16:06     ` Christian Limpach
2005-02-18 16:33       ` Nivedita Singhvi
2005-02-18 16:03   ` Anthony Liguori
2005-02-18 16:30     ` Tobias Hunger
2005-02-18 19:20   ` Jacob Gorm Hansen [this message]
2005-02-18 20:04     ` Anthony Liguori
2005-02-18 20:03       ` Jacob Gorm Hansen
2005-03-07 10:01         ` Nick Craig-Wood
2005-02-18 21:25     ` Tobias Hunger
2005-02-18 19:56   ` Adam Sulmicki
2005-02-19 13:10 ` Keir Fraser

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=42164010.7010805@diku.dk \
    --to=jacobg@diku.dk \
    --cc=rminnich@lanl.gov \
    --cc=tobias@aquazul.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.