> However for unix the real issue is to have the html files been built.
Ack.
>
> I thought about parameterized Makefile.am and a catalog.xml.in that
> overwrite both files from the repo (used by cygwin) if --with-fop=xxx
> --with-docbook=yyy options are passed to ./configure. What the
> --with-fop option should look for is fop, xlstproc and xmllint, the
> other one locates the dtds.
>
I'm currently thinking of splitting (after the 0.99.5 release) the current Makefile into our usual triple:
- Makefile.am (well, keeping the Makefile for now and including things from Makefile.common, as I don't know the .am files well)
- Makefile.common
- Makefile.nmake
This would have some advantages:
a) Makefile.nmake can read settings from config.nmake (instead of currently having two places to configure - as that's *really* odd)
b) I guess Makefile.am would be easier to work with
c) it looks the same as in other dirs - therefore it might be easier to understand
d) Win32 won't need cygwin's GNU make to build (one dependency gone)
When I implemented the initial Makefile long ago, I thought it was a good idea to generally have a single Makefile for all platforms and the experimental docbook would be a good place to start.
In the meantime I got the feeling that it wasn't such a good idea. The differences between UNIX and Win32(even under cygwin) are just not ignorable and especially a) really annoys me.
Regards, ULFL
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066