Re: xwpe -> want autoconf? (fwd)

[Jan Dvorak <johnydog@go.cz>]

On Thu, Sep 14, 2000 at 10:32:06PM -0400, Dennis Payne wrote:
> What do you mean by autoconf support for xwpe-1.5.x?  autoconf is
> already used to compile xwpe.  As for using it for project files,
> I don't see how that would be useful.  Personally what I was thinking
> of for project files is to make them full blown makefiles.  For the
> most part users would just add files and perhaps edit the variables
> (like CFLAGS).  If however you wanted to add support for a different
> compiler you could by making a new rule.  Or you edit the rules for
> some weird modifications you need.
> 

I disagree with this. Most modern projects uses autoconf and/or automake, so
makefiles are generated. You'll than have two makefiles - one called .prj,
one the 'real' project makefile. I think that in project file there should
be only desktop settings, and what files belongs to project. That thing,
that project files have to contain compile rules, and compile than runs
from within them was obsoleted years before by *just* makefiles. In fact,
this was designed for that only person who has source codes is author
itself, and other people gets .exe only. In opensource development, there
is need for many people to get sources compile, and when there is makefiles,
there is really no need for compile-projectfiles. You cannot merge .prj and
'real' makefiles even if they have *exactly* the same syntax, or when
makefiles are included in source files, because they are generated.
Generated from *.in which is generated from *.am which may be generated from
`ls -l`.

Jan Dvorak <johnydog@go.cz>