Re: [Gimp-developer] MacOS-Build, maybe I could help?

I am available for testing the package. :)
Some first impressions:
- It starts, Gimp opens just fine
- Dragged a PNG from Finder, the popup "Convert to RGB Working Space" didn't come into the foreground. I had to move the main window in order to make it visible.
- Drew a bit, added another layer, drew a bit, so far so good
- The buttons of the export dialog are not properly rendered:

Am 19.05.18 um 19:13 schrieb Carmelo DrRaw:
For your info, I have managed to create a first GIMP 2.10.1 .dmg package using Travis-CI. It is still highly experimental, and I am already aware that for example the python plug-ins still do not work…

Anyway, I would really appreciate if you could test the package and give me some feedback. Once all issues fixed, it will provide an automated creation of OSX packages from the development code.

@Philip: are you available for testing the package? Also, do you have an account on github?

On 15 May 2018, at 20:43, Philip Lehmann-Böhm <philip philiplb de <mailto:philip philiplb de>> wrote:

Hi Andrea,

sure, sounds good. :)

Am 15.05.18 um 19:31 schrieb Carmelo DrRaw:
Somehow I forgot to mention the most important thing…

@Philip: would you be interested to collaborate with me on this? I such case, I have no problem to give you contributor access to the corresponding github repo, for example. Once the first DMG is created, the most important thing will be to test the package and report/fix problems, and that’s were in my opinion it will be super-useful to share the work…

What do you think?


On 15 May 2018, at 14:11, Carmelo DrRaw <aferrero1975 gmail com <mailto:aferrero1975 gmail com>> wrote:

I would like to chime in this thread, to let you know that I have quite some experience in automating the OSX DMG creation process for GTK applications.

I have already set-up such a build procedure for another project of mine (, and I am currently working on applying the same concept to GIMP. The build environment is based on Homebrew, and is designed to run automatically on Travis-CI ( <>). The resulting DMG package gets automatically uploaded back to GitHub, without any manual intervention. Up to now I have successfully compiled the git head version of BABL/GEGL/GIMP using dependencies from homebrew. Now I am starting to adapt the scripts to Travis-CI and to package the whole thing into a DMG file. The whole set of scripts would be hosted in a github repository, so that it will be accessible to everybody for checking and improving…

If that sounds interesting/useful, just let me know. The idea is primarily meant at regularly providing ready-to-install snapshots of the development version, with close-to-zero workload for developers. By the way, I am already taking care of a similar automated build procedure for a GIMP Linux AppImage package (


On 15 May 2018, at 12:53, Philip Lehmann-Böhm <philip philiplb de <mailto:philip philiplb de>> wrote:

Am 15.05.18 um 12:50 schrieb Philip Lehmann-Böhm:
Am 15.05.18 um 10:47 schrieb Kristian Rietveld:
On 12 May 2018, at 14:00, Philip Lehmann-Böhm <philip philiplb de <mailto:philip philiplb de>> wrote:

I've read in the FAQs that the guy with the Mac is a bit busy at the moment and so there is hardly any time left for creating the DMG. Maybe I could help here and do the build? I would just need some directions what is needed to compile and build the package.
How we have been building the DMG up till now is documented in git:

This is now a little outdated because I have been working on fully automating this process when I still had some spare time. This work is in fact almost complete. I am trying to find the time to upload this work into git. It will consist of a Python script that will automatically build all components and create the DMG and some documentation on how to setup the environment within which to launch this Python script.

Note that this concerns GIMP 2.8. There are no instructions for 2.10 yet. My plan was to work on making the necessary changes to the script and moduleset to build 2.10 as soon as the work for 2.8 has been published in git.



Hi Kris,

automating the build process seems like a good idea. :)

Is there anything I could do in the meantime? Like adjusting the Python script to 2.10?
Or following the steps of the README and build a dmg?

gimp-developer-list mailing list
List address: gimp-developer-list gnome org <mailto:gimp-developer-list gnome org> List membership:
List archives:

gimp-developer-list mailing list
List address: gimp-developer-list gnome org <mailto:gimp-developer-list gnome org> List membership:
List archives:

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