| Newsgroups |
gmane.comp.video.gimp.windows.devel |
| Message-ID |
<[email protected]> |
Opps. All I needed to do was look under the Database link to find the
solution to my problem (I needed the -mno-cygwin and -fnative-struct
flags).
In my own defence, I did try to do some browsing of the message log
before posting, but because I wasn't a yahoo member, I never saw the faq.
-Sven
--- In [email protected], "sven2178 <sven2178@y...>"
<sven2178@y...> wrote:
> So I would like to be able to compile a plugin for wingimp under
> windows 2k.
>
> I downloaded all the release and development packages off Tor's site,
> and installed them as suggested. I also grabbed the gimp source, so
> that I would have a body of example plugin code to look at.
>
> Next I took the colortoalpha.c and config.h.win32 files from Tor's
> gimp src, put them in a dev dir, and wrote a little makefile using
> output from pkg-config and gimptool:
>
> colortoalpha.exe : colortoalpha.o
> gcc -o colortoalpha.exe colortoalpha.o -Lc:/gimplibs/lib -lgimpui
> -lgimp -lgtk -lgdk -lgmodule-2.0 -lglib-2.0 -lintl -liconv
>
> colortoalpha.o : colortoalpha.c
> gcc -c colortoalpha.c -Ic:/gimplibs/lib/gtk+/include
> -Ic:/gimplibs/include/glib-2.0 -Ic:/gimplibs/lib/glib-2.0/include
> -Ic:/gimplibs/include
>
> If I try to compile this calling make from the dos shell, I get the
> following error:
> ld: cannot open -lgimpui: No such file or directory
>
> However, if I call make from cygwin's bash shell, the plugin compiles
> without complaints. But when I replace the colortoalpha.exe in the
> plugin directory with my version, colortoalpha crashes when I try to
> call it from gimp
> --The instruction at "0x6dcf2600" referenced memory at
> "0x000000062".
> The memory could not be "read".
>
> My first thought was that I might somehow be invoking the wrong
> version of gcc from the cygwin shell, but `gcc -v` prints out exactly
> the same thing when I call it from both the dos shell and cygwin:
> Reading specs from c:gcc-2.95.2bin..libgcc-libi386-mingw322.95.2specs
>
> Does anyone have any idea what might be going wrong?
> (I've tried adding the -mwindows -mcpu=pentium -mms-bitfields -O2
> flags to my LFLAGS as suggested by an earlier post. But it didn't
> help. I also tried switching pentium to athlon (my own cpu type) but
> that failed as well.)
>
> -Sven
To Post a message, send it to: [email protected]
To Unsubscribe, send a blank message to: [email protected]
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/