Sign up now! · Forgot password?
RSS/Atom feed identi.ca Twitter

Windows development

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

6 of 6 messages available
Toggle history

Please log in to manage your subscriptions.

Windows development Jasper van de Gronde 04 May 08:50
  Windows development Victor Oliveira 05 May 07:52
   Windows development gfxuser 05 May 08:32
    Windows development Victor Oliveira 06 May 22:37
     Windows development Jasper van de Gronde 08 May 17:32
      Windows development Victor Oliveira 08 May 21:04
Jasper van de Gronde
2012-05-04 08:50:19 UTC (almost 2 years ago)

Windows development

Hi,

I'm at LGM and having problems compiling GEGL on windows. Does anyone have experience with this? Or are there prebuilt libraries available that I could use? (Ideally I'd like to also be able to compile it myself, but for some initial experimentation prebuilt libraries would be fine.)

I'm using MSYS btw, and have installed quite a few dependencies, but am now stuck on m4 (perhaps the wrong version is available, it doesn't recognize the --gnu flag).

- Jasper

Victor Oliveira
2012-05-05 07:52:57 UTC (almost 2 years ago)

Windows development

Hi Jasper!

I really don't recommend you compiling it in Windows (it's slow and full of bugs). You should do cross-compiling in Linux. Have you tried that?

I can send some scripts I have if you like.

On Fri, May 4, 2012 at 10:50 AM, Jasper van de Gronde < th.v.d.gronde@hccnet.nl> wrote:

Hi,

I'm at LGM and having problems compiling GEGL on windows. Does anyone have experience with this? Or are there prebuilt libraries available that I could use? (Ideally I'd like to also be able to compile it myself, but for some initial experimentation prebuilt libraries would be fine.)

I'm using MSYS btw, and have installed quite a few dependencies, but am now stuck on m4 (perhaps the wrong version is available, it doesn't recognize the --gnu flag).

- Jasper

_______________________________________________ gegl-developer-list mailing list
gegl-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gegl-developer-list

gfxuser
2012-05-05 08:32:22 UTC (almost 2 years ago)

Windows development

On 05/05/2012 at 09:52 Victor Oliveira wrote:

I really don't recommend you compiling it in Windows (it's slow and full of bugs). You should do cross-compiling in Linux.

Hi Victor,

could you please put a finer point on this? Is this for GEGL only or for GIMP, too? Which tools do you use in Windows? Mitch regretfully noticed in a bug report lately that there are no Windows developers for GIMP. Maybe your informations could help to bring more Windows developers into the project.

Best regards,

grafxuser

Victor Oliveira
2012-05-06 22:37:59 UTC (almost 2 years ago)

Windows development

As far as I know, there are really few Windows developers for GIMP (one or two?), basically, all development is done on Linux and because of that, Windows-only problems are discovered just at the end of the release cycle.

I spent a long time trying to discover how to compile GIMP in Windows, even though I'm a Linux developer, I needed to run it in Windows for my OpenCL work because my GPU doesn't have a Linux driver.

At first, I tried to use MinGW+MSYS in Windows, it worked, but it is _extremely_ slow... like 3~4 hours to build GIMP and dependencies. Also, it had some random bugs.

Much better is to use mingw-w64 in Linux to build Windows binaries.

Anyway, here is what I've been doing.

System: Ubuntu 12.04LST

1. Install mingw-w64 2. use the grab-stuff.sh script (from Ender) to download precompiled packages from OpenSUSE repositories, change your prefix in the script 3. What we need will be extracted to ./usr/x86_64-w64-mingw32/sys-root/mingw 4. set your environment vars like the env.sh file (change to your directories)

5. get babl, gegl and gimp from git and build it:

$ cd babl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no ; make ; make install

$ cd gegl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no --disable-docs; make ; make install

$ cd gimp $ ./configure --prefix=$PREFIX --without-dbus --without-gudev --without-linux-input --without-xmc --disable-python --host=x86_64-w64-mingw32 --without-libjpeg; make ; make install

I had problems with a -pthreads flag (which breaks mingw), it seems my system was polluted and I had a autotools file somewhere including it, I couldn't find the file. so my brute force solution was to have an Ubuntu VM with a clean system :/

and that's it...

bye! Victor

On Sat, May 5, 2012 at 10:32 AM, gfxuser wrote:

On 05/05/2012 at 09:52 Victor Oliveira wrote:

I really don't recommend you compiling it in Windows (it's slow and full of bugs). You should do cross-compiling in Linux.

Hi Victor,

could you please put a finer point on this? Is this for GEGL only or for GIMP, too? Which tools do you use in Windows? Mitch regretfully noticed in a bug report lately that there are no Windows developers for GIMP. Maybe your informations could help to bring more Windows developers into the project.

Best regards,

grafxuser

______________________________**_________________ gegl-developer-list mailing list
gegl-developer-list@gnome.org
http://mail.gnome.org/mailman/**listinfo/gegl-developer-list

Jasper van de Gronde
2012-05-08 17:32:35 UTC (almost 2 years ago)

Windows development

Thanks for the info. This should get me at least a bit further. I might try using a LiveCD or something to cross-compile. Again thanks for the information.

BTW, did you do your Windows experiment using the "normal" mingw, or using TDM's GCC?

On 2012-05-07 00:37, Victor Oliveira wrote:

As far as I know, there are really few Windows developers for GIMP (one or two?), basically, all development is done on Linux and because of that, Windows-only problems are discovered just at the end of the release cycle.

I spent a long time trying to discover how to compile GIMP in Windows, even though I'm a Linux developer, I needed to run it in Windows for my OpenCL work because my GPU doesn't have a Linux driver.

At first, I tried to use MinGW+MSYS in Windows, it worked, but it is _extremely_ slow... like 3~4 hours to build GIMP and dependencies. Also, it had some random bugs.

Much better is to use mingw-w64 in Linux to build Windows binaries.

Anyway, here is what I've been doing.

System: Ubuntu 12.04LST

1. Install mingw-w64 2. use the grab-stuff.sh script (from Ender) to download precompiled packages from OpenSUSE repositories, change your prefix in the script 3. What we need will be extracted to ./usr/x86_64-w64-mingw32/sys-root/mingw 4. set your environment vars like the env.sh file (change to your directories)

5. get babl, gegl and gimp from git and build it:

$ cd babl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no ; make ; make install

$ cd gegl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no --disable-docs; make ; make install

$ cd gimp $ ./configure --prefix=$PREFIX --without-dbus --without-gudev --without-linux-input --without-xmc --disable-python --host=x86_64-w64-mingw32 --without-libjpeg; make ; make install

I had problems with a -pthreads flag (which breaks mingw), it seems my system was polluted and I had a autotools file somewhere including it, I couldn't find the file. so my brute force solution was to have an Ubuntu VM with a clean system :/

and that's it...

bye! Victor

On Sat, May 5, 2012 at 10:32 AM, gfxuser > wrote:

On 05/05/2012 at 09:52 Victor Oliveira wrote:

I really don't recommend you compiling it in Windows (it's slow and full of bugs). You should do cross-compiling in Linux.

Hi Victor,

could you please put a finer point on this? Is this for GEGL only or for GIMP, too? Which tools do you use in Windows? Mitch regretfully noticed in a bug report lately that there are no Windows developers for GIMP. Maybe your informations could help to bring more Windows developers into the project.

Best regards,

grafxuser

_______________________________________________ gegl-developer-list mailing list gegl-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gegl-developer-list

_______________________________________________ gegl-developer-list mailing list
gegl-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gegl-developer-list

Victor Oliveira
2012-05-08 21:04:27 UTC (almost 2 years ago)

Windows development

On Tue, May 8, 2012 at 7:32 PM, Jasper van de Gronde < th.v.d.gronde@hccnet.nl> wrote:

Thanks for the info. This should get me at least a bit further. I might try using a LiveCD or something to cross-compile. Again thanks for the information.

BTW, did you do your Windows experiment using the "normal" mingw, or using TDM's GCC?

The "normal" one :p

On 2012-05-07 00:37, Victor Oliveira wrote:

As far as I know, there are really few Windows developers for GIMP (one or two?), basically, all development is done on Linux and because of that, Windows-only problems are discovered just at the end of the release cycle.

I spent a long time trying to discover how to compile GIMP in Windows, even though I'm a Linux developer, I needed to run it in Windows for my OpenCL work because my GPU doesn't have a Linux driver.

At first, I tried to use MinGW+MSYS in Windows, it worked, but it is _extremely_ slow... like 3~4 hours to build GIMP and dependencies. Also, it had some random bugs.

Much better is to use mingw-w64 in Linux to build Windows binaries.

Anyway, here is what I've been doing.

System: Ubuntu 12.04LST

1. Install mingw-w64 2. use the grab-stuff.sh script (from Ender) to download precompiled packages from OpenSUSE repositories, change your prefix in the script 3. What we need will be extracted to ./usr/x86_64-w64-mingw32/sys-root/mingw 4. set your environment vars like the env.sh file (change to your directories)

5. get babl, gegl and gimp from git and build it:

$ cd babl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no ; make ; make install

$ cd gegl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no --disable-docs; make ; make install

$ cd gimp $ ./configure --prefix=$PREFIX --without-dbus --without-gudev --without-linux-input --without-xmc --disable-python --host=x86_64-w64-mingw32 --without-libjpeg; make ; make install

I had problems with a -pthreads flag (which breaks mingw), it seems my system was polluted and I had a autotools file somewhere including it, I couldn't find the file. so my brute force solution was to have an Ubuntu VM with a clean system :/

and that's it...

bye! Victor

On Sat, May 5, 2012 at 10:32 AM, gfxuser wrote:

On 05/05/2012 at 09:52 Victor Oliveira wrote:

I really don't recommend you compiling it in Windows (it's slow and full of bugs). You should do cross-compiling in Linux.

Hi Victor,

could you please put a finer point on this? Is this for GEGL only or for GIMP, too? Which tools do you use in Windows? Mitch regretfully noticed in a bug report lately that there are no Windows developers for GIMP. Maybe your informations could help to bring more Windows developers into the project.

Best regards,

grafxuser

_______________________________________________ gegl-developer-list mailing list
gegl-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gegl-developer-list

_______________________________________________ gegl-developer-list mailing listgegl-developer-list@gnome.orghttp://mail.gnome.org/mailman/listinfo/gegl-developer-list