MacOS-Build, maybe I could help?
This discussion is connected to the gimp-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.
MacOS-Build, maybe I could help? | Philip Lehmann-Böhm | 12 May 12:00 |
MacOS-Build, maybe I could help? | Shlomi Fish | 12 May 15:21 |
MacOS-Build, maybe I could help? | Kristian Rietveld | 15 May 08:47 |
MacOS-Build, maybe I could help? | Philip Lehmann-Böhm | 15 May 10:50 |
MacOS-Build, maybe I could help? | Philip Lehmann-Böhm | 15 May 10:53 |
MacOS-Build, maybe I could help? | Carmelo DrRaw | 15 May 12:11 |
MacOS-Build, maybe I could help? | Carmelo DrRaw | 15 May 17:31 |
MacOS-Build, maybe I could help? | Philip Lehmann-Böhm | 15 May 18:43 |
MacOS-Build, maybe I could help? | Carmelo DrRaw | 15 May 20:18 |
MacOS-Build, maybe I could help? | Carmelo DrRaw | 19 May 17:13 |
MacOS-Build, maybe I could help? | Carmelo DrRaw | 19 May 17:14 |
MacOS-Build, maybe I could help? | Habib Gahbiche | 19 May 17:30 |
MacOS-Build, maybe I could help? | Carmelo DrRaw | 19 May 19:43 |
MacOS-Build, maybe I could help? | Habib Gahbiche | 19 May 20:33 |
MacOS-Build, maybe I could help? | Philip Lehmann-Böhm | 19 May 19:20 |
MacOS-Build, maybe I could help? | Carmelo DrRaw | 21 May 11:19 |
MacOS-Build, maybe I could help?
Hi all,
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.
Philip Lehmann-Böhm
MacOS-Build, maybe I could help?
Hi,
On Sat, 12 May 2018 14:00:55 +0200 Philip Lehmann-Böhm wrote:
Hi all,
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.
thanks for your help. Perhaps look into the homebrew/macports packages.
----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ http://youtu.be/KxGRhd_iWuE - Never Give Up!! “A is A, and A is not not-A? WTH is he talking about??! Of course A can be not-A! I want a little of the stuff he’s on!” — Initial reaction to the http://en.wikipedia.org/wiki/Organon Please reply to list if it's a mailing list post - http://shlom.in/reply .
MacOS-Build, maybe I could help?
On 12 May 2018, at 14:00, Philip Lehmann-Böhm 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
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.
MacOS-Build, maybe I could help?
Am 15.05.18 um 10:47 schrieb Kristian Rietveld:
On 12 May 2018, at 14:00, Philip Lehmann-Böhm 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
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?
MacOS-Build, maybe I could help?
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 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
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 List membership:
https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
MacOS-Build, maybe I could help?
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 ), 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 ). 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 ).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm 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 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
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 List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: 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
MacOS-Build, maybe I could help?
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 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 ), 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 ). 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 ).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm > 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 > 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
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 List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: 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
MacOS-Build, maybe I could help?
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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw > 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), 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 ). 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).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm > 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 > 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
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.orgList membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives:https://mail.gnome.org/archives/gimp-developer-list
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.orgList membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
MacOS-Build, maybe I could help?
On 15 May 2018, at 20:43, Philip Lehmann-Böhm 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
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 > 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 ), 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 ). 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 ).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm > 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 > 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
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 List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: 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
MacOS-Build, maybe I could help?
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 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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw > 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 ), 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 ). 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 ).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm > 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 > 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
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 List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: 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
MacOS-Build, maybe I could help?
Sorry, I forgot to send the link to the package… here it is: https://github.com/aferrero2707/gimp-osx/releases/download/continuous/gimp-osx-git-2.10.1-20180519.dmg
On 19 May 2018, at 19:13, Carmelo DrRaw wrote:
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 > 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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw > 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 ), 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 ). 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 ).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm > 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 > 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
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 List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: 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
MacOS-Build, maybe I could help?
Hi,
I'm willing to help here too. I just downloaded the dmg file and Gimp seems to work fine (I quickly opened a jpg image by drag and drop, used a few brushes and exported it to png successfully). But I'm not sure if I'm supposed to look for specific things in gimp or does a successful launch mean that the dmg file is fine? Also, could you please send us the link to the building script? Thanks.
Macbook Pro 2012:
macOS 10.13.4
2,5 GHz Intel Core i5
Intel HD Graphics 4000 1536 MB
Best,
2018-05-19 19:14 GMT+02:00 Carmelo DrRaw :
Sorry, I forgot to send the link to the package… here it is: https://github.com/aferrero2707/gimp-osx/releases/download/continuous/ gimp-osx-git-2.10.1-20180519.dmg
On 19 May 2018, at 19:13, Carmelo DrRaw wrote:
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
> 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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw
> 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 ), 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 ). 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
).
Regards,
AndreaOn 15 May 2018, at 12:53, Philip Lehmann-Böhm
> 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
> 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
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.orggimp-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
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.orggimp-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
_______________________________________________ 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
MacOS-Build, maybe I could help?
Hi,
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 > 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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw > 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), 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 ). 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).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm > 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 > 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
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.orgList membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives:https://mail.gnome.org/archives/gimp-developer-list
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.orgList membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
MacOS-Build, maybe I could help?
Hi!
On 19 May 2018, at 19:30, Habib Gahbiche wrote:
Hi,
I'm willing to help here too. I just downloaded the dmg file and Gimp seems to work fine (I quickly opened a jpg image by drag and drop, used a few brushes and exported it to png successfully). But I'm not sure if I'm supposed to look for specific things in gimp or does a successful launch mean that the dmg file is fine? Also, could you please send us the link to the building script? Thanks.
I would say that this is already a very good news. One important thing is to test as many tools and filters as possible in “normal” conditions, and report whatever does not work properly.
The build scripts can be found here: https://github.com/aferrero2707/gimp-osx/blob/master/build-hb.sh https://github.com/aferrero2707/gimp-osx/blob/master/package-gimp-hb.sh
The cached homebrew dependencies are taken from here: https://github.com/aferrero2707/pf-build-osx
Hope this helps!
Macbook Pro 2012:
macOS 10.13.4
2,5 GHz Intel Core i5
Intel HD Graphics 4000 1536 MBBest,
2018-05-19 19:14 GMT+02:00 Carmelo DrRaw >: Sorry, I forgot to send the link to the package… here it is: https://github.com/aferrero2707/gimp-osx/releases/download/continuous/gimp-osx-git-2.10.1-20180519.dmg >
On 19 May 2018, at 19:13, Carmelo DrRaw > wrote:
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 >> 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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw >> 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 >), 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 >). 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 >).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm >> 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 >> 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 >
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 > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: 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 >_______________________________________________ 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
MacOS-Build, maybe I could help?
Hi,
thanks for the links. So did you simply install the dependencies described in [1] with homebrew and then run the script build.hb.sh? Or are there other steps I should be aware of?
[1] https://wiki.gimp.org/wiki/Hacking:Building#GIMP.27s_dependencies
2018-05-19 21:43 GMT+02:00 Carmelo DrRaw :
Hi!
On 19 May 2018, at 19:30, Habib Gahbiche wrote:
Hi,
I'm willing to help here too. I just downloaded the dmg file and Gimp seems to work fine (I quickly opened a jpg image by drag and drop, used a few brushes and exported it to png successfully). But I'm not sure if I'm supposed to look for specific things in gimp or does a successful launch mean that the dmg file is fine? Also, could you please send us the link to the building script? Thanks.
I would say that this is already a very good news. One important thing is to test as many tools and filters as possible in “normal” conditions, and report whatever does not work properly.
The build scripts can be found here: https://github.com/aferrero2707/gimp-osx/blob/master/build-hb.sh https://github.com/aferrero2707/gimp-osx/blob/master/package-gimp-hb.sh
The cached homebrew dependencies are taken from here: https://github.com/aferrero2707/pf-build-osx
Hope this helps!
Macbook Pro 2012: macOS 10.13.4
2,5 GHz Intel Core i5
Intel HD Graphics 4000 1536 MBBest,
2018-05-19 19:14 GMT+02:00 Carmelo DrRaw :
Sorry, I forgot to send the link to the package… here it is: https://github.com/aferrero2707/gimp-osx/releases/download/ continuous/gimp-osx-git-2.10.1-20180519.dmg < https://github.com/aferrero2707/gimp-osx/releases/download/ continuous/gimp-osx-git-2.10.1-20180519.dmg>
On 19 May 2018, at 19:13, Carmelo DrRaw wrote:
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
> 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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw
> 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 ). 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,
AndreaOn 15 May 2018, at 12:53, Philip Lehmann-Böhm
> 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 > 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=gi
mp-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.orggimp-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
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.orggimp-developer-list@gnome.org>
List membership: https://mail.gnome.org/mailman
/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archiv
es/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
MacOS-Build, maybe I could help?
On 19 May 2018, at 21:20, Philip Lehmann-Böhm wrote:
Hi, I am available for testing the package. :)
Thanks!
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.
I will look into that...
- Drew a bit, added another layer, drew a bit, so far so good - The buttons of the export dialog are not properly rendered:
Could you post a screenshot of the export dialog?
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 > 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?
regards, Andrea
On 15 May 2018, at 14:11, Carmelo DrRaw > 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), 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 ). 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).
Regards, Andrea
On 15 May 2018, at 12:53, Philip Lehmann-Böhm > 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 > 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
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 List membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: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_______________________________________________ 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