Just to share that I was able to build all the pdf/html files with MacPorts under MacOs High Sierra. My version of FOP is old (v1.1) but it worked. P.O., thank you for the very clear instructions, it was easy to follow. It took 1 hour 10 min on my old laptop Mid 2010.
I had just to put in comment this line: export XML_CATALOG_FILES=/usr/local/etc/xml/catalog in doc2fo.sh and doc2html.sh because the variable is already defined and its value is different for MacPorts. I switched to Gil’s toolkit because rexxpg and rexxref no longer build with Publican (at least for me). Gil, thank you for this toolkit. The section "DocBook DTD and Style Sheets” in sources.txt gives interesting informations. I tested the setup under Windows. The URL for FOP seems not working, don’t know if it”s temporary. I replaced it with https://archive.apache.org/dist/xmlgraphics/fop/binaries/ Jean-Louis > On 19 May 2020, at 19:56, P.O. Jonsson <oor...@jonases.se> wrote: > > Dear developers, > > I have ported Gils tools for building the documentation to macOS and to > Ubuntu Linux. > > I have followed Gil´s logics as far as I could and the names of the scripts > are in essence the same and the way to use them as well. > > For macOS I could make the build run on local files so it is just as fast as > the Windows version. For Ubuntu I failed this so the Ubuntu version rely on > an internet connection and is substantially slower. But the output for PDF > and HTML is (as far as I can judge) identical for all three build processes. > So at least this constitutes a proof of concept for building on all platforms. > > Different from on Windows it was not possible for me to make a self-contained > version of the build tools, neither on macOS nor on Linux. I have set out > what tools need to be installed in a file WhatISHere.txt and explained how to > install them + I have briefly explained he build process. Since the readme > for Windows is so complete I refer to it for the deeper understanding of the > build process. > > Further I have set up a Dropbox folder Jenkinsshare > <https://www.dropbox.com/sh/uv5j1w6h5tioi2y/AACTceDdBkAGDCeguXk0fP6aa?dl=0> > where I have put zipped copies of the scripts. To try them out copy either > one of oorexxdocs-macOS.zip or oorexxdocs-Ubuntu.zip to a local folder, unzip > and follow the instructions in WhatIsHere.txt. Feedback is welcome. > > Jenkinsshare > <https://www.dropbox.com/sh/uv5j1w6h5tioi2y/AACTceDdBkAGDCeguXk0fP6aa?dl=0> > also contains 3 complete sets of the documentation (Win/macOS/Ubuntu Linux), > please have a look and let us know what you think. > > Jenkinsshare is intended as a platform for sharing files during development. > Gil, myself and Rony use it for sharing work on the documentation. > JenkinsShare is owned by Jenkins and present on the master and my Jenkins > slaves. Any developer who wants permanent access can send me a mail and I > will set it up. It is NOT a replacement for SVN/Sourceforge, just a quick way > of sharing data. Since the folder is shared by many I ask you to be moderate > when putting data there. > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se <mailto:oor...@jonases.se> > > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
