This is the mail archive of the
mailing list for the GCC project.
RE: automation: Problem with builddir != srcdir requirement
- From: Claudio Fontana <sick_soul at yahoo dot it>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: 'GCC Development' <gcc at gcc dot gnu dot org>
- Date: Fri, 3 Mar 2006 04:34:47 -0800 (PST)
- Subject: RE: automation: Problem with builddir != srcdir requirement
--- Dave Korn <firstname.lastname@example.org> wrote:
> On 03 March 2006 11:38, Claudio Fontana wrote:
> >> Programs that do
> >> not support it are buggy and should be reported
> >> the author.
> > This might be good in theory, but in practice it's
> > that simple. I am screening _all_ GNU projects,
> > I'm testing, contacting the maintainers, advicing,
> > writing many, many patches and whole new build
> > just to have all GNU projects support the
> existence of
> > a working configure script, or a Makefile with the
> > common targets.
> > Maybe when all GNU projects are mostly ok with the
> > coding standards, then we can be picky and start
> > fix projects with builddir == srcdir assumption.
> > Now it's not a realistic goal.
> Surely, now, when you're going over the build
> systems of all these projects
> and tidying them up to standard, rather than later,
> in an entire subsequent
> second pass over all the same ground again, is
> /exactly/ the right time to do
Yes, when I have the chance to provide a completely
new build system, I try to offer a complete and good
> Supporting builddir!=srcdir is only a tiny
> amount extra on top of what
> you're already doing, probably mostly handled simply
> by modifying your
> standard templates for configure scripts. Doing it
> in a second pass would
> require a /vast/ amount of redundant effort.
Sometimes the maintainers are not too happy to have
their build systems changed, so it happens that I have
to keep changes to a minimum in order to get anything
> _Please_ think very seriously about doing it now,
> as you go along.
When I can, I do it. In practice I'll need more than
one pass, and even more than two (test the release
when it comes out, point out remaining problems, or
bugs that crept in for example in the dist: rule,..)
> Can't think of a witty .sigline today....
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB