> > One area I would be interested in seeing some thoughts from you Dave is > > on how to structure the XML toolchain and build. Doug has a recommended > > XSLT engine and a Makefile in the sandbox, but these things are a bit > > outside the boost norm. The other day I got motivated to start trying out > > Doug's stuff, but I got bogged down in the usual Open Source > > issue of successfully downloading and installing Doug's recommended > > toolset (still haven't got it working). > > Which platform? What kind of problems are you running into?
Mandrake Linux 9. Finding a compatible download. Compile and dependency issues. As I said, the usual stuff... > > So I was thinking about > > moving over to the Apache toolset (which I am more used to) instead > > just too get going. But then I have to modify the makefiles etc... > > I've run across more than a few comments that Xalan has a few bugs > that the DocBook XSL stylesheets trigger. Entirely possible. > > In the long run I would imagine we would want to treat XSLT engines > > just like C++ compilers -- have Jam configurations and Jam targets > > etc. and possibly even a list of tools that have been tried. I'm > > assuming we will be able to do this without modifing bjam, but > > given that my knowledge of the innerworkings of Jam is minimal > > I'm not certain what all is involved... > > > > Jeff > > If you're already running into problems with the Makefiles (and, of > course, they won't work on Win32), perhaps a Jam-based solution should be Well, they would probably work under cygwin where I already have an operational version of Xalan. I might give that a whirl over the weekend. Jeff ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
