Peter Clifton wrote: > Doesn't having maintainer mode options present, but switched off - > effect the automatic generation of build dependencies for C files etc..? > (This is a vague memory, but not one I've had chance to verify). > > This commit: > > commit 8dbe3eb93d3281d4f0e496f68d4ba7f20e78b43b > Author: Dan McMahill <d...@mcmahill.net> > > When building from git sources and building docs, force maintainer-mode. > > When building from git sources, maintainer mode is required to build > the manual. So, unless the user has specified --disable-doc then > force maintainer mode. When building from a tarball, the preformatted > manual is already contained and we do not impose maintainer-mode. > Hopefully this puts to rest the documentation building issues once > and for all! > > > Tying --disable-doc to the disabling of maintainer mode is a bit "magic" > for my liking - especially if maintainer mode has other side-effects.
The logic is the other way around. --enable-maintainer-mode *always* enables maintainer-mode. --disable-docs *always* disables doing anything with the docs. The "magic" is if you have git sources *and* you have not disabled building of the docs, then you get a messge like checking if maintainer-mode is requred - yes (building documentation with git sources requires it) and it is turned on regardless of what you have asked for. Thats is the only case where it is messed around with. _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user