Re: [Denemo-devel] Release 2.2

[Jeremiah Benham]

I was able to compile evince with minimal patching. I can set the backends directory with an environment variable. I have all the dependencies built. Now I build denemo. I will probably have to patch denemo for the environt variable to be set.

Jeremiah

On Jul 12, 2017 12:19 PM, "Richard Shann" <address@hidden> wrote:

On Wed, 2017-07-12 at 11:39 -0500, Jeremiah Benham wrote:
> I have a hard time with this. In gub I can upgrade gtk because it
> requires me to upgrade gettext. This dependency would not upgrade. It
> gave me an error about undefined symbols with __imp_ . There was a
> bunch of these. I goggled it and had something to did not find a
> working solution. If I was able to upgrade mingw-w64, I may be able to
> get this to compile. Unfortunately mingw-w64 is like "wired" up into
> gubs framework making it very difficult (for me anyway) to upgrade.
> In MXE, I have everything compile but Evince, and fluidsynth. Evince
> needs poppler to compile but I need to fix it because it is installing
> in the wrong directory.  I have not written a MXE make file for
> librubberband yet. I may have started it.
>
>
> In Windows msys2, I managed to compile most of denemo's dependencies
> but the problems was the files were mixed up on different prefixes
> (mingw64/usr/lib vs. msys/usr/lib etc...)  and not always compatible
> with each other. This means I would have to find all the make files
> and get them to compile for mingw-w64. This is what is needed for
> distribution. It will compile with msys2 libs but this, according to
> the docs, is not suitable for distribution.
>
>
> I am currently back to working on MXE.

That sounds tough ... libevince is the most worrying, as it has some way
of finding the PDF backend which may not work even when it is built on
MXE :(

Richard