On Thu, Feb 14, 2013 at 11:45 AM, Richard Shann <richard.sh...@virgin.net>wrote:
> I just found the backends that are built, and copied them across. Now > evince complains that libpdfdocument.dll is not found - it is looking in > the right place, but of course we have > > ~/mxe/usr/i686-pc-mingw32/lib/evince/3/backends$ ls -l > total 212 > -rw-r--r-- 1 rshann rshann 202016 Feb 14 16:48 libpdfdocument.a > -rwxr-xr-x 1 rshann rshann 3202 Feb 14 16:48 libpdfdocument.la > -rw-r--r-- 1 rshann rshann 3535 Feb 14 16:48 pdfdocument.evince-backend > > Any thoughts - can we generate the .dll instead (we already have > fluidsynth.dll and that is causing no problem). > > Maybe we will have to patch the Makefile in the evince/backends/pdf (I am not sure on that path spelling) to tell it to create a .dll or something. I don't know. We should probably ask the evince people. Mac Os X using gub and linux using gub had the same problems. Mingw using gub was always working. Jeremiah > Richard > > > On Thu, 2013-02-14 at 17:18 +0000, Richard Shann wrote: > > On Thu, 2013-02-14 at 17:03 +0000, Richard Shann wrote: > > > On Thu, 2013-02-14 at 09:42 -0600, Jeremiah Benham wrote: > > > > > > > > I have tested it, but > > > > cannot get it to fire off from denemo - it is not at all > > > > obvious where > > > > glib will look for the helper program with a static build, it > > > > doesn't > > > > seem to find it in the path, and we don't have a .dll, though > > > > if we did > > > > it would be where I have put gspawn_win32_helper.exe, ie > where > > > > denemo.exe is and fluidsynth.dll, in the bin directory. > > > > > > This is fixed now - it turns out there are two helper functions the > > > other one is called gspawn_win32_helper-console.exe and that is also > > > built by mxe and once I installed that all was well. > > > Now LilyPond is crashing, but that will be because it is being found in > > > an old Denemo installation without its data path being set up before it > > > is called. Either we need to combine the two builds or build LilyPond > on > > > mxe (yikes!) or leave it to the user to do a standard LilyPond install > > > from the LilyPond website. > > > > Now I have LilyPond successfully completing, but the evince build is > > incomplete - it cannot load pdf files :( > > The evince build recipe is something you have generated Jeremiah - I > > expect you have built something that I have not copied across, some sort > > of backend module? I think I just copied everything that was > > bin/*evince* ... > > or is it that some pdf backend is not built? > > > > Richard > > > > >
_______________________________________________ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel
