avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avrdude-dev] Documentation build tools requirements - many complain


From: Russell Shaw
Subject: Re: [avrdude-dev] Documentation build tools requirements - many complaints
Date: Mon, 07 Feb 2005 01:14:58 +1100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1

Joerg Wunsch wrote:
As Brian Dean wrote:


Would folks here object too loudly if we trimmed down the
documentation of AVRDUDE to just the Unix man page?

Does Windows support Unix man pages?

Not even WinAVR does.  It ships a `man' command, but that would need a
lot of hacking before it could be made work.

The reason I ask is that many folks have trouble building avrdude
from source.

Why don't you go the way avr-libc did?  Use configure --enable-docs in
order to build them, and default to being disabled.

I would prefer that we move essential documentation to just the man
page.  AVRDUDE is not a very complex program, after all.

What bothers me more here is that both, the man and the info page
basically express the same content, but as a developer, you gotta
write everything twice.  Some mdoc -> texi converter would be really
useful, in order to obtain the info pages automagically.

http://docbook2x.sourceforge.net/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]