New subject: Intent to remove auto-autoloads.el, custom-load.el from CVS

Tuesday, 11 July 2000

        ...
>>>> "OG" == Olivier Galibert
<galibert(a)pobox.com&gt; writes: 
OG> On Tue, Jul 11, 2000 at 10:58:17AM +0900, Martin Buchholz wrote:
...
> Anyways, I now have changes in a private workspace to correctly
build
> these files, and if using GNU make, with minimal overhead (i.e. use
> the dependency information that can be gathered using GNU make
> extensions to avoid rebuilding every make). 
OG> In principle, I agree with this.  The only question I see is whether
OG> it will work out well with windows native?

On thinking it over, I've decided it's better to have a `depend' file
for the root directory just like we have one in src, instead of
relying on GNU make features.  The dependencies for lisp change rarely
(usually only when a file is added) and it's easy for the release
engineer to update it automatically (I already run `make depend').

`depend' is very simple.  It would contain only two lines:

lisp/custom-load.el lisp/auto-autoloads.el: lisp/foo.el lisp/bar.el ...
lisp/mule/auto-autoloads.el: lisp/mule/foo.el lisp/mule/bar.el ...

configure can automatically append this to Makefile, just like in
src.  This way of doing things ensures that something similar can be
easily done for Windows, because it's so simple.  All we need is an
"include" facility.  Am I right, Windows hackers?

And of course, non-GNU-make users will have the right things happen
with no effort.

Martin

P.S.
My current implementation does things like:

#ifdef USE_GNU_MAKE
lisp/custom-load.el: $(filter-out lisp/auto-autoloads.el lisp/custom-load.el
lisp/finder-inf.el, $(wildcard lisp/*.el))
#else
non-GNU make hackery
#endif

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Re: Intent to remove auto-autoloads.el, custom-load.el from CVS