rsvg dependencies in the last gimp git master
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.
rsvg dependencies in the last gimp git master
hi all,
I have problems with the 'make' of gimp, on the last git master is necessary a different release of my environment.
My environment is a bit old (ubuntu gnome 14.04.2 with gnome 3.10 ;), but until this moment I have had success to configure the dependencies... but now I have problems to understand completely the issue... so, I am not sure how is possible fix this.
When I do 'make' on gimp, I have this:
WARNING: Your gettext version is 0.18.3. The recommended gettext version is 0.19 or over. If you continue without updating gettext, your build will have partially broken localization.
Error: GIMP configuration failed.
- Error: missing dependency rsvg >= 2.40.6
See the file 'INSTALL' for more help.
make: *** [config.status] Error 1
make: *** Waiting for unfinished jobs....
When I try 'autogen.sh' on my prefix with the last rsvb, I have this:
checking for LIBRSVG... no configure: error: Package requirements ( gdk-pixbuf-2.0 >= 2.20 glib-2.0 >= 2.12.0 gio-2.0 >= 2.24.0 libxml-2.0 >= 2.7.0 pangocairo >= 1.32.6 cairo >= 1.2.0 cairo-png >= 1.2.0 libcroco-0.6 >= 0.6.1) were not met:
Requested 'pangocairo >= 1.32.6' but version of Pango Cairo is 1.29.5
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBRSVG_CFLAGS and LIBRSVG_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details
===
So, some of dependencies as Pango Cairo I have installed the more recent versions in the specific environment of gimp git master... but is curious that the rsvg don't see this.
How is the method to configure the rsvg?
Someone can help me?
thanks
americo
Gimp 2.8 plugins which not work properly with Gimp 2.9.x/2.10.x
Good morning, folks,
AFAIK there are some old plugins which not work properly with Gimp 2.9.x/2.10.x.
Is there any way to determine which old plugins don't work (properly) any more?
I concern that some users could be confused if their favourite plugins crashes e.g. I think that could be a bad user experience.
Any ideas? Blacklisting?
Cheers
Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut. Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.
Gimp 2.8 plugins which not work properly with Gimp 2.9.x/2.10.x
Good morning, folks,
AFAIK there are some old plugins which not work properly with Gimp 2.9.x/2.10.x.
Is there any way to determine which old plugins don't work (properly) any more?
I concern that some users could be confused if their favourite plugins crashes e.g. I think that could be a bad user experience.
Any ideas? Blacklisting?
Cheers
Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut. Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.
Gimp 2.8 plugins which not work properly with Gimp 2.9.x/2.10.x
Which is more overwhelming for a user? Not being able to locate a blacklisted plugin or being able to tell people what error it fails with?
Alex
24 июня 2017 г. 11:10 пользователь "Thorsten Stettin" < thorsten.stettin@gmail.com> написал:
Good morning, folks,
AFAIK there are some old plugins which not work properly with Gimp 2.9.x/2.10.x.
Is there any way to determine which old plugins don't work (properly) any more?
I concern that some users could be confused if their favourite plugins crashes e.g. I think that could be a bad user experience.
Any ideas? Blacklisting?
Cheers
-- Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut.
Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen._______________________________________________ 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 2.8 plugins which not work properly with Gimp 2.9.x/2.10.x
Am 24.06.17 um 10:24 schrieb Alexandre Prokoudine:
Which is more overwhelming for a user? Not being able to locate a blacklisted plugin or being able to tell people what error it fails with?
Alex
You answers my questions with questions. Nice, Dude. 8-)
24 июня 2017 г. 11:10 пользователь "Thorsten Stettin" < thorsten.stettin@gmail.com> написал:
Good morning, folks,
AFAIK there are some old plugins which not work properly with Gimp 2.9.x/2.10.x.
Is there any way to determine which old plugins don't work (properly) any more?
I concern that some users could be confused if their favourite plugins crashes e.g. I think that could be a bad user experience.
Any ideas? Blacklisting?
Cheers
-- Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut.
Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen._______________________________________________ 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
Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut. Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.
Trouble with building Gimp 2.9.5 against libmypaint
Hello,
OS: Ubuntu 17.10
Build environment: launchpad.net
libmypaint: 2.0.0
https://github.com/mypaint/libmypaint/commit/e5beceeb552c0889e89ae252594cff16ffe8f241
gimp:
https://git.gnome.org/browse/gimp/commit/?id=970e9aca90760433490555560a472149ddabb57c
issue:
/<>/app/paint/gimpmybrushcore.c: In function ‘gimp_mybrush_core_motion’:
/<>/app/paint/gimpmybrushcore.c:281:11: error: too few arguments to function ‘mypaint_brush_stroke_to’
mypaint_brush_stroke_to (brush,
^~~~~~~~~~~~~~~~~~~~~~~
In file included from /<>/app/paint/gimpmybrushcore.c:26:0:
/usr/include/libmypaint/mypaint-brush.h:44:1: note: declared here
mypaint_brush_stroke_to(MyPaintBrush *self, MyPaintSurface *surface, float x, float y,
^~~~~~~~~~~~~~~~~~~~~~~
/<>/app/paint/gimpmybrushcore.c:317:7: error: too few arguments to function ‘mypaint_brush_stroke_to’
mypaint_brush_stroke_to (brush,
^~~~~~~~~~~~~~~~~~~~~~~
In file included from /<>/app/paint/gimpmybrushcore.c:26:0:
/usr/include/libmypaint/mypaint-brush.h:44:1: note: declared here
mypaint_brush_stroke_to(MyPaintBrush *self, MyPaintSurface *surface, float x, float y,
Any hints?
Thanks for your help.
Cheers
Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut. Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.
Trouble with building Gimp 2.9.5 against libmypaint
On Sat, Jun 24, 2017 at 7:26 AM, Thorsten Stettin < thorsten.stettin@gmail.com> wrote:
Hello,
OS: Ubuntu 17.10
Build environment: launchpad.net
libmypaint: 2.0.0 https://github.com/mypaint/lib mypaint/commit/e5beceeb552c0889e89ae252594cff16ffe8f241 gimp: https://git.gnome.org/browse/gimp/commit/?id=970e9aca9076043 3490555560a472149ddabb57c
issue:/<>/app/paint/gimpmybrushcore.c: In function ‘gimp_mybrush_core_motion’:
/<>/app/paint/gimpmybrushcore.c:281:11: error: too few arguments to function ‘mypaint_brush_stroke_to’ mypaint_brush_stroke_to (brush, ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /<>/app/paint/gimpmybrushcore.c:26:0: /usr/include/libmypaint/mypaint-brush.h:44:1: note: declared here mypaint_brush_stroke_to(MyPaintBrush *self, MyPaintSurface *surface, float x, float y,
^~~~~~~~~~~~~~~~~~~~~~~
/<>/app/paint/gimpmybrushcore.c:317:7: error: too few arguments to function ‘mypaint_brush_stroke_to’ mypaint_brush_stroke_to (brush, ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /<>/app/paint/gimpmybrushcore.c:26:0: /usr/include/libmypaint/mypaint-brush.h:44:1: note: declared here mypaint_brush_stroke_to(MyPaintBrush *self, MyPaintSurface *surface, float x, float y,buildlog: https://launchpadlibrarian.net/325334804/buildlog_ubuntu-art ful-amd64.gimp_2.9.5~115-0a0~ppa~970e9ac_BUILDING.txt.gz
Any hints?
Thanks for your help.
Cheers
It has been mentioned at least 3 times in as many days. :)
Revert your libmypaint to a commit prior to the current one.
Trouble with building Gimp 2.9.5 against libmypaint
Am 24.06.17 um 14:00 schrieb Partha Bagchi:
On Sat, Jun 24, 2017 at 7:26 AM, Thorsten Stettin > wrote:
Hello,
OS: Ubuntu 17.10
Build environment: launchpad.net
libmypaint: 2.0.0 https://github.com/mypaint/libmypaint/commit/e5beceeb552c0889e89ae252594cff16ffe8f241
gimp:
https://git.gnome.org/browse/gimp/commit/?id=970e9aca90760433490555560a472149ddabb57c
issue:/<>/app/paint/gimpmybrushcore.c: In function ‘gimp_mybrush_core_motion’:
/<>/app/paint/gimpmybrushcore.c:281:11: error: too few arguments to function ‘mypaint_brush_stroke_to’ mypaint_brush_stroke_to (brush, ^~~~~~~~~~~~~~~~~~~~~~~ In file included from
/<>/app/paint/gimpmybrushcore.c:26:0: /usr/include/libmypaint/mypaint-brush.h:44:1: note: declared here mypaint_brush_stroke_to(MyPaintBrush *self, MyPaintSurface *surface, float x, float y,
^~~~~~~~~~~~~~~~~~~~~~~
/<>/app/paint/gimpmybrushcore.c:317:7: error: too few arguments to function ‘mypaint_brush_stroke_to’ mypaint_brush_stroke_to (brush, ^~~~~~~~~~~~~~~~~~~~~~~
In file included from
/<>/app/paint/gimpmybrushcore.c:26:0: /usr/include/libmypaint/mypaint-brush.h:44:1: note: declared here mypaint_brush_stroke_to(MyPaintBrush *self, MyPaintSurface *surface, float x, float y,Any hints?
Thanks for your help.
Cheers
It has been mentioned at least 3 times in as many days. :)
This don't impress me much.
Revert your libmypaint to a commit prior to the current one.
Don't go back look forward. Your opinion I cannot accept.
I wrote messages to Andrew Chadwick and Brien
Dieterle too.
AFAIK the both are maintaining the project.
Please agrees you.
Thanks
Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut. Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.
Trouble with building Gimp 2.9.5 against libmypaint
Am 24.06.2017 um 16:34 schrieb Thorsten Stettin:
Am 24.06.17 um 14:00 schrieb Partha Bagchi:
It has been mentioned at least 3 times in as many days. :)
This don't impress me much.
Do you follow the GIMP and libmypaint bug trackers? If not, then you should do so (and read the notifications you get).
https://bugzilla.gnome.org/show_bug.cgi?id=783936 https://github.com/mypaint/libmypaint/issues/92
P.S. please do not hijack old threads on the list for new topics, create new messages for those. Changing the subject is not sufficient to start new threads.
Regards, Michael GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
Trouble with building Gimp 2.9.5 against libmypaint
Am 24.06.17 um 18:08 schrieb Michael Schumacher:
Am 24.06.2017 um 16:34 schrieb Thorsten Stettin:
Am 24.06.17 um 14:00 schrieb Partha Bagchi:
It has been mentioned at least 3 times in as many days. :)
This don't impress me much.
Do you follow the GIMP and libmypaint bug trackers? If not, then you should do so (and read the notifications you get).
https://bugzilla.gnome.org/show_bug.cgi?id=783936 https://github.com/mypaint/libmypaint/issues/92
P.S. please do not hijack old threads on the list for new topics, create new messages for those. Changing the subject is not sufficient to start new threads.
Hijack old threads? Are you kidding me? I'm just a fucking packager who needs some help.
Who do you think you are?
Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen. Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege. Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut. Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.
Trouble with building Gimp 2.9.5 against libmypaint
Am 24.06.2017 um 18:19 schrieb Thorsten Stettin:
Am 24.06.17 um 18:08 schrieb Michael Schumacher:
P.S. please do not hijack old threads on the list for new topics, create new messages for those. Changing the subject is not sufficient to start new threads.
Hijack old threads? Are you kidding me?
No, I'm not.
There's two header lines from the your message which started the current topic:
[...]
In-Reply-To:
[...]
Subject: [Gimp-developer] Trouble with building Gimp 2.9.5 against
libmypaint
[...]
Note the "In-Reply-To". You have started this message by replying to an existing message and changed the subject. You shouldn't do this, as it gets threading all wrong.
This can be avoided by starting a new mail message to the list address for new topics.
Who do you think you are?
Someone who knows that the actions described above are called thread hijacking, or threadjacking.
Regards, Michael GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
Trouble with building Gimp 2.9.5 against libmypaint
24 июня 2017 г. 17:34 пользователь "Thorsten Stettin" < thorsten.stettin@gmail.com> написал:
It has been mentioned at least 3 times in as many days. :)
This don't impress me much.
It's not supposed to impress.
Revert your libmypaint to a commit prior to the current one.
Don't go back look forward. Your opinion I cannot accept.
Or build with libmypaint 1.3.0. If you cannot accept that, then you cannot build GIMP. Whether you agree or not isn't much relevant. You don't cut libmypaint releases and you don't change its API. That's just a basic fact.
I wrote messages to Andrew Chadwick and Brien Dieterle too.
So that they do what, exactly?
Please agrees you.
Parser error.
Alex
Trouble with building Gimp 2.9.5 against libmypaint
24 июня 2017 г. 2:27 PM пользователь "Thorsten Stettin" < thorsten.stettin@gmail.com> написал:
libmypaint: 2.0.0
https://github.com/mypaint/libmypaint/commit/aace2b9bdfb944d40360506d76cb36ae046f0076
https://github.com/mypaint/libmypaint/issues/92
Alex