Brian, How did you get po4a to build? I tried everything I could think of (I'm no Perl expert so take that with the appropriate grain of salt) but no luck. I did manage to get the some of the dependencies to build using msys2 but po4a is still giving me grief. I would rather not have to install externally built binary if I don't have to.
Thanks, Wayne On 4/17/2015 6:07 PM, Brian Sidebotham wrote: > I'm nearly ready for a pull request. I've just committed changes to my > repo so that PDF and HTML can be built on Windows and Linux. > > Both dblatex and FOP are supported for PDF generation on Linux and > Windows, however I cannot get the dblatex PDF build to complete on > Windows because of a problem with the xlstproc I'm using. Perhaps > someone will have better luck than me. Because of that, I've noted in > cmake-readme.adoc in my repo that only FOP is suppored under Windows. > > CMake just does feature checking, not platform checking, so you can > give anything that's supported a go. Getting the full dblatex tool > chain seutp on Windows is a bit of a pain! > > Best Regards, > > Brian. > > On 14 April 2015 at 00:52, Nick Østergaard <oe.n...@gmail.com> wrote: >> Great. >> >> Den 13/04/2015 22.57 skrev "Brian Sidebotham" <brian.sidebot...@gmail.com>: >>> >>> I sync'd with Marco's repo so that's now reflected in my repo. >>> >>> I just need to do the po update stuff I think and then I'll do a pull >>> request to get the repo's aligned. >>> >>> Best Regards, >>> >>> Brian. >>> >>> On 12 April 2015 at 23:12, Nick Østergaard <oe.n...@gmail.com> wrote: >>>> I have now done this. >>>> >>>> 2015-04-11 13:48 GMT+02:00 Nick Østergaard <oe.n...@gmail.com>: >>>>> So now is a good time to remove the src/markdown and src/rest and move >>>>> src/asciidoc to src? >>>>> >>>>> If so, I can do that now, such that you can pull those changes. >>>>> >>>>> 2015-04-11 13:43 GMT+02:00 Brian Sidebotham >>>>> <brian.sidebot...@gmail.com>: >>>>>> On 11 April 2015 at 12:32, Brian Sidebotham >>>>>> <brian.sidebot...@gmail.com> wrote: >>>>>>> On 11 April 2015 at 12:11, Nick Østergaard <oe.n...@gmail.com> wrote: >>>>>>>> Great. I just looked briefly on the cmake setup. It seems to me like >>>>>>>> you intend to include a CMakeLists.txt inside each doc dir with the >>>>>>>> only change being the name or path of the root adoc file. Would it >>>>>>>> not >>>>>>>> mere more sense to have a common CMakeLists.txt in the src/asciidoc >>>>>>>> dir (to be renamed just src when we remove the markdown and rest >>>>>>>> variants), which searches the folders or is just given an array of >>>>>>>> root doc files? >>>>>>>> >>>>>>> >>>>>>> Things will change, I've just begun the start of adding macros to >>>>>>> create pdf and html targets. There's plenty more work to do yet. >>>>>>> Certainly there'll be a lot of common code that can be shared through >>>>>>> higher level cmake files. >>>>>>> >>>>>> >>>>>> The initial plan was to get CvPcb translation and generation complete. >>>>>> Once the repo achieves that, I can pull request it into Marco's repo >>>>>> and then hopefully there'll be plenty of resource to complete the >>>>>> CMake stuff, then Marco's repo will come under the KiCad umbrella. >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> Brian. > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
