That's great drawoc!

Any chance you have any writeup/info on how to setup to run this locally? Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc

This is awesome work :)

On Fri, Aug 10, 2012 at 5:25 PM, drawoc wrote:

I just added a README to the github repository in my first email.

Let me know if the scripts give you any trouble.

-- drawoc

On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala wrote:

That's great drawoc!

Any chance you have any writeup/info on how to setup to run this locally? Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Hello drawoc,

On Thu, 9 Aug 2012 16:09:51 -0400 drawoc wrote:

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

Thanks a bunch for this!

Regards,

wwp

Thanks drawoc!

I'm running into some problems that I'm trying to work through but perhaps you or someone else has run into this before and can point me in the right direction (or point out what's wrong with my setup)...

Here's the error and afterwards I have listed all the steps I have taken to try to get my environment to be able to run the build script:

Jari@Jari-PC /gimp $ build
I: unknown keys defined in configuration file: mingw_tool_prefix, mingw_tools, searchprefix, fullpath_tool, flavour_cfla gs, module, tool, flavour_opt, flavour, mingw_tools_args, flavour_ext Traceback (most recent call last):
File "C:/mingw/msys/1.0/bin/jhbuild", line 31, in jhbuild.main.main(sys.argv[1:])
File "C:/mingw/msys/1.0/jhbuild\jhbuild\main.py", line 130, in main config = jhbuild.config.Config(options.configfile) File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 205, in __init__ self.setup_env()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 429, in setup_env get_stderr = False).strip()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\cmds.py", line 63, in get_output
**kws)
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\subprocess_win32.py", line 112, in __init__
elif not command[0].endswith('.exe') or kws['shell']: KeyError: 'shell'

1. Install mingw, choose latest packages, c/c++ compiler, msys and developer kit.

2. Install mingw64
http://mingw-w64.sourceforge.net/

Choose the latest w32 build e.g. mingw32-w32-bin_i686-mingw_xxxxxxxx.zip http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Wi n32/Automated%20Builds/

Extract it to your machine on top of mingw, e.g. c:\mingw

3. Install Python27 Add python to your path (msys/1.0/etc/profile): export PATH="$PATH:/c/Python27"

4. Get some needed packages mingw-get.exe install msys-wget
mingw-get.exe install msys-openssl
mingw-get.exe install msys-unzip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config_0.26-1 _win32.zip
unzip pkg-config_0.26-1_win32.zip
rm pkg-config_0.26-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config-dev_0. 26-1_win32.zip
unzip pkg-config-dev_0.26-1_win32.zip rm pkg-config-dev_0.26-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnome-common -dev_2.28.0-1_win32.zip
unzip gnome-common-dev_2.28.0-1_win32.zip rm gnome-common-dev_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnome-common _2.28.0-1_win32.zip
unzip gnome-common_2.28.0-1_win32.zip rm gnome-common_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool-dev_0.4 0.4-1_win32.zip
unzip intltool-dev_0.40.4-1_win32.zip rm intltool-dev_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool_0.40.4- 1_win32.zip
unzip intltool_0.40.4-1_win32.zip
rm intltool_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib-dev_2.28.8-1_wi n32.zip
unzip glib-dev_2.28.8-1_win32.zip
rm glib-dev_2.28.8-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib_2.28.8-1_win32. zip
unzip glib_2.28.8-1_win32.zip
rm glib_2.28.8-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-runtime-d ev_0.18.1.1-2_win32.zip
unzip gettext-runtime-dev_0.18.1.1-2_win32.zip rm gettext-runtime-dev_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-runtime_0 .18.1.1-2_win32.zip
unzip gettext-runtime_0.18.1.1-2_win32.zip rm gettext-runtime_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-doc-utils/0.12/gnome-doc -utils-0.12.0.zip
unzip gnome-doc-utils-0.12.0.zip
rm gnome-doc-utils-0.12.0.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2-dev_2.7.7 -1_win32.zip
unzip libxml2-dev_2.7.7-1_win32.zip
rm libxml2-dev_2.7.7-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2_2.7.7-1_w in32.zip
unzip libxml2_2.7.7-1_win32.zip
rm libxml2_2.7.7-1_win32.zip

5. Adjust ACLOCAL_FLAGS export ACLOCAL_FLAGS="-I /share/aclocal"

6. Install msysgit to c:\git. When asked, choose the 'Use Git Bash only' option (avoid adding anything to the PATH). In the line ending conversions choice, pick "Checkout as-is, commit Unix-style line endings" Add git/bin to the end of your path (msys/1.0/etc/profile): export PATH="$PATH:/c/git/bin"

7. jhbuild needs to know shell location to be able to run it export SHELL=/bin/sh

8. Install jhbuild http://afuera.me.uk/jhbuild-windows/ git clone git://gitorious.org/jhbuild/jhbuild.git cd jhbuild
./autogen-sh (not sure if this is necessary) make -f Makefile.windows
make install
# create .jhbuildrc file as described on the jhbuild windows page jhbuild sanitycheck (mine is still complaining about gettext and xml catalog)
jhbuild bootstrap
jhbuild build (some failures here still with libxml2)

11. Get the gimp windows jhbuild https://github.com/drawoc/windows-gimp-jhbuild. Follow directions in README

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Friday, August 10, 2012 5:25 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I just added a README to the github repository in my first email.

Let me know if the scripts give you any trouble.

-- drawoc

On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala wrote:

That's great drawoc!

Any chance you have any writeup/info on how to setup to run this locally? Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Ah, that explains it :) I tried with the latest and I'm still getting the same problem.

There were a lot of issues discussed with jhbuild on Windows so I think I'll just get Linux running on a VM to save myself a lot of pain in the short and long run. I can retry this later when I'm more familiar with Gimp and the whole build process...

Do you have a recommendation on the flavor of Linux? Or on the setup in general? I'm 'ok' on Linux but definitely not an expert.

Thanks!!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 1:48 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Try this: Pull my latest changes from git, and then do: export PYTHON="/c/Python27/bin/python.exe" (I'm not sure where your python exe is, so change "/c/Python27/bin/python.exe" to the location of the actual exe) Then try running the script again.
Hopefully that will work.

As a side note, I've actually never successfully compiled the GIMP directly on windows before, only cross compiled for Windows from Linux. (So you're trying something new.)

-- drawoc

On Tue, Aug 14, 2012 at 1:27 PM, Jari Niskala wrote:

Thanks drawoc!

I'm running into some problems that I'm trying to work through but perhaps you or someone else has run into this before and can point me in the right direction (or point out what's wrong with my setup)...

Here's the error and afterwards I have listed all the steps I have taken to try to get my environment to be able to run the build script:

Jari@Jari-PC /gimp $ build
I: unknown keys defined in configuration file: mingw_tool_prefix, mingw_tools, searchprefix, fullpath_tool, flavour_cfla gs, module, tool, flavour_opt, flavour, mingw_tools_args, flavour_ext Traceback (most recent call last):
File "C:/mingw/msys/1.0/bin/jhbuild", line 31, in jhbuild.main.main(sys.argv[1:])
File "C:/mingw/msys/1.0/jhbuild\jhbuild\main.py", line 130, in main config = jhbuild.config.Config(options.configfile) File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 205, in

__init__

self.setup_env()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 429, in

setup_env

get_stderr = False).strip()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\cmds.py", line 63, in get_output
**kws)
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\subprocess_win32.py", line 112, in __init__
elif not command[0].endswith('.exe') or kws['shell']: KeyError: 'shell'

1. Install mingw, choose latest packages, c/c++ compiler, msys and developer kit.

2. Install mingw64 http://mingw-w64.sourceforge.net/

Choose the latest w32 build e.g. mingw32-w32-bin_i686-mingw_xxxxxxxx.zip http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targettin g%20Wi
n32/Automated%20Builds/

Extract it to your machine on top of mingw, e.g. c:\mingw

3. Install Python27 Add python to your path (msys/1.0/etc/profile): export PATH="$PATH:/c/Python27"

4. Get some needed packages mingw-get.exe install msys-wget
mingw-get.exe install msys-openssl
mingw-get.exe install msys-unzip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config_ 0.26-1
_win32.zip
unzip pkg-config_0.26-1_win32.zip
rm pkg-config_0.26-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config-dev_0.

26-1_win32.zip
unzip pkg-config-dev_0.26-1_win32.zip rm pkg-config-dev_0.26-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnome- common
-dev_2.28.0-1_win32.zip
unzip gnome-common-dev_2.28.0-1_win32.zip rm gnome-common-dev_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnome- common
_2.28.0-1_win32.zip
unzip gnome-common_2.28.0-1_win32.zip rm gnome-common_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool-d ev_0.4
0.4-1_win32.zip
unzip intltool-dev_0.40.4-1_win32.zip rm intltool-dev_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool_0 .40.4-
1_win32.zip
unzip intltool_0.40.4-1_win32.zip
rm intltool_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib-dev_2.28. 8-1_wi
n32.zip
unzip glib-dev_2.28.8-1_win32.zip
rm glib-dev_2.28.8-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib_2.28.8-1_win32.

zip
unzip glib_2.28.8-1_win32.zip
rm glib_2.28.8-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-run time-d
ev_0.18.1.1-2_win32.zip
unzip gettext-runtime-dev_0.18.1.1-2_win32.zip rm gettext-runtime-dev_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-run time_0
.18.1.1-2_win32.zip
unzip gettext-runtime_0.18.1.1-2_win32.zip rm gettext-runtime_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-doc-utils/0.12/gno me-doc
-utils-0.12.0.zip
unzip gnome-doc-utils-0.12.0.zip
rm gnome-doc-utils-0.12.0.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2-dev _2.7.7
-1_win32.zip
unzip libxml2-dev_2.7.7-1_win32.zip
rm libxml2-dev_2.7.7-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2_2.7 .7-1_w
in32.zip
unzip libxml2_2.7.7-1_win32.zip
rm libxml2_2.7.7-1_win32.zip

5. Adjust ACLOCAL_FLAGS export ACLOCAL_FLAGS="-I /share/aclocal"

6. Install msysgit to c:\git. When asked, choose the 'Use Git Bash only' option (avoid adding anything to the PATH). In the line ending conversions choice, pick "Checkout as-is, commit Unix-style line endings" Add git/bin to the end of your path (msys/1.0/etc/profile): export PATH="$PATH:/c/git/bin"

7. jhbuild needs to know shell location to be able to run it export SHELL=/bin/sh

8. Install jhbuild http://afuera.me.uk/jhbuild-windows/ git clone git://gitorious.org/jhbuild/jhbuild.git cd jhbuild
./autogen-sh (not sure if this is necessary) make -f Makefile.windows make install # create .jhbuildrc file as described on the jhbuild windows page jhbuild sanitycheck (mine is still complaining about gettext and xml
catalog)
jhbuild bootstrap
jhbuild build (some failures here still with libxml2)

11. Get the gimp windows jhbuild https://github.com/drawoc/windows-gimp-jhbuild. Follow directions in README

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Friday, August 10, 2012 5:25 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I just added a README to the github repository in my first email.

Let me know if the scripts give you any trouble.

-- drawoc

On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala

wrote:

That's great drawoc!

Any chance you have any writeup/info on how to setup to run this locally? Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Thanks Drawoc! I got my Linux Mint Debian running but I keep running into a problem when the jhbuild is trying to configre glib...:

configure: error: Could not find a glib-compile-resources in your PATH *** Error during phase configure of glib: ########## Error running ./configure --prefix /home/jari/windows-gimp-jhbuild/targets/gimp-dev/ --libdir '/home/jari/windows-gimp-jhbuild/targets/gimp-dev//lib' --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --disable-docs --enable-all-warnings --disable-static --enable-debug=no AR="/usr/bin/i686-w64-mingw32-ar" RANLIB="/usr/bin/i686-w64-mingw32-ranlib" STRIP="/usr/bin/i686-w64-mingw32-strip" AS="/usr/bin/i686-w64-mingw32-as" DLLTOOL="/usr/bin/i686-w64-mingw32-dlltool" OBJDUMP="/usr/bin/i686-w64-mingw32-objdump" NM="/usr/bin/i686-w64-mingw32-nm"
WINDRES="/usr/bin/i686-w64-mingw32-windres" --disable-gtk-doc --cache-file=/home/jari/windows-gimp-jhbuild/win32.cache *** [5/24]

Any ideas? I can see that glib-compile-resource.c is part of glib itself but it's not on my system. I can see other glib components there just fine such as glib-compile-schemas.

Thanks!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 5:29 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I run the scripts under Debian testing regularly, so if you choose Debian or one of its derivatives you shouldn't have a hard time.

If you're still fairly new to linux though, you probably want to go with something other than straight Debian. Linux Mint is my personal favorite of the more user-friendly distros (and it's debian-derived). http://www.linuxmint.com/
You might want to go with eg. the xfce version of mint as it should be faster than the cinnamon or mate based desktops.

Anyway, once you have one of those distros installed, you can install most of the required packages like this:
sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev

Then just follow the README in my git repo,

-- drawoc

On Tue, Aug 14, 2012 at 5:09 PM, Jari Niskala wrote:

Ah, that explains it :) I tried with the latest and I'm still getting the same problem.

There were a lot of issues discussed with jhbuild on Windows so I think I'll just get Linux running on a VM to save myself a lot of pain in the short and long run. I can retry this later when I'm more familiar with Gimp and the whole build process...

Do you have a recommendation on the flavor of Linux? Or on the setup in general? I'm 'ok' on Linux but definitely not an expert.

Thanks!!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 1:48 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Try this: Pull my latest changes from git, and then do: export PYTHON="/c/Python27/bin/python.exe" (I'm not sure where your python exe is, so change "/c/Python27/bin/python.exe" to the location of the actual exe) Then try running the script again.
Hopefully that will work.

As a side note, I've actually never successfully compiled the GIMP directly on windows before, only cross compiled for Windows from Linux. (So you're trying something new.)

-- drawoc

On Tue, Aug 14, 2012 at 1:27 PM, Jari Niskala

wrote:

Thanks drawoc!

I'm running into some problems that I'm trying to work through but perhaps you or someone else has run into this before and can point me in the right direction (or point out what's wrong with my setup)...

Here's the error and afterwards I have listed all the steps I have taken to try to get my environment to be able to run the build script:

Jari@Jari-PC /gimp $ build
I: unknown keys defined in configuration file: mingw_tool_prefix, mingw_tools, searchprefix, fullpath_tool, flavour_cfla gs, module, tool, flavour_opt, flavour, mingw_tools_args, flavour_ext Traceback (most recent call last):
File "C:/mingw/msys/1.0/bin/jhbuild", line 31, in jhbuild.main.main(sys.argv[1:])
File "C:/mingw/msys/1.0/jhbuild\jhbuild\main.py", line 130, in main config = jhbuild.config.Config(options.configfile) File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 205, in

__init__

self.setup_env()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 429, in

setup_env

get_stderr = False).strip()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\cmds.py", line 63, in get_output
**kws)
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\subprocess_win32.py", line 112, in __init__
elif not command[0].endswith('.exe') or kws['shell']: KeyError: 'shell'

1. Install mingw, choose latest packages, c/c++ compiler, msys and developer kit.

2. Install mingw64 http://mingw-w64.sourceforge.net/

Choose the latest w32 build e.g. mingw32-w32-bin_i686-mingw_xxxxxxxx.zip http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetti n
g%20Wi
n32/Automated%20Builds/

Extract it to your machine on top of mingw, e.g. c:\mingw

3. Install Python27 Add python to your path (msys/1.0/etc/profile): export PATH="$PATH:/c/Python27"

4. Get some needed packages mingw-get.exe install msys-wget
mingw-get.exe install msys-openssl
mingw-get.exe install msys-unzip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config _
0.26-1
_win32.zip
unzip pkg-config_0.26-1_win32.zip
rm pkg-config_0.26-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config-dev_0.

26-1_win32.zip
unzip pkg-config-dev_0.26-1_win32.zip rm pkg-config-dev_0.26-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnome -
common
-dev_2.28.0-1_win32.zip
unzip gnome-common-dev_2.28.0-1_win32.zip rm gnome-common-dev_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnome -
common
_2.28.0-1_win32.zip
unzip gnome-common_2.28.0-1_win32.zip rm gnome-common_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool- d
ev_0.4
0.4-1_win32.zip
unzip intltool-dev_0.40.4-1_win32.zip rm intltool-dev_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool_ 0
.40.4-
1_win32.zip
unzip intltool_0.40.4-1_win32.zip
rm intltool_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib-dev_2.28. 8-1_wi
n32.zip
unzip glib-dev_2.28.8-1_win32.zip
rm glib-dev_2.28.8-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib_2.28.8-1_win32.

zip
unzip glib_2.28.8-1_win32.zip
rm glib_2.28.8-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-ru n
time-d
ev_0.18.1.1-2_win32.zip
unzip gettext-runtime-dev_0.18.1.1-2_win32.zip rm gettext-runtime-dev_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-ru n
time_0
.18.1.1-2_win32.zip
unzip gettext-runtime_0.18.1.1-2_win32.zip rm gettext-runtime_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-doc-utils/0.12/gn o
me-doc
-utils-0.12.0.zip
unzip gnome-doc-utils-0.12.0.zip
rm gnome-doc-utils-0.12.0.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2-de v
_2.7.7
-1_win32.zip
unzip libxml2-dev_2.7.7-1_win32.zip
rm libxml2-dev_2.7.7-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2_2. 7
.7-1_w
in32.zip
unzip libxml2_2.7.7-1_win32.zip
rm libxml2_2.7.7-1_win32.zip

5. Adjust ACLOCAL_FLAGS export ACLOCAL_FLAGS="-I /share/aclocal"

6. Install msysgit to c:\git. When asked, choose the 'Use Git Bash only' option (avoid adding anything to the PATH). In the line ending conversions choice, pick "Checkout as-is, commit Unix-style line endings" Add git/bin to the end of your path (msys/1.0/etc/profile): export PATH="$PATH:/c/git/bin"

7. jhbuild needs to know shell location to be able to run it export SHELL=/bin/sh

8. Install jhbuild http://afuera.me.uk/jhbuild-windows/ git clone git://gitorious.org/jhbuild/jhbuild.git cd jhbuild
./autogen-sh (not sure if this is necessary) make -f Makefile.windows make install # create .jhbuildrc file as described on the jhbuild windows page jhbuild sanitycheck (mine is still complaining about gettext and xml
catalog)
jhbuild bootstrap
jhbuild build (some failures here still with libxml2)

11. Get the gimp windows jhbuild https://github.com/drawoc/windows-gimp-jhbuild. Follow directions in README

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Friday, August 10, 2012 5:25 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I just added a README to the github repository in my first email.

Let me know if the scripts give you any trouble.

-- drawoc

On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala

wrote:

That's great drawoc!

Any chance you have any writeup/info on how to setup to run this

locally?

Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Unfortunately I did catch that so no luck with that :)

It's really weird... I couldn't find anything obvious for it online either.

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Sunday, August 19, 2012 1:33 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Ah, in my last email, the command that said this:

sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev

was supposed to be all on one line, but it got automatically word-wrapped at some point.

As a result, it looks like you missed those last three packages, so just run this to install the missing packages as well: sudo apt-get install autoconf libtool libgtk2.0-dev

-- drawoc

On Sun, Aug 19, 2012 at 4:01 PM, Jari Niskala wrote:

Thanks Drawoc! I got my Linux Mint Debian running but I keep running into a problem when the jhbuild is trying to configre glib...:

configure: error: Could not find a glib-compile-resources in your PATH *** Error during phase configure of glib: ########## Error running ./configure --prefix /home/jari/windows-gimp-jhbuild/targets/gimp-dev/ --libdir '/home/jari/windows-gimp-jhbuild/targets/gimp-dev//lib' --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --disable-docs --enable-all-warnings --disable-static --enable-debug=no AR="/usr/bin/i686-w64-mingw32-ar"

RANLIB="/usr/bin/i686-w64-mingw32-ranlib"

STRIP="/usr/bin/i686-w64-mingw32-strip" AS="/usr/bin/i686-w64-mingw32-as" DLLTOOL="/usr/bin/i686-w64-mingw32-dlltool" OBJDUMP="/usr/bin/i686-w64-mingw32-objdump" NM="/usr/bin/i686-w64-mingw32-nm"
WINDRES="/usr/bin/i686-w64-mingw32-windres" --disable-gtk-doc --cache-file=/home/jari/windows-gimp-jhbuild/win32.cache *** [5/24]

Any ideas? I can see that glib-compile-resource.c is part of glib itself but it's not on my system. I can see other glib components there just fine such as glib-compile-schemas.

Thanks!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 5:29 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I run the scripts under Debian testing regularly, so if you choose Debian or one of its derivatives you shouldn't have a hard time.

If you're still fairly new to linux though, you probably want to go with something other than straight Debian. Linux Mint is my personal favorite of the more user-friendly distros (and it's debian-derived). http://www.linuxmint.com/
You might want to go with eg. the xfce version of mint as it should be faster than the cinnamon or mate based desktops.

Anyway, once you have one of those distros installed, you can install most of the required packages like this: sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev

Then just follow the README in my git repo,

-- drawoc

On Tue, Aug 14, 2012 at 5:09 PM, Jari Niskala

wrote:

Ah, that explains it :) I tried with the latest and I'm still getting the same problem.

There were a lot of issues discussed with jhbuild on Windows so I think I'll just get Linux running on a VM to save myself a lot of pain in the short and long run. I can retry this later when I'm more familiar with Gimp and the whole build process...

Do you have a recommendation on the flavor of Linux? Or on the setup in general? I'm 'ok' on Linux but definitely not an expert.

Thanks!!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 1:48 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Try this: Pull my latest changes from git, and then do: export PYTHON="/c/Python27/bin/python.exe" (I'm not sure where your python exe is, so change "/c/Python27/bin/python.exe" to the location of the actual exe) Then try running the script again.
Hopefully that will work.

As a side note, I've actually never successfully compiled the GIMP directly on windows before, only cross compiled for Windows from Linux. (So you're trying something new.)

-- drawoc

On Tue, Aug 14, 2012 at 1:27 PM, Jari Niskala

wrote:

Thanks drawoc!

I'm running into some problems that I'm trying to work through but perhaps you or someone else has run into this before and can point me in the right direction (or point out what's wrong with my setup)...

Here's the error and afterwards I have listed all the steps I have taken to try to get my environment to be able to run the build script:

Jari@Jari-PC /gimp $ build
I: unknown keys defined in configuration file: mingw_tool_prefix, mingw_tools, searchprefix, fullpath_tool, flavour_cfla gs, module, tool, flavour_opt, flavour, mingw_tools_args, flavour_ext Traceback (most recent call last):
File "C:/mingw/msys/1.0/bin/jhbuild", line 31, in jhbuild.main.main(sys.argv[1:])
File "C:/mingw/msys/1.0/jhbuild\jhbuild\main.py", line 130, in main config = jhbuild.config.Config(options.configfile) File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 205, in

__init__

self.setup_env()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 429, in

setup_env

get_stderr = False).strip()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\cmds.py", line 63, in get_output
**kws)
File
"C:/mingw/msys/1.0/jhbuild\jhbuild\utils\subprocess_win32.py", line 112, in __init__
elif not command[0].endswith('.exe') or kws['shell']: KeyError: 'shell'

1. Install mingw, choose latest packages, c/c++ compiler, msys and developer kit.

2. Install mingw64 http://mingw-w64.sourceforge.net/

Choose the latest w32 build e.g. mingw32-w32-bin_i686-mingw_xxxxxxxx.zip http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targett i
n
g%20Wi
n32/Automated%20Builds/

Extract it to your machine on top of mingw, e.g. c:\mingw

3. Install Python27 Add python to your path (msys/1.0/etc/profile): export PATH="$PATH:/c/Python27"

4. Get some needed packages mingw-get.exe install msys-wget
mingw-get.exe install msys-openssl
mingw-get.exe install msys-unzip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-confi g
_
0.26-1
_win32.zip
unzip pkg-config_0.26-1_win32.zip
rm pkg-config_0.26-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config-dev_0.

26-1_win32.zip
unzip pkg-config-dev_0.26-1_win32.zip rm pkg-config-dev_0.26-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnom e
-
common
-dev_2.28.0-1_win32.zip
unzip gnome-common-dev_2.28.0-1_win32.zip rm gnome-common-dev_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gnom e
-
common
_2.28.0-1_win32.zip
unzip gnome-common_2.28.0-1_win32.zip rm gnome-common_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool -
d
ev_0.4
0.4-1_win32.zip
unzip intltool-dev_0.40.4-1_win32.zip rm intltool-dev_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltool _
0
.40.4-
1_win32.zip
unzip intltool_0.40.4-1_win32.zip
rm intltool_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib-dev_2.28. 8-1_wi
n32.zip
unzip glib-dev_2.28.8-1_win32.zip
rm glib-dev_2.28.8-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib_2.28.8-1_win32.

zip
unzip glib_2.28.8-1_win32.zip
rm glib_2.28.8-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-r u
n
time-d
ev_0.18.1.1-2_win32.zip
unzip gettext-runtime-dev_0.18.1.1-2_win32.zip rm gettext-runtime-dev_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext-r u
n
time_0
.18.1.1-2_win32.zip
unzip gettext-runtime_0.18.1.1-2_win32.zip rm gettext-runtime_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-doc-utils/0.12/g n
o
me-doc
-utils-0.12.0.zip
unzip gnome-doc-utils-0.12.0.zip
rm gnome-doc-utils-0.12.0.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2-d e
v
_2.7.7
-1_win32.zip
unzip libxml2-dev_2.7.7-1_win32.zip
rm libxml2-dev_2.7.7-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2_2. 7
.7-1_w
in32.zip
unzip libxml2_2.7.7-1_win32.zip
rm libxml2_2.7.7-1_win32.zip

5. Adjust ACLOCAL_FLAGS export ACLOCAL_FLAGS="-I /share/aclocal"

6. Install msysgit to c:\git. When asked, choose the 'Use Git Bash only' option (avoid adding anything to the PATH). In the line ending conversions choice, pick "Checkout as-is, commit Unix-style line

endings"

Add git/bin to the end of your path (msys/1.0/etc/profile): export PATH="$PATH:/c/git/bin"

7. jhbuild needs to know shell location to be able to run it export SHELL=/bin/sh

8. Install jhbuild http://afuera.me.uk/jhbuild-windows/ git clone git://gitorious.org/jhbuild/jhbuild.git cd jhbuild
./autogen-sh (not sure if this is necessary) make -f Makefile.windows make install # create .jhbuildrc file as described on the jhbuild windows page jhbuild sanitycheck (mine is still complaining about gettext and xml
catalog)
jhbuild bootstrap
jhbuild build (some failures here still with libxml2)

11. Get the gimp windows jhbuild https://github.com/drawoc/windows-gimp-jhbuild. Follow directions in README

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Friday, August 10, 2012 5:25 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I just added a README to the github repository in my first email.

Let me know if the scripts give you any trouble.

-- drawoc

On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala

wrote:

That's great drawoc!

Any chance you have any writeup/info on how to setup to run this

locally?

Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Hi Drawoc,

Thanks for your help in this! I finally got it working although it ended up being on Ubuntu. The weird part was that for Ubuntu, the glib-compile-resources was there in the same package...

I also had to add some other mingw components etc but I'm now very happy to have a working build environment :)

Thanks again for your prompt and helpful responses!

Best regards, Jari Niskala
Mobile: (858) 449-8952

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Sunday, August 19, 2012 3:49 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Maybe libglib2.0-bin didn't install correctly? Try reinstalling it:
sudo apt-get install --reinstall libglib2.0-bin

-- drawoc

On Sun, Aug 19, 2012 at 4:57 PM, Jari Niskala wrote:

Unfortunately I did catch that so no luck with that :)

It's really weird... I couldn't find anything obvious for it online

either.

-----Original Message-----
From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Sunday, August 19, 2012 1:33 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Ah, in my last email, the command that said this:

sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev

was supposed to be all on one line, but it got automatically word-wrapped at some point.

As a result, it looks like you missed those last three packages, so just run this to install the missing packages as well: sudo apt-get install autoconf libtool libgtk2.0-dev

-- drawoc

On Sun, Aug 19, 2012 at 4:01 PM, Jari Niskala

wrote:

Thanks Drawoc! I got my Linux Mint Debian running but I keep running into a problem when the jhbuild is trying to configre glib...:

configure: error: Could not find a glib-compile-resources in your PATH
*** Error during phase configure of glib: ########## Error running ./configure --prefix
/home/jari/windows-gimp-jhbuild/targets/gimp-dev/ --libdir '/home/jari/windows-gimp-jhbuild/targets/gimp-dev//lib' --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --disable-docs --enable-all-warnings --disable-static --enable-debug=no AR="/usr/bin/i686-w64-mingw32-ar"

RANLIB="/usr/bin/i686-w64-mingw32-ranlib"

STRIP="/usr/bin/i686-w64-mingw32-strip"

AS="/usr/bin/i686-w64-mingw32-as"

DLLTOOL="/usr/bin/i686-w64-mingw32-dlltool" OBJDUMP="/usr/bin/i686-w64-mingw32-objdump" NM="/usr/bin/i686-w64-mingw32-nm"
WINDRES="/usr/bin/i686-w64-mingw32-windres" --disable-gtk-doc --cache-file=/home/jari/windows-gimp-jhbuild/win32.cache *** [5/24]

Any ideas? I can see that glib-compile-resource.c is part of glib itself but it's not on my system. I can see other glib components there just fine such as glib-compile-schemas.

Thanks!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 5:29 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I run the scripts under Debian testing regularly, so if you choose Debian or one of its derivatives you shouldn't have a hard time.

If you're still fairly new to linux though, you probably want to go with something other than straight Debian. Linux Mint is my personal favorite of the more user-friendly distros (and it's debian-derived). http://www.linuxmint.com/
You might want to go with eg. the xfce version of mint as it should be faster than the cinnamon or mate based desktops.

Anyway, once you have one of those distros installed, you can install most of the required packages like this: sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev

Then just follow the README in my git repo,

-- drawoc

On Tue, Aug 14, 2012 at 5:09 PM, Jari Niskala

wrote:

Ah, that explains it :) I tried with the latest and I'm still getting the same problem.

There were a lot of issues discussed with jhbuild on Windows so I think I'll just get Linux running on a VM to save myself a lot of pain in the short and long run. I can retry this later when I'm more familiar with Gimp and the whole build process...

Do you have a recommendation on the flavor of Linux? Or on the setup in general? I'm 'ok' on Linux but definitely not an expert.

Thanks!!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 1:48 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Try this: Pull my latest changes from git, and then do: export PYTHON="/c/Python27/bin/python.exe" (I'm not sure where your python exe is, so change "/c/Python27/bin/python.exe" to the location of the actual exe) Then try running the script again.
Hopefully that will work.

As a side note, I've actually never successfully compiled the GIMP directly on windows before, only cross compiled for Windows from Linux. (So you're trying something new.)

-- drawoc

On Tue, Aug 14, 2012 at 1:27 PM, Jari Niskala

wrote:

Thanks drawoc!

I'm running into some problems that I'm trying to work through but perhaps you or someone else has run into this before and can point me in the right direction (or point out what's wrong with my setup)...

Here's the error and afterwards I have listed all the steps I have taken to try to get my environment to be able to run the build script:

Jari@Jari-PC /gimp $ build
I: unknown keys defined in configuration file: mingw_tool_prefix, mingw_tools, searchprefix, fullpath_tool, flavour_cfla gs, module, tool, flavour_opt, flavour, mingw_tools_args, flavour_ext Traceback (most recent call last):
File "C:/mingw/msys/1.0/bin/jhbuild", line 31, in jhbuild.main.main(sys.argv[1:])
File "C:/mingw/msys/1.0/jhbuild\jhbuild\main.py", line 130, in main config = jhbuild.config.Config(options.configfile) File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 205, in

__init__

self.setup_env()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 429, in

setup_env

get_stderr = False).strip()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\cmds.py", line 63, in get_output
**kws)
File
"C:/mingw/msys/1.0/jhbuild\jhbuild\utils\subprocess_win32.py", line 112, in __init__
elif not command[0].endswith('.exe') or kws['shell']: KeyError: 'shell'

1. Install mingw, choose latest packages, c/c++ compiler, msys and developer kit.

2. Install mingw64 http://mingw-w64.sourceforge.net/

Choose the latest w32 build e.g. mingw32-w32-bin_i686-mingw_xxxxxxxx.zip http://sourceforge.net/projects/mingw-w64/files/Toolchains%20target t
i
n
g%20Wi
n32/Automated%20Builds/

Extract it to your machine on top of mingw, e.g. c:\mingw

3. Install Python27 Add python to your path (msys/1.0/etc/profile): export PATH="$PATH:/c/Python27"

4. Get some needed packages mingw-get.exe install msys-wget
mingw-get.exe install msys-openssl
mingw-get.exe install msys-unzip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-conf i
g
_
0.26-1
_win32.zip
unzip pkg-config_0.26-1_win32.zip
rm pkg-config_0.26-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config-dev_0.

26-1_win32.zip
unzip pkg-config-dev_0.26-1_win32.zip rm pkg-config-dev_0.26-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gno m
e
-
common
-dev_2.28.0-1_win32.zip
unzip gnome-common-dev_2.28.0-1_win32.zip rm gnome-common-dev_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gno m
e
-
common
_2.28.0-1_win32.zip
unzip gnome-common_2.28.0-1_win32.zip rm gnome-common_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltoo l
-
d
ev_0.4
0.4-1_win32.zip
unzip intltool-dev_0.40.4-1_win32.zip rm intltool-dev_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intltoo l
_
0
.40.4-
1_win32.zip
unzip intltool_0.40.4-1_win32.zip
rm intltool_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib-dev_2.28. 8-1_wi
n32.zip
unzip glib-dev_2.28.8-1_win32.zip
rm glib-dev_2.28.8-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib_2.28.8-1_win32.

zip
unzip glib_2.28.8-1_win32.zip
rm glib_2.28.8-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext- r
u
n
time-d
ev_0.18.1.1-2_win32.zip
unzip gettext-runtime-dev_0.18.1.1-2_win32.zip rm gettext-runtime-dev_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext- r
u
n
time_0
.18.1.1-2_win32.zip
unzip gettext-runtime_0.18.1.1-2_win32.zip rm gettext-runtime_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-doc-utils/0.12/ g
n
o
me-doc
-utils-0.12.0.zip
unzip gnome-doc-utils-0.12.0.zip
rm gnome-doc-utils-0.12.0.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2- d
e
v
_2.7.7
-1_win32.zip
unzip libxml2-dev_2.7.7-1_win32.zip rm libxml2-dev_2.7.7-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2_2. 7
.7-1_w
in32.zip
unzip libxml2_2.7.7-1_win32.zip
rm libxml2_2.7.7-1_win32.zip

5. Adjust ACLOCAL_FLAGS export ACLOCAL_FLAGS="-I /share/aclocal"

6. Install msysgit to c:\git. When asked, choose the 'Use Git Bash

only'

option (avoid adding anything to the PATH). In the line ending conversions choice, pick "Checkout as-is, commit Unix-style line

endings"

Add git/bin to the end of your path (msys/1.0/etc/profile): export PATH="$PATH:/c/git/bin"

7. jhbuild needs to know shell location to be able to run it export SHELL=/bin/sh

8. Install jhbuild http://afuera.me.uk/jhbuild-windows/ git clone git://gitorious.org/jhbuild/jhbuild.git cd jhbuild
./autogen-sh (not sure if this is necessary) make -f Makefile.windows make install # create .jhbuildrc file as described on the jhbuild windows page jhbuild sanitycheck (mine is still complaining about gettext and xml
catalog)
jhbuild bootstrap
jhbuild build (some failures here still with libxml2)

11. Get the gimp windows jhbuild https://github.com/drawoc/windows-gimp-jhbuild. Follow directions in README

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Friday, August 10, 2012 5:25 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I just added a README to the github repository in my first email.

Let me know if the scripts give you any trouble.

-- drawoc

On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala

wrote:

That's great drawoc!

Any chance you have any writeup/info on how to setup to run this

locally?

Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

FYI, for anyone new interested in getting this to work from scratch these are the minor adjustments I had to make to complete the compilation on Ubuntu:

1. Get latest Ubuntu with latest updates up and running (I used VirtualBox)

2. Install pre-reqs. I had to add the last 3 to get the compilation to finish on Ubuntu. The weird one was that the mingw-w64 package didn't include g++...
sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev g++-mingw-w64 intltool xsltproc

3. git clone https://github.com/drawoc/windows-gimp-jhbuild

4. Follow readme

During the installation I believe I had to manually sudo the bzip2 install and freetype failed the first time around (wipe and re-do fixed it with some magic).

Once the build is completed, is there a good way to figure out what the actual files needed are? I can of course compare to the released Windows build of course but it would be nice to have a more 'scientific' approach and some more insight :)

Thanks again to drawoc for your help!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Wednesday, August 22, 2012 10:01 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Glad to hear you've got it working. :)

-- drawoc

On Wed, Aug 22, 2012 at 12:49 PM, Jari Niskala wrote:

Hi Drawoc,

Thanks for your help in this! I finally got it working although it ended up being on Ubuntu. The weird part was that for Ubuntu, the glib-compile-resources was there in the same package...

I also had to add some other mingw components etc but I'm now very happy to have a working build environment :)

Thanks again for your prompt and helpful responses!

Best regards, Jari Niskala
Mobile: (858) 449-8952

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Sunday, August 19, 2012 3:49 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Maybe libglib2.0-bin didn't install correctly? Try reinstalling it:
sudo apt-get install --reinstall libglib2.0-bin

-- drawoc

On Sun, Aug 19, 2012 at 4:57 PM, Jari Niskala

wrote:

Unfortunately I did catch that so no luck with that :)

It's really weird... I couldn't find anything obvious for it online

either.

-----Original Message-----
From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Sunday, August 19, 2012 1:33 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Ah, in my last email, the command that said this:

sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev

was supposed to be all on one line, but it got automatically word-wrapped at some point.

As a result, it looks like you missed those last three packages, so just run this to install the missing packages as well: sudo apt-get install autoconf libtool libgtk2.0-dev

-- drawoc

On Sun, Aug 19, 2012 at 4:01 PM, Jari Niskala

wrote:

Thanks Drawoc! I got my Linux Mint Debian running but I keep running into a problem when the jhbuild is trying to configre glib...:

configure: error: Could not find a glib-compile-resources in your PATH
*** Error during phase configure of glib: ########## Error running ./configure --prefix
/home/jari/windows-gimp-jhbuild/targets/gimp-dev/ --libdir '/home/jari/windows-gimp-jhbuild/targets/gimp-dev//lib' --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --disable-docs --enable-all-warnings --disable-static --enable-debug=no AR="/usr/bin/i686-w64-mingw32-ar"

RANLIB="/usr/bin/i686-w64-mingw32-ranlib"

STRIP="/usr/bin/i686-w64-mingw32-strip"

AS="/usr/bin/i686-w64-mingw32-as"

DLLTOOL="/usr/bin/i686-w64-mingw32-dlltool" OBJDUMP="/usr/bin/i686-w64-mingw32-objdump" NM="/usr/bin/i686-w64-mingw32-nm"
WINDRES="/usr/bin/i686-w64-mingw32-windres" --disable-gtk-doc --cache-file=/home/jari/windows-gimp-jhbuild/win32.cache *** [5/24]

Any ideas? I can see that glib-compile-resource.c is part of glib itself but it's not on my system. I can see other glib components there just fine such as glib-compile-schemas.

Thanks!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 5:29 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I run the scripts under Debian testing regularly, so if you choose Debian or one of its derivatives you shouldn't have a hard time.

If you're still fairly new to linux though, you probably want to go with something other than straight Debian. Linux Mint is my personal favorite of the more user-friendly distros (and it's debian-derived). http://www.linuxmint.com/
You might want to go with eg. the xfce version of mint as it should be faster than the cinnamon or mate based desktops.

Anyway, once you have one of those distros installed, you can install most of the required packages like this: sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev

Then just follow the README in my git repo,

-- drawoc

On Tue, Aug 14, 2012 at 5:09 PM, Jari Niskala

wrote:

Ah, that explains it :) I tried with the latest and I'm still getting the same problem.

There were a lot of issues discussed with jhbuild on Windows so I think I'll just get Linux running on a VM to save myself a lot of pain in the short and long run. I can retry this later when I'm more familiar with Gimp and the whole build process...

Do you have a recommendation on the flavor of Linux? Or on the setup in general? I'm 'ok' on Linux but definitely not an expert.

Thanks!!

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Tuesday, August 14, 2012 1:48 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Try this: Pull my latest changes from git, and then do: export PYTHON="/c/Python27/bin/python.exe" (I'm not sure where your python exe is, so change "/c/Python27/bin/python.exe" to the location of the actual exe) Then try running the script again.
Hopefully that will work.

As a side note, I've actually never successfully compiled the GIMP directly on windows before, only cross compiled for Windows from Linux. (So you're trying something new.)

-- drawoc

On Tue, Aug 14, 2012 at 1:27 PM, Jari Niskala

wrote:

Thanks drawoc!

I'm running into some problems that I'm trying to work through but perhaps you or someone else has run into this before and can point me in the right direction (or point out what's wrong with my setup)...

Here's the error and afterwards I have listed all the steps I have taken to try to get my environment to be able to run the build script:

Jari@Jari-PC /gimp $ build
I: unknown keys defined in configuration file: mingw_tool_prefix, mingw_tools, searchprefix, fullpath_tool, flavour_cfla gs, module, tool, flavour_opt, flavour, mingw_tools_args, flavour_ext Traceback (most recent call last):
File "C:/mingw/msys/1.0/bin/jhbuild", line 31, in jhbuild.main.main(sys.argv[1:])
File "C:/mingw/msys/1.0/jhbuild\jhbuild\main.py", line 130, in main config = jhbuild.config.Config(options.configfile) File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 205, in

__init__

self.setup_env()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\config.py", line 429, in

setup_env

get_stderr = False).strip()
File "C:/mingw/msys/1.0/jhbuild\jhbuild\utils\cmds.py", line 63, in get_output
**kws)
File
"C:/mingw/msys/1.0/jhbuild\jhbuild\utils\subprocess_win32.py", line 112, in __init__
elif not command[0].endswith('.exe') or kws['shell']: KeyError: 'shell'

1. Install mingw, choose latest packages, c/c++ compiler, msys and developer kit.

2. Install mingw64 http://mingw-w64.sourceforge.net/

Choose the latest w32 build e.g. mingw32-w32-bin_i686-mingw_xxxxxxxx.zip http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targe t
t
i
n
g%20Wi
n32/Automated%20Builds/

Extract it to your machine on top of mingw, e.g. c:\mingw

3. Install Python27 Add python to your path (msys/1.0/etc/profile): export PATH="$PATH:/c/Python27"

4. Get some needed packages mingw-get.exe install msys-wget
mingw-get.exe install msys-openssl mingw-get.exe install msys-unzip

wget
http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-con f
i
g
_
0.26-1
_win32.zip
unzip pkg-config_0.26-1_win32.zip
rm pkg-config_0.26-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/pkg-config-dev_0.

26-1_win32.zip
unzip pkg-config-dev_0.26-1_win32.zip rm pkg-config-dev_0.26-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gn o
m
e
-
common
-dev_2.28.0-1_win32.zip
unzip gnome-common-dev_2.28.0-1_win32.zip rm gnome-common-dev_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-common/2.28/gn o
m
e
-
common
_2.28.0-1_win32.zip
unzip gnome-common_2.28.0-1_win32.zip rm gnome-common_2.28.0-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intlto o
l
-
d
ev_0.4
0.4-1_win32.zip
unzip intltool-dev_0.40.4-1_win32.zip rm intltool-dev_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/intltool/0.40/intlto o
l
_
0
.40.4-
1_win32.zip
unzip intltool_0.40.4-1_win32.zip
rm intltool_0.40.4-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib-dev_2.28. 8-1_wi
n32.zip
unzip glib-dev_2.28.8-1_win32.zip
rm glib-dev_2.28.8-1_win32.zip

wget

http://ftp.gnome.org/pub/GNOME/binaries/win32/glib/2.28/glib_2.28.8-1_win32.

zip
unzip glib_2.28.8-1_win32.zip
rm glib_2.28.8-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext -
r
u
n
time-d
ev_0.18.1.1-2_win32.zip
unzip gettext-runtime-dev_0.18.1.1-2_win32.zip rm gettext-runtime-dev_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/gettext -
r
u
n
time_0
.18.1.1-2_win32.zip
unzip gettext-runtime_0.18.1.1-2_win32.zip rm gettext-runtime_0.18.1.1-2_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/gnome-doc-utils/0.12 /
g
n
o
me-doc
-utils-0.12.0.zip
unzip gnome-doc-utils-0.12.0.zip
rm gnome-doc-utils-0.12.0.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2 -
d
e
v
_2.7.7
-1_win32.zip
unzip libxml2-dev_2.7.7-1_win32.zip rm libxml2-dev_2.7.7-1_win32.zip

wget http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/libxml2_2. 7
.7-1_w
in32.zip
unzip libxml2_2.7.7-1_win32.zip
rm libxml2_2.7.7-1_win32.zip

5. Adjust ACLOCAL_FLAGS export ACLOCAL_FLAGS="-I /share/aclocal"

6. Install msysgit to c:\git. When asked, choose the 'Use Git Bash

only'

option (avoid adding anything to the PATH). In the line ending conversions choice, pick "Checkout as-is, commit Unix-style line

endings"

Add git/bin to the end of your path (msys/1.0/etc/profile): export PATH="$PATH:/c/git/bin"

7. jhbuild needs to know shell location to be able to run it export SHELL=/bin/sh

8. Install jhbuild http://afuera.me.uk/jhbuild-windows/ git clone git://gitorious.org/jhbuild/jhbuild.git cd jhbuild
./autogen-sh (not sure if this is necessary) make -f Makefile.windows make install # create .jhbuildrc file as described on the jhbuild windows page jhbuild sanitycheck (mine is still complaining about gettext and xml catalog)
jhbuild bootstrap
jhbuild build (some failures here still with libxml2)

11. Get the gimp windows jhbuild https://github.com/drawoc/windows-gimp-jhbuild. Follow directions in README

-----Original Message----- From: drawoc [mailto:drawoc@darkrefraction.com] Sent: Friday, August 10, 2012 5:25 PM To: Jari Niskala
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

I just added a README to the github repository in my first email.

Let me know if the scripts give you any trouble.

-- drawoc

On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala

wrote:

That's great drawoc!

Any chance you have any writeup/info on how to setup to run this

locally?

Any info, no matter how small greatly appreciated.

Thanks!

-Jari

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc
Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Nightly Builds

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

On 09.08.12 at 10:09 pm drawoc wrote:

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild

-- drawoc _______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Thanks, drawoc, for the nightly builds. This makes it easier to detect and report bugs before a release.
Unfortunately your builds don't contain debug symbols. So in case of a crash a post-mortem-analysis can't be done. A current example is bug #682742. I encountered a crash when trying to edit the module settings (Edit/Modules). Due to missing debug symbols the stacktrace [1] is completely useless. Can you include debug symbols, please? I'd personally prefer PDB format for Visual Studio, if it's possible to do that.

Thank you,

Sven

[1] https://bugzilla.gnome.org/show_bug.cgi?id=682742#c9

On 09.08.12 at 10:09 pm drawoc wrote: > I've set up a machine to do start doing nightly builds of the GIMP for Windows.
>
> Anyone who's interested can find them here: > http://nightly.darkrefraction.com/gimp/

Thanks, drawoc, for the nightly builds. This makes it easier to detect and report bugs before a release.
Unfortunately your builds don't contain debug symbols. So in case of a crash a post-mortem-analysis can't be done. A current example is bug #682742. I encountered a crash when trying to edit the module settings (Edit/Modules). Due to missing debug symbols the stacktrace [1] is completely useless. Can you include debug symbols, please? I'd personally prefer PDB format for Visual Studio, if it's possible to do that.

Thank you,

Sven

[1] https://bugzilla.gnome.org/show_bug.cgi?id=682742#c9

Thanks drawoc!

-----Original Message----- From: gimp-developer-list-bounces@gnome.org [mailto:gimp-developer-list-bounces@gnome.org] On Behalf Of drawoc Sent: Tuesday, September 18, 2012 12:21 PM To: scl
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] Nightly Builds

Sven: Try one of the builds from September 12 or later. There were some crashes being caused by a specific version of cairo that I was building with. I switched cairo versions, and now those crashes should be gone. If that doesn't help, I'll make a debug build for you. (I have plans to make the debug builds happen every night as well, I just haven't gotten around to it yet.)

Jari:
The mkarchive script has code to remove unneeded files. In mkarchive, comment out line 63, which should say "rm -rf $f" and then run mkarchive. Then, in targets/combined you should see a folder. That folder contains the GIMP, with all unnecessary files removed.

-- drawoc

On Wed, Sep 12, 2012 at 3:14 PM, scl wrote:

On 09.08.12 at 10:09 pm drawoc wrote:

I've set up a machine to do start doing nightly builds of the GIMP for Windows.

Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/

Thanks, drawoc, for the nightly builds. This makes it easier to detect and report bugs before a release.
Unfortunately your builds don't contain debug symbols. So in case of a crash a post-mortem-analysis can't be done. A current example is bug #682742. I encountered a crash when trying to edit the module settings (Edit/Modules). Due to missing debug symbols the stacktrace [1] is completely useless. Can you include debug symbols,

please?

I'd personally prefer PDB format for Visual Studio, if it's possible to do that.

Thank you,

Sven

[1] https://bugzilla.gnome.org/show_bug.cgi?id=682742#c9

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

On 18.09.12 at 9:20 pm drawoc wrote:

Sven:
Try one of the builds from September 12 or later.

Thanks, drawoc. I tried again, but GIMP still crashes when calling Edit/Modules.

I have plans to make the debug builds happen every night as well, I just haven't gotten around to it yet.

Yes, that would be nice. In the meantime I found another debugger (DrMingw), which is freely available and thus more useful for a wider audience. It can also read debug information in Stabs formats, generated by the Gnu C/C++ Compiler [1]. Perhaps these informations are easier to generate with JHBuild as PDB files (just a thought).

Kind regards,

Sven

[1] http://code.google.com/p/jrfonseca/wiki/DrMingw

On 19.09.12 at 05:43 am scl wrote: > Perhaps these informations are easier to > generate with JHBuild as PDB files (just a thought).

I meant '...than PDB files'.

Kind regards,

Sven