> On 15 May 2018, at 20:43, Philip Lehmann-Böhm <phi...@philiplb.de> wrote: > > Hi Andrea, > > sure, sounds good. :)
Great! For your info, here is my first successful build log of BABL/GEGL/GIMP on Travis-CI, using dependencies from homebrew: https://api.travis-ci.org/v3/job/379322731/log.txt <https://api.travis-ci.org/v3/job/379322731/log.txt> > > 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? >> >> regards, >> Andrea >> >>> On 15 May 2018, at 14:11, Carmelo DrRaw <aferrero1...@gmail.com >>> <mailto:aferrero1...@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 >>> (https://github.com/aferrero2707/pf-build-osx >>> <https://github.com/aferrero2707/pf-build-osx>), 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 (https://travis-ci.org >>> <https://travis-ci.org/>). 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 >>> (https://github.com/aferrero2707/gimp-appimage >>> <https://github.com/aferrero2707/gimp-appimage>). >>> >>> Regards, >>> Andrea >>> >>>> On 15 May 2018, at 12:53, Philip Lehmann-Böhm <phi...@philiplb.de >>>> <mailto:phi...@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 <phi...@philiplb.de >>>>>>> <mailto:phi...@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: >>>>>> >>>>>> https://git.gnome.org/browse/gimp/tree/build/osx/README?h=gimp-2-8 >>>>>> <https://git.gnome.org/browse/gimp/tree/build/osx/README?h=gimp-2-8> >>>>>> >>>>>> >>>>>> 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. >>>>>> >>>>>> >>>>>> regards, >>>>>> >>>>>> -kris. >>>>>> >>>>> 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: >>>>> https://mail.gnome.org/mailman/listinfo/gimp-developer-list >>>>> <https://mail.gnome.org/mailman/listinfo/gimp-developer-list> >>>>> List archives: https://mail.gnome.org/archives/gimp-developer-list >>>>> <https://mail.gnome.org/archives/gimp-developer-list> >>>> >>>> >>>> _______________________________________________ >>>> gimp-developer-list mailing list >>>> List address: gimp-developer-list@gnome.org >>>> <mailto:gimp-developer-list@gnome.org> >>>> List membership: >>>> https://mail.gnome.org/mailman/listinfo/gimp-developer-list >>>> <https://mail.gnome.org/mailman/listinfo/gimp-developer-list> >>>> List archives: https://mail.gnome.org/archives/gimp-developer-list >>>> <https://mail.gnome.org/archives/gimp-developer-list> >> > _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
