Re: [Gimp-developer] building GIMP from git
In fact, I also built glib from git, thus maybe GIO_EXTRA_MODULES was also needed. Anyway, I used it and everything is OK now. Olivier Lecarme 2015-10-07 21:23 GMT+02:00 Elle Stone: > On 10/07/2015 12:54 PM, Olivier wrote: > >> Finally I succedded in installing GIMP, by fetching gegl, babl, >> gdk-pixbuf, and gimp itself from git, and configuring and installing >> them all under the same prefix. Under Ubuntu 15.04, the GIO extra >> modules are located in usr/lib/x86_64-linux-gnu/gio/modules. >> >> Thus I used Martin Nordholts' explanation in >> http://www.gimp.org/source/howtos/gimp-git-build.html, but I added gegl, >> babl, and gdk-pixbuf tothe packages to be fetched from git, compiled and >> installed, and I added GIO_EXTRA_MODULES to the exported variables, >> although I'm not sure that is needed. >> >> Thanks to all! >> >> Olivier Lecarme >> > > Based on comments in https://aur.archlinux.org/packages/gegl-git/, it > does look like maybe the original problem was that GIMP was finding a > too-outdated version of GEGL. > > I never needed to export GIO_EXTRA_MODULES until I tried to run GIMP 2.8 > installed from the Gentoo package manager alongside babl/GEGL/GIMP from git > installed in a prefix. But here's the reference, fwiw: > > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00042.html > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00051.html > > Looking at what Mitch said, it seems exporting GIO_EXTRA_MODULES is only > be needed if glib is also built in the prefix. So sorry for the noise! if > you didn't also build glib in the prefix. > > For the next person trying to build GIMP from git who might stumble over > this thread, a few other "why it doesn't work and what to do" are > documented here: > > http://wiki.gimp.org/wiki/Hacking:Problems_and_solutions > > -- Olivier Lecarme ___ 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
Re: [Gimp-developer] building GIMP from git
On Wed, 2015-10-07 at 18:03 +0200, Olivier wrote: > I downloaded GEGL and BABL from the links on page http://www.gimp.org > /, > i.e. http://gegl.org/ and http://gegl.org/babl/. I compiled and > installed > them using the normal procedure (sudo ./configure && make && make > install). > > Thus GEGL and BABL are not built from git But you must install babl and gegl from git in order to build gimp from git. Just install them from git too, into the same prefix, using the same environment. Regards, --Mitch ___ 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] New gimp-gui-list mailing list.
Hello everyone, The GIMP team has opened a new mailing list dedicated to discuss user interaction in GIMP, in particular graphical interaction. This is a place to discuss of the future of GIMP interface and any decision should lead to properly designed specifications for further implementation. Anyone interested in participating should be aware of GIMP "product vision", and works done in the previous years (cf. http://gui.gimp.org/index.php/GIMP_UI_Redesign) since this is the continuation of such works, and not a change of vision. Of course, the same code of conduct (which you can read here: http://www.gimp.org/mail_lists.html) applies there, as on all other mailing lists managed by the GIMP project. To subscribe: https://mail.gnome.org/mailman/listinfo/gimp-gui-list Have fun! Jehan ___ 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
Re: [Gimp-developer] building GIMP from git
It's likely that you're missing LD_LIBRARY_PATH when you're loading GIMP. While you're starting GIMP that was compiled from Git it is loading GEGL libraries from other sources. You should do the following (assuming GIMP, GEGL, and BABL were installed under /usr/local prefix by default): LD_LIBRARY_PATH=/usr/local/lib gimp-2.9 GIMP will then look to /usr/local/lib for its GEGL and BABL libraries instead of /usr/lib (which is where it is typically installed by a package manager). On Wed, Oct 7, 2015 at 11:31 PM, Olivierwrote: > In fact, I also built glib from git, thus maybe GIO_EXTRA_MODULES was also > needed. Anyway, I used it and everything is OK now. > > Olivier Lecarme > > 2015-10-07 21:23 GMT+02:00 Elle Stone : > > > On 10/07/2015 12:54 PM, Olivier wrote: > > > >> Finally I succedded in installing GIMP, by fetching gegl, babl, > >> gdk-pixbuf, and gimp itself from git, and configuring and installing > >> them all under the same prefix. Under Ubuntu 15.04, the GIO extra > >> modules are located in usr/lib/x86_64-linux-gnu/gio/modules. > >> > >> Thus I used Martin Nordholts' explanation in > >> http://www.gimp.org/source/howtos/gimp-git-build.html, but I added > gegl, > >> babl, and gdk-pixbuf tothe packages to be fetched from git, compiled and > >> installed, and I added GIO_EXTRA_MODULES to the exported variables, > >> although I'm not sure that is needed. > >> > >> Thanks to all! > >> > >> Olivier Lecarme > >> > > > > Based on comments in https://aur.archlinux.org/packages/gegl-git/, it > > does look like maybe the original problem was that GIMP was finding a > > too-outdated version of GEGL. > > > > I never needed to export GIO_EXTRA_MODULES until I tried to run GIMP 2.8 > > installed from the Gentoo package manager alongside babl/GEGL/GIMP from > git > > installed in a prefix. But here's the reference, fwiw: > > > > > > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00042.html > > > > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00051.html > > > > Looking at what Mitch said, it seems exporting GIO_EXTRA_MODULES is only > > be needed if glib is also built in the prefix. So sorry for the noise! if > > you didn't also build glib in the prefix. > > > > For the next person trying to build GIMP from git who might stumble over > > this thread, a few other "why it doesn't work and what to do" are > > documented here: > > > > http://wiki.gimp.org/wiki/Hacking:Problems_and_solutions > > > > > > > -- > Olivier Lecarme > ___ > 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 > -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ 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
Re: [Gimp-developer] building GIMP from git
Am Donnerstag, 8. Oktober 2015, 10:57:49 schrieb Sam Gleske: > It's likely that you're missing LD_LIBRARY_PATH when you're loading GIMP. > While you're starting GIMP that was compiled from Git it is loading GEGL > libraries from other sources. You should do the following (assuming GIMP, > GEGL, and BABL were installed under /usr/local prefix by default): > > LD_LIBRARY_PATH=/usr/local/lib gimp-2.9 > > GIMP will then look to /usr/local/lib for its GEGL and BABL libraries > instead of /usr/lib (which is where it is typically installed by a package > manager). With everyone telling how they build GIMP I would like to add how to avoid setting the LD_LIBRARY_PATH: baking the path into the executable. I am installing everything (babl, gegl and GIMP) to /opt/gimp-GIT/ (which belongs to my user so I don't need root to install). These are my calls to configure the three, afterwards a simple "make -j5 install" is enough. babl: LDFLAGS="-Wl,-rpath -Wl,/opt/gimp-GIT/lib" CFLAGS="-march=native -O3" CXXFLAGS="$CFLAGS" ./autogen.sh --prefix=/opt/gimp-GIT/ gegl (disabling stuff just because I don't need it): PKG_CONFIG_PATH="/opt/gimp-GIT/lib/pkgconfig" LDFLAGS="-Wl,-rpath - Wl,/opt/gimp-GIT/lib" CFLAGS="-march=native -O3" CXXFLAGS="$CFLAGS" ./autogen.sh --prefix=/opt/gimp-GIT/ --disable-docs --without-libavformat -- without-vala GIMP (with mypaint being installed in /opt/mypaint/): PKG_CONFIG_PATH="/opt/gimp-GIT/lib/pkgconfig:/opt/mypaint/lib/pkgconfig" LDFLAGS="-Wl,-rpath -Wl,/opt/gimp-GIT/lib" CFLAGS="-march=native -O3" CXXFLAGS="$CFLAGS" ./autogen.sh --prefix=/opt/gimp-GIT --enable-python Each of them is one line. HTH Tobias > On Wed, Oct 7, 2015 at 11:31 PM, Olivierwrote: > > In fact, I also built glib from git, thus maybe GIO_EXTRA_MODULES was also > > needed. Anyway, I used it and everything is OK now. > > > > Olivier Lecarme > > > > 2015-10-07 21:23 GMT+02:00 Elle Stone : > > > On 10/07/2015 12:54 PM, Olivier wrote: > > >> Finally I succedded in installing GIMP, by fetching gegl, babl, > > >> gdk-pixbuf, and gimp itself from git, and configuring and installing > > >> them all under the same prefix. Under Ubuntu 15.04, the GIO extra > > >> modules are located in usr/lib/x86_64-linux-gnu/gio/modules. > > >> > > >> Thus I used Martin Nordholts' explanation in > > >> http://www.gimp.org/source/howtos/gimp-git-build.html, but I added > > > > gegl, > > > > >> babl, and gdk-pixbuf tothe packages to be fetched from git, compiled > > >> and > > >> installed, and I added GIO_EXTRA_MODULES to the exported variables, > > >> although I'm not sure that is needed. > > >> > > >> Thanks to all! > > >> > > >> Olivier Lecarme > > > > > > Based on comments in https://aur.archlinux.org/packages/gegl-git/, it > > > does look like maybe the original problem was that GIMP was finding a > > > too-outdated version of GEGL. > > > > > > I never needed to export GIO_EXTRA_MODULES until I tried to run GIMP 2.8 > > > installed from the Gentoo package manager alongside babl/GEGL/GIMP from > > > > git > > > > > installed in a prefix. But here's the reference, fwiw: > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00042 > > .html > > > > > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00051 > > .html> > > > Looking at what Mitch said, it seems exporting GIO_EXTRA_MODULES is only > > > be needed if glib is also built in the prefix. So sorry for the noise! > > > if > > > you didn't also build glib in the prefix. > > > > > > For the next person trying to build GIMP from git who might stumble over > > > this thread, a few other "why it doesn't work and what to do" are > > > documented here: > > > > > > http://wiki.gimp.org/wiki/Hacking:Problems_and_solutions > > > > -- > > Olivier Lecarme > > ___ > > 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 signature.asc Description: This is a digitally signed message part. ___ 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
Re: [Gimp-developer] Fade length setting for paint dynamics
On 08/10/15 14:05, Jon Tait wrote: 1. The "percent" setting is relative to maximal image dimension (ie. image width or height, whichever is larger). Ref: https://git.gnome.org/browse/gimp/tree/app/paint/gimppaintoptions.c?h=gimp-2-8#n591 And as far as I can see it *does* work as intended - eg. Paintbrush Tool with Dynamics=Fade Tapering, Fade length=100% will fade in/out over a *stroke* length equal to the larger of image width and height. And pro rata for other values of "percent". [But note that it is the maximal *image* dimension, not *drawable* dimension.] I tried that and it didn't seem to work. 2. No it cannot currently be set programmatically. The fade parameters are *dynamic options* (ie. specific to the fade dynamic), not common *paint options* (ie. applicable to all paint tools regardless of dynamics). And setting dynamic options is AFAIK not currently supported via PDB. IIRC this problem has been noted before but I cannot find anything on bugzilla about it now. Note this is a wider problem than just fade length, it requires a generalized method of getting/setting *all* dynamic options. Dynamics take their other values from the general context For instance the varying "color" in the Dynamics uses the context gradient, the brush size is the context brush size, etc... And if I change a dynamics-related setting (fo instance, the "repeat") for one tool (brush), the value changes for other tools (airbrush, clone...). ___ 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