denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] A useful looking link for cross compiling... Re: gtk-


From: Richard Shann
Subject: Re: [Denemo-devel] A useful looking link for cross compiling... Re: gtk-app-devel-list Digest, Vol 105, Issue 20
Date: Mon, 04 Feb 2013 12:34:21 +0000

On Sun, 2013-02-03 at 14:09 -0600, Jeremiah Benham wrote:
> You can. Its all up there.
I have built the mxe default packages, which succeeded, and then added
the files I could see that you had extra into src and replaced
index.html with your version (as it seems, reading the Makefile that
this file is what is used to specify what can be built).
With this make denemo downloaded and built portmidi, downloaded
fluidsynth and the could not link

The failing link line was this:

libtool: link: i686-pc-mingw32-gcc -mms-bitfields -O2
-fomit-frame-pointer -funroll-all-loops -finline-functions -Wall -W
-Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align
-Wstrict-prototypes -Winline -Wno-unused-parameter -Wno-cast-qual
-Wl,--as-needed -o fluidsynth.exe
fluidsynth-fluidsynth.o  ./.libs/libfluidsynth.a -lreadline
-L/home/rshann/mxe/usr/i686-pc-mingw32/lib 
/home/rshann/mxe/usr/i686-pc-mingw32/lib/libportaudio.a -lwinmm -ldsound 
/home/rshann/mxe/usr/i686-pc-mingw32/lib/libgthread-2.0.a 
/home/rshann/mxe/usr/i686-pc-mingw32/lib/libglib-2.0.a -lws2_32 -lole32 
-lshlwapi /home/rshann/mxe/usr/i686-pc-mingw32/lib/libpcre.a 
/home/rshann/mxe/usr/i686-pc-mingw32/lib/libintl.a 
/home/rshann/mxe/usr/i686-pc-mingw32/lib/libiconv.a -lpthread
fluidsynth-fluidsynth.o:fluidsynth.c:(.text+0x41): undefined reference
to `_imp__new_fluid_cmd_handler'


There is no patch for fluidsynth (right?). Is the flag --disable-realine
in fluidsynth.mk a typo for --disable-readline?


>  I had to cp and rename evince's pkg-config file but that should be
> all you have to do other then patches.

Can you give more detail here? Copying pkg-config from where to where?
(Not that I have hit that yet)

Richard



>  The patches are in the src dir named like this
> evince-1-descrption.patch. the system knows it is to be patched simply
> by the presence of the patch file.
> 
> Jeremiah
> 
> On Feb 3, 2013 11:04 AM, "Richard Shann" <address@hidden>
> wrote:
>         On Sun, 2013-02-03 at 10:38 -0600, Jeremiah Benham wrote:
>         > Yes. Evince required a few patches to get compiled.
>         That's fantastic news! I take it the files like
>         http://denemo.org/~jjbenham/mxe/src/evince.mk
>         
>         are the ones you have developed to do this? Shall I try to
>         repeat the
>         build on my machine and then I can copy them across to some
>         windows
>         machines and test them?
>         
>         >  Would I look into using nsis now or would I put everyhing
>         into a
>         > zipped directory?
>         For testing we can just zip them, I would guess nsis will be
>         the easiest
>         way of getting something we can give users.
>         
>         Richard
>         
>         





reply via email to

[Prev in Thread] Current Thread [Next in Thread]