Re: documentation patch

2001-01-24 Thread Gerald Pfeifer
On Fri, 19 Jan 2001, John R. Sheets wrote: The attached patch fixes this problem, but I'm not sure about using the conditional in documentation/Makefile.in. I'm pretty sure that's a GNU Make-specific feature (I could be wrong about that, tho). Then, please don't use it. ;) Are the Wine

Re: documentation patch

2001-01-19 Thread John R. Sheets
On Jan 18, 2001, Joerg Mayer [EMAIL PROTECTED] wrote: On Thu, Jan 18, 2001 at 09:09:35AM -0600, Jeremy White wrote: then documentation/wine-doc contains a nice set of HTML pages that can be used by the user (or tarballed into an RPM g). I've had problems building the documentation on a

RE: documentation patch

2001-01-19 Thread Neulinger, Nathan R.
NOTE: You'll want to run autoconf before reconfiguring Wine. Unfortunately since the patch adds a block of code to an early part of the configure script, and autoconf hardwires line numbers into the configure script, the extra diff noise turns the patch from a nice 1K

Re: documentation patch

2001-01-19 Thread Joerg Mayer
On Fri, Jan 19, 2001 at 11:44:43AM -0800, Alexandre Julliard wrote: You could use a configure variable, like we do with @XFILES@ for conditional X11 compilation. In this case I don't think it is justified though; the doc is not built by default, so there is no point in making it conditional.

Re: documentation patch

2001-01-19 Thread Alexandre Julliard
Joerg Mayer [EMAIL PROTECTED] writes: Maybe I understand you incorrectly, but a plain text or html version of the documentation should be provided with the normal tarball, just like we provide not only configure.in but also configure because there would be so many more questions/help

Re: documentation patch

2001-01-18 Thread Uwe Bonnes
Chris Morgan writes: ChangeLog entry: *documentation/installing.sgml, running.sgml, fonts.sgml, printing.sgml, installation-und-konfiguration.german, configuring.sgml opengl.sgml, registry.sgml: Chris Morgan [EMAIL PROTECTED] Updated for change in config file name. Removed references to

Re: documentation patch

2001-01-18 Thread Jeremy White
If you do cd documentation make wine-doc/index.html then documentation/wine-doc contains a nice set of HTML pages that can be used by the user (or tarballed into an RPM g). Jer Uwe Bonnes wrote: Chris Morgan writes: ChangeLog entry: *documentation/installing.sgml, running.sgml,

Re: documentation patch

2001-01-18 Thread Uwe Bonnes
Jeremy White writes: If you do cd documentation make wine-doc/index.html then documentation/wine-doc contains a nice set of HTML pages that can be used by the user (or tarballed into an RPM g). Hallo Jeremy, this is a problem with installed tools and what tools to install.

Re: documentation patch

2001-01-18 Thread Francois Gouget
On Thu, 18 Jan 2001, Uwe Bonnes wrote: [...] our development package now doesn't contain any more readable formatted files in ../documentation. So it get's harder to point posters in c.e.m.w to those files... [...] If that isn't acceptable, there should be another place where up-to-date

Re: documentation patch

2001-01-18 Thread John R. Sheets
On Jan 18, 2001, Uwe Bonnes [EMAIL PROTECTED] wrote: this is a problem with installed tools and what tools to install. hertz:/spare/bon/wine/documentation make wine-doc/index.html db2html wine-doc.sgml make: db2html: Command not found make: *** [wine-doc/index.html] Error 127 I don't

Re: documentation patch

2001-01-18 Thread Jeremy White
Hmm. IMHO, we should do a configure test for db2html, and report it as missing when the user goes to make the doco, along with some useful advice on where to get it from. And, of course, this applies to all the other tools required to build 'em. Jer "John R. Sheets" wrote: On Jan 18, 2001,

Re: documentation patch

2001-01-18 Thread Joerg Mayer
On Thu, Jan 18, 2001 at 09:09:35AM -0600, Jeremy White wrote: then documentation/wine-doc contains a nice set of HTML pages that can be used by the user (or tarballed into an RPM g). I've had problems building the documentation on a SuSE 7.0 (not solved). I think providing a Text version with