Marc van Woerkom wrote:
>
> Hello Stephan,
>
> I looked at the build management in kdebase-2.0.
> Very interesting to see how you guys did it.
>
> Two questions:
>
> 1. I am still not sure, if modules should have their
> own configure script.
> My position so far was that there is only one
> configuration, for the whole tree.
> What is the benefit of sub-configure scripts?
They don't have it. There is only one configure, but it's created
from several configure.in.ins. The idea is to make parts of the
modules interchangable.
>
> 2. You use this sequence in your Makefile.cvs bootstrap:
>
> @echo "*** Building Makefile templates (step one)"
> @automake
> @echo "*** Scanning for moc files and kde tags"
> @perl admin/am_edit
> @echo "*** Building Makefile templates (step two)"
> @autoconf
>
> Why does one need to have a autoconf call after
> the automake call?
> My belief was that automake is responsible for the
> autoconf calls.
No, it's not
Greetings, Stephan
--
Frauen und Maenner passen vielleicht nicht zusammen, aber meine
allerschoensten Schrammen habe ich mir bei diesem Duell geholt.
-- Reinhard Mey
