kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

On 18 April 2015 at 17:36, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
> 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
>

Hi Wayne,

The "trick" is not to build po4a because it's not required to be
built. So long as po4a is in your path, kicad-doc's FindPO4A will be
able to find it and use it.

I found the easiest thing to do is not to install po4a as a perl
module, but rather just run it with the perl interpreter from source.
The only dependency it requires for us to use it is Unicode:GCString;
You must install that perl module using cpan or similar.

Once that dependency is in place, you can simply run the po4a utilities like so:

    perl -IC:/path/to/po4a/lib po4a

That's what we do in the kicad-doc CMake. In msys2, perhaps you want
to do a helper script in /usr/bin or something that as having the po4a
source directory in your PATH may seem a bit odd, whereas in Windows
the PATH variable is usually just full of this sort of junk! ;)

By the way, I too spent a few days trying to get it to build properly
on Windows, using various versions of Perl, but with no luck until I
had the epiphany of not building it!

For dblatex, please see the appropriate notes in
https://github.com/BrianSidebotham/kicad-doc/blob/master/cmake-readme.adoc

Best Regards,

Brian.