This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: [ANNOUNCEMENT] Cygwin/XFree86 DocBook-based FAQ draft
- To: "Harold Hunt" <huntharo at msu dot edu>,"David Starks-Browning" <starksb at ebi dot ac dot uk>,<cygwin-xfree at cygwin dot com>
- Subject: Re: [ANNOUNCEMENT] Cygwin/XFree86 DocBook-based FAQ draft
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Thu, 24 May 2001 08:17:22 +1000
- References: <NHEELHJHHFKPMAEAFMFCAEMGCFAA.huntharo@msu.edu>
----- Original Message -----
From: "Harold Hunt" <huntharo@msu.edu>
> Ah good, so I'm not alone in thinking that it is ok to build the
> documentation on Linux.
Whoever said it shouldn't be ok to do that? The point is that is
__MUST__ be ok for cygwin users to build. Otherwise we are going
__backwards__.
> Does Cygwin actually have an elaborate build system for documentation?
> (e.g. makefiles, autoconf stuff, etc.) Or, do the doc builders just
run
> 'db2html' on their Linux boxen when things have been updated?
autoconf is used, not automake:
$ ls /usr/src/src/winsup/doc/
CVS faq.texinfo overview2.sgml
ChangeLog fhandler-tut.txt pathnames.sgml
Makefile.in filemodes.sgml programming.sgml
calls.texinfo gcc.sgml readme.texinfo
changes.texinfo gdb.sgml relnotes.texinfo
configure history.texinfo setup-net.sgml
configure.in how-api.texinfo setup.sgml
copy.texinfo how-programming.texinfo setup2.sgml
cygwin-api.in.sgml how-resources.texinfo textbinary.sgml
cygwin-ug-net.in.sgml how-using.texinfo using.sgml
cygwin-ug.in.sgml how.texinfo what.texinfo
cygwinenv.sgml install.texinfo who.texinfo
dll.sgml legal.sgml windres.sgml
doctool.c ntsec.sgml
doctool.txt overview.sgml
> Thanks for the input,
>
> Harold
>
>
Rob