Re: [Gimp-developer] [Gimp-user] Discontinuation of mailing lists and moving to Discourse

[Ken Moffat via gimp-developer-list]

On Mon, Oct 17, 2022 at 10:00:24PM +0200, Jehan Pagès via gimp-developer-list 
wrote:
> Hi!
> 
> On Mon, Oct 17, 2022 at 9:48 PM Rick Strong  wrote:
> 
> > So if I want to ask a question about using GIMP, or respond to a question,
> > how do I do it?
> >
> 
> Well basically same as you always did, except that now it will be on one of
> the Discourse instances, such as the pixls.us one or the GNOME one. Instead
> of being subscribed to a mailing list, it's on Discourse (which is
> basically a modern-time forum, as I see it), on which you'd have a
> login/account. :-)
> 
> Jehan
> 

As a linux user, this feels like a retrograde step (there are ways
of running mailing lists without python2, such as sympa, although
they tend to work sub-optimally).  But it is outside my, and your,
control so thanks for the forewarning.

I guess that if I have any questions in the future I'll use
https://discuss.pixls.us in the hope that I might get indications of
how to do something (I'm logged in there on one of my machines, I
get mails every week or so with topics since I last visited - most
of which seem to be about non-interesting *to me* software).

This might be my last post here, so I'll say thanks to the people
who have helped me on -user over the years, and to the devs who have
made 2.10 what it is - yes, I'd like to use 2.99 but I also want
script-fu and g'mic plugins so I guess I'll be staying on 2.10 for a
while.

ĸen
-- 
Greater love hath no woman for the premiership than to lay down the
life of her bosom friend in an attempt to save her own skin.
 -- Andrew Rawnsley
___
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] Gimp "make install" fails with undefined references to fresh-built gegl

[Ken Moffat via gimp-developer-list]

On Wed, Jul 08, 2020 at 02:39:08PM -0700, Deft Developer wrote:
> I got all of the dependencies (except WebKit) and GIMP 2.10.20 to build on
> CentOS.
> To make a very long  story short, each dependency, and GIMP, is best built
> with no traces of previous builds or out-of-date dependencies. "make clean"
> and re-configuring  are inadequate. It's easiest just to re-clone each
> repository, or delete each extracted source directory.
> Each dependency needs to be installed into whatever build-prefix is
> configured, and then the next dependency may be built. Sometimes, Iterating
> over multiple versions of a dependency is required. In that case,
> delete/uninstall the older version after you have built what needed it, and
> then build the newer version.
> 
> I simply gave up for webkit. Webkit is gigantic, and has a wilderness of
> dependencies. It easier just to use an external browser to access GIMP help.
> 
First, I'm glad you fixed it.

Second, for webkit my impression is that gimp-2.10 looks for an
ancient version.  Certainly, using firefox to access the online help
has worked fine for me in the last couple of years.

ĸen
-- 
   He died at the console, of hunger and thirst.
   Next day he was buried, face-down, nine-edge first.
  - the perfect programmer
___
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] Asking for help/collaboration in nonprofit mini-project around covid-19

[Ken Moffat via gimp-developer-list]

On Fri, May 01, 2020 at 11:21:18PM +0200, Ofnuts wrote:
> On 01/05/2020 22:40, P. Cáliz wrote:
> > Hi all
> > 
> > I am trying to launch a social (non-profit) mini-project based on the
> > hashtag #EstasEnMisPensamientos / #YouAreOnMyMind.
> > I am going to publicly share a selection of my photos (a few hundred, I
> > suppose there will be some good ones ;-) ) labeled with that hastag and
> > with the URL of the collection, so that anyone can freely send them to
> > family, friends, ... Also I will try to involve professional photographers,
> > and entities that have their own collections (botanical gardens, museums,
> > conservation societies of monuments such as La Alhambra de Granada or the
> > Topkapi palace, etc), to contribute with material from their collections.
> > I do not know what success I can have, but being optimistic I must
> > expect a volume of contributions that I will not be able to handle by
> > myself, by hand. And it is for this that I request your help, perhaps
> > someone can make a Script-fu that automates the treatment of the photos. I
> > have only used Gimp sporadically to correct the color or contrast of my
> > photos, but I have an absolute ignorance beyond this.
> > 
> > Ideally the script should run in a loop with the following actions:
> > 
> > - Take a photo from the originals directory A
> > - Adjust the photo to a maximum size (~ 2048 pix vertical or horizontal)
> > preserving the aspect ratio
> > - Add a frame around the image with the bottom side wider than the
> > others (similar to Polaroid photos), and write the hastag (english and
> > spanish), and the collection URL in this bottom border. This is just an
> > idea, I'm open to your artistic suggestions
> > - Export as .jpeg in the modified photos directory B
> > - If possible, move the original photo from A directory to the C
> > directory so that it is not treated again
> > 
> > Maybe it is necessary to define some additional detail, please feel free
> > to ask me anything.
> > 
> > I will exclusively dedicate a Raspberry Pi 3 for Gimp to fly.
> > Every day I will try to download in the original directory "A" all the
> > photos received at youareonmym...@scrive.org (by the way, if someone knows
> > how to automate this, I would be s grateful). And also every day I will
> > upload all the taged photos in directory "B" to the public album (I'm still
> > not sure of the URL, I will probably host it in google photos).
> > 
> > Any volunteer? Hope yes.
> 
> Typically done with ImageMagick: https://imagemagick.org/index.php
> 
> Some features:
> 
> https://imagemagick.org/Usage/resize/
> 
> https://imagemagick.org/Usage/text/
> 
Probably getting a bit OT for gimp-dev, but I'll reply here anyway
this time.

For the rest, typically done with shell script(s) from bash since
all you are doing is invoking programs with some options, e.g. 'cp'
to move files from 'A' to 'C' IFF (if and only if) the modifications
to create the file in B did not end in failure.

Obviously, set aside some work space to play around with a *copy*
of a file and then when the modifications seem to work on that file,
try a copy of a different file.

I've done the resizing in the past but I've never tried adding text
on top, or borders.

But the fun part will be downloading everything from the original
directory, and then wiping out everything that is there, without
losing anything that comes in after you have started the download.

Perhaps list everything currently at the directory, wget each item
in turn checking for no errors (e.g. full disk, non-responsive
external server) make a backup (did I mention the aggravation caused
by losing something someone sent you?) and only then rm the file
from the original.

Or do the rm at the end, but perhaps keeping a separate file of those
jpegs you have successfully downloaded and adding the details to that
file after tou have successfully downloaded a file.

For IM there are lots of posts online.

I've in the past used it to resize a batch of photos, the salient
points were (from a bash script which was modifying the original
in-place):

for F in $*; do
echo "Processing $F" # I like scripts to keep me informed

# confirm it really is a jpeg, and find its dimensions
DIMENSIONS=$(identify $F | grep JPEG | awk '{ print $3}')
if [ -z "$DIMENSIONS" ]; then
echo "ERROR: $F seems not to be a jpeg"
exit 1
fi
WIDTH=$(echo $DIMENSIONS | cut -d 'x' -f1)
DEPTH=$(echo $DIMENSIONS | cut -d 'x' -f2)

if [ $WIDTH -gt 2048 ] || [ $DEPTH -gt 2048 ]; then
mogrify -resize 2048x2048 $F
else
echo "$F not resized, is only $WIDTH x $DEPTH"
fi
done

As with all old scripts, or hunks you find online, replace active
commands by a comment of what will happen when doing it the first
time, so in this case comment out the 

Re: [Gimp-developer] Doing without pygtk ?

[Ken Moffat via gimp-developer-list]

On Sat, Aug 17, 2019 at 12:22:49AM +0200, Jehan Pagès wrote:
> Hi!
> 
> On Sun, Aug 4, 2019 at 10:32 PM Ken Moffat via gimp-developer-list <
> gimp-developer-list@gnome.org> wrote:
> 
> > On Sun, Aug 04, 2019 at 08:18:26PM +0100, Ken Moffat via
> > gimp-developer-list wrote:
> >
> Is it a question because it is actually going to be impossible to have
> pygtk in some distributions in a close future?
> If so, which distribution, and for when?
> 
It was a problem in Beyond Linux From Scratch, but for the moment we
have reverted to 2.42.4.
> 
> >
> > Builds fine with --disable-python.  Whether all users will find it
> > usable is a different matter ;-)
> >
> 
> Yeah Python has always been an option but it is also a very important
> feature of GIMP. People will not be happy if their scripts suddenly stop
> working.
> 
> This being said, we already dropped pygtk in the master branch (future Gimp
> 3), which now uses GObject Introspection for Python support (both 2 and 3)
> and much more (we tested with success already JavaScript and Lua too, and
> someone is working on Vala if not mistaken).
> 
> Now when will GIMP 3 be released? Nobody can say. We'd really like GIMP
> 2.10 to keep Python 2 support for as long as possible.
> 
> Jehan
> 

It's good to know that master has dropped pygtk.  Here's hoping that
GIMP 3 is ready before python-2 stops getting vulnerability fixes.
Thanks for taking your time to reply.

ĸen
-- 
Adopted by dwarfs, brought up by dwarfs.  To dwarfs I'm a dwarf, sir.
I can do the rite of k'zakra, I know the secrets of h'ragna, I can
ha'lk my g'rakha correctly ... I am a dwarf
   Captain Carrot Ironfoundersson (in The Fifth Elephant)
___
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] help compiling babl

[Ken Moffat via gimp-developer-list]

On Mon, Aug 12, 2019 at 02:33:42PM -0400, Elle Stone wrote:
> On 08/12/2019 01:38 PM, Alexandre Prokoudine via gimp-developer-list wrote:
> > Hello,
> > 
> > You should be using the Meson build system now.
> 
> In case it helps anyone, here are the lines I've been using with meson to
> build babl:
> 
> 
> cd $SRC_DIR/babl
> git status
> rm -r build
> git checkout build
> cd build
> CFLAGS="-march=native -O3 -ffast-math -ftree-vectorize -pipe"
> CXXFLAGS="${CFLAGS}" meson --prefix=$PREFIX ..
> ninja install
> 
> Here are some questions about meson:
> 
> 1. Any suggestions to modify my lines?
> 

Adding '-Dbuildtype=release' to a meson package will turn off debug
assertions, if any (e.g. mesa) and (usually) use -O3 (ISTR that at
least pango uses -O2 for a release build).

> 2. Do the CFLAGS lines actually do anything when using meson?
> 

Do a verbose build using 'ninja -v' to see what flags and defines
are used.  I usually do separate steps for 'ninja' and 'ninja
install', but whatever works for you.  Verbose builds will produce a
_lot_ more output, teeing it to a log so you can read it afterwards
helps (but I'm sure you know that).

> 3. How do I tell meson to use "something" equivalent to the following "make"
> lines?
> 
> ./autogen.sh --prefix=$PREFIX --enable-avx2=false --enable-mmx=no
> --enable-sse=no --enable-sse2=no --enable-sse3=no --enable-sse4_1=no
> --enable-f16c=no --enable-altivec=no --disable-docs
> 

I very much doubt you are on ppc/powerpc, so altivec cannot be used.

In general, meson uses defines (-Dsomething=value, rather like
cmake) for things which are not covered by --prefix= --sysconfdir=.
To see the options for a particular package, look in the
meson_options.txt file.  That might have an option to disable docs,
or it might even be automatic if the deps are missing.

With -march=native I would tend to let gcc sort out sse and similar
options.  I'm assuming you are on x86_64.

The gcc manual gives some options (for X86) about what you can put
in CFLAGS|CXXFLAGS, see the  -mfpath= section.
https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html
(That is for 9.2, probably the only big change from 9.1 is adding
znver2).  And more generally, the -f options are linked from
.../gcc/Option-Index.html

Docs for the latest point release of each gcc version are at
https://gcc.gnu.org/onlinedocs/ if you are using an earlier major
version.

OTOH, if you have the (lots of) time needed to try playing with
these options, and scripts which you can run using 'time' (several
runs for each different build) then perhaps tuning out some of these
things might be worthwhile.  I spent a lot of time in the past couple
of months doing whole-system builds with different flags (mostly for
slight hardening) and ended up concluding there was just too much
variation between runs to get much meaningful data on timing.  And I
didn't have any runtime scripts for gimp-related actions.

ĸen
-- 
Adopted by dwarfs, brought up by dwarfs.  To dwarfs I'm a dwarf, sir.
I can do the rite of k'zakra, I know the secrets of h'ragna, I can
ha'lk my g'rakha correctly ... I am a dwarf
   Captain Carrot Ironfoundersson (in The Fifth Elephant)
___
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] Doing without pygtk ?

[Ken Moffat via gimp-developer-list]

On Sun, Aug 04, 2019 at 08:18:26PM +0100, Ken Moffat via gimp-developer-list 
wrote:
> Everyone knows that python2 is reaching end of life, but until now
> pygtk-2 (which seems to be unmaintained) has continued to build.
> But now pango is under more-active maintenance, and using harfbuzz
> (which is a good thing).  Unfortunately, as part of the changes in
> pango-1.44 to move to hb, a _lot_ of things from pango headers have
> moved into private headers which do not get installed.
> 
> At the risk of offending people who want to use python2 with gimp:
> is it practical to build gimp-2.10 without pygtk-2 ?
> 

Builds fine with --disable-python.  Whether all users will find it
usable is a different matter ;-)

ĸen
-- 
One pill makes you larger, And one pill makes you small.
And the ones that mother gives you, Don't do anything at all.
Go ask Alice, When she's ten feet tall.
   -- Jefferson Airplane, White Rabbit
___
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] Doing without pygtk ?

[Ken Moffat via gimp-developer-list]

Everyone knows that python2 is reaching end of life, but until now
pygtk-2 (which seems to be unmaintained) has continued to build.
But now pango is under more-active maintenance, and using harfbuzz
(which is a good thing).  Unfortunately, as part of the changes in
pango-1.44 to move to hb, a _lot_ of things from pango headers have
moved into private headers which do not get installed.

At the risk of offending people who want to use python2 with gimp:
is it practical to build gimp-2.10 without pygtk-2 ?

ĸen
-- 
One pill makes you larger, And one pill makes you small.
And the ones that mother gives you, Don't do anything at all.
Go ask Alice, When she's ten feet tall.
   -- Jefferson Airplane, White Rabbit
___
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] [Gimp-web] Alexandre Prokoudine attacks on GIMP critics around the Web

[Ken Moffat via gimp-developer-list]

On Wed, Jan 09, 2019 at 05:51:00AM +, Ryan Stark via gimp-developer-list 
wrote:
> One question to ask is why are Procreate and Photoshop so popular with
> digital painters and Photoshop wasn't even originally designed for this?
> One major reason for this is the way the internal textures to the brushes
> are handled. Photoshop isn't even super fast for painting but this feature
> gives lovely brush textures. Clip Paint Studio does this but it does it in
> a crap way.
> 
I will note in passing that top-posting on developer mailing lists
is generally regarded as bad form (on user lists it seems to be less
unacceptable, although still a PITA), and even gmail can be beaten
into shape for that.  But these 'digital painters' will need to
speak up for themselves on either the -dev or -user lists before
anyone will pay attention.

Meanwhile, the gimp developers have made vast progress in the last
year, for which I thank them (even if I don't agree with all their
decisions re importing raw photos ;) : there are few developers, and
they do not have infinite time to work on whatever interests them.
I will suggest that this thread is a distraction to them and will go
nowhere unless you are either willing to provide code, or to find
someone whom you can sponsor to produce the code.

I hope I will speak for most people here when I say that I don't use
Photoshop and I had never heard of Procreate until you mentioned it.
As a user of libre software, to me they appear to be irrelevant.

ĸen
-- 
Take three of these a minute for four minutes.  Don't take with
alcohol or you'll grow an extra head.
  -- The Doctor
___
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] [Gimp-web] Alexandre Prokoudine attacks on GIMP critics around the Web

[Ken Moffat via gimp-developer-list]

On Tue, Jan 08, 2019 at 06:23:27PM +, Ryan Stark via gimp-developer-list 
wrote:
> If you aren't a heavy critic of Gimp there is something wrong with you.

Since I no-longer have the mail this was apparently replying to, and
given (from the subject) its apparent personal attack, I regard
this as just another troll, probably politically motivated (for my
definition of political), and if it wasn't for the fact that some
people who I respect for their contributions had already replied, I
would have given the standard "do not feed trolls" reply.

-- 
Take three of these a minute for four minutes.  Don't take with
alcohol or you'll grow an extra head.
  -- The Doctor
___
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] how to build json-glib in a prefix when building gimp from git in a prefix?

[Ken Moffat via gimp-developer-list]

On Sun, Sep 30, 2018 at 10:44:38AM +0200, wwp wrote:
> Hello Ken,
> 
Hi wwp,
> 
> On Sun, 30 Sep 2018 02:33:34 +0100 Ken Moffat via gimp-developer-list 
>  wrote:
> 
> > On Sun, Sep 30, 2018 at 12:00:40AM +0100, Ken Moffat via 
> > gimp-developer-list wrote:
> > > On Sat, Sep 29, 2018 at 06:21:36PM -0400, Elle Stone wrote:  
> > > > 
> > > > I don't know what version json-glib from git is on. I cloned it as 
> > > > follows:
> > > > git clone https://gitlab.gnome.org/GNOME/json-glib But I'd be happy to
> > > > download a specific tarball, if anyone knows what version of json-glib 
> > > > is
> > > > currently required by GIMP.
> > > >   
> > Are you sure you need json-glib ?
> > 
> 
> Json-glib *is* needed to build gimp 2.10. I build gimp 2.8/2.10 on
> CentOS 6 and 7 boxes, where no package is available (for the latest 2.8
> and 2.10 at all), and I build quite all the necessary deps (it's a lot
> and the cross-deps are a nightmare), json-glib is required at some
> step. From what I see in my build script, gegl 0.3/0.4 need it.
> 

Yeah, you are right.  I thought it must be a new dep for gimp
itself.  And I didn't remember using it.  But now that I look at my
scripts I can see that it is GEGL which needs it.

So for Elle, the version is whatever your GEGL needs.  A quick look
at https://gitlab.gnome.org/GNOME/gegl/blob/master/configure.ac
suggests json-glib-1.0 which both json-glib-1.2 and -1.4 (and
probably even -1.0) provided.

ĸen
-- 
  Well grubbed , old mole!
___
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] how to build json-glib in a prefix when building gimp from git in a prefix?

[Ken Moffat via gimp-developer-list]

On Sun, Sep 30, 2018 at 12:00:40AM +0100, Ken Moffat via gimp-developer-list 
wrote:
> On Sat, Sep 29, 2018 at 06:21:36PM -0400, Elle Stone wrote:
> > 
> > I don't know what version json-glib from git is on. I cloned it as follows:
> > git clone https://gitlab.gnome.org/GNOME/json-glib But I'd be happy to
> > download a specific tarball, if anyone knows what version of json-glib is
> > currently required by GIMP.
> > 
Are you sure you need json-glib ?

I just cloned https://gitlab.gnome.org/GNOME/gimp.git a few minutes
ago.  I cani't run ./autogen.sh (don't have gtk-doc, and no intention
of installing that source of pain), but grepping for json-glib only
finds:

ken@origin /scratch/ken/git/gimp $find -type f | xargs grep json-glib 
./build/windows/jhbuild/gimp.moduleset: 
./build/windows/jhbuild/misclibs.moduleset:
./build/windows/jhbuild/misclibs.moduleset: 
module="json-glib/1.2/json-glib-1.2.2.tar.xz"
./build/docker/gimpbuilder-base/Dockerfile:RUN apt-get install $APT_GET_OPTIONS 
intltool libglib2.0-dev libjson-c-dev libjson-glib-dev libgexiv2-dev 
libcairo2-dev libpango1.0-dev libjpeg62-turbo-dev libsuitesparse-dev 
libspiro-dev libopenexr-dev libwebp-dev

which suggests that only docker and windows need it.  And grepping
for JSON in capitals finds some perl modules in a git hook, and
JSON_C_LIBS references in the Makefile.am files under app/ - json-c
(0.12.1) is again referenced in windows and docker files.

ĸen
-- 
  Well grubbed , old mole!
___
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] how to build json-glib in a prefix when building gimp from git in a prefix?

[Ken Moffat via gimp-developer-list]

On Sat, Sep 29, 2018 at 03:23:24PM -0400, Elle Stone wrote:
> Anyone know the precise terminal commands for building json-glib in a prefix
> using meson? I'm trying to update this article:
> 
> https://ninedegreesbelow.com/photography/build-gimp-in-prefix-for-artists.html
> 
> I already established the prefix using these commands:
> 
> 
> PREFIX=$HOME/code/gimpdefault/install
> export PATH=$PREFIX/bin:$PATH
> export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH
> export XDG_DATA_DIRS=$PREFIX/share:$XDG_DATA_DIRS
> export ACLOCAL_FLAGS="-I $PREFIX/share/aclocal"
> export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH
> export PKG_CONFIG_PATH=$PREFIX/share/pkgconfig:$PKG_CONFIG_PATH
> export GIO_EXTRA_MODULES=/usr/lib64/gio/modules
> export SRC_DIR=$HOME/code/gimpdefault/build
> 
> I'm building on OpenSUSE Tumbleweed. Probably I need to install meson
> something or other, so does anyone know what package(s) to install? And then
> of course what commands to type.
> 
> Best,
> 
> and thanks in advance for any help!
> 
> Elle
> 
Hi Elle,

I don't know how OpenSUSE splits packages into sub-packages (-dev or
something for headers), but the upstream packages you will need are
meson, ninja, and python3.

For building meson in /usr, see
http://www.linuxfromscratch.org/blfs/view/svn/general/json-glib.html

Note that is still on 1.4.2 which is probably older than what you
are going to build.

I don't think the _process_ of using meson has changed recently:
create a build directory, change to it, invoke meson with whatever
switches you need (a minimum of --prefix=) followed by .. to point
to where the meson files are.

For some options you may need cmake-style -Dfoo=bar.

I have found it necessary to export LC_ALL with a UTF-8 value, e.g.
en_GB.UTF-8, if invoking meson from a script running under the C or
POSIX locales.

And ninja will use all your cores, although for json-glib that is
probably immaterial.

So, use meson to create the Makefile(s), ninja to build, ninja
install.  For a DESTDIR-style install to check what is going to be
installed:
 DESTDIR=/tmp/JG ninja install
(i.e. put the DESTDIR first)

In BLFS we target linuxfromscratch which includes meson and ninja,
so those are not listed as dependencies, and the build time uses
LFS's "standard build units" (SBU) - for json-glib the time should
only be a few seconds on any modern machine.  Other deps are
whatever any 'Required' or 'Recommended' packages specify - but
since you probably already have glib and gobject-introspection I
guess you have everything necessary.

Also, in BLFS we only use lib, not lib64, I'm not sure if that will
affect meson.  Old docs from fedora suggest --libdir, but I don't
immediately see that in their latest build, so I suggest you try
without, and if it builds do a DESTDIR install to see if the files
are where you expect them to be.

For building with meson the important files are meson.build and
meson_options.txt.

From the first, for json-glib-1.4.2 meson needs to be >= 0.40.1,
glib >= 2.44.0, and from the second, introspection defaults to true
but can be set to false if you don't have gobject-introspection, and
the docs are not built by default (needs gtk-doc and xsltproc).  But
check the required version of meson in the version of json-glib you
are going to build.

HTH

ĸen
-- 
  Well grubbed , old mole!
___
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] Problem with most png images when building gimp-help

[Ken Moffat via gimp-developer-list]

Hi,

Not sure if this is the right place to ask about a problem when
building gimp-help from git ?  If it isn't, where should I ask,
please ?

And if it is -

my basic process seems to work and I even get the mushroom 2.10
image in the index.  Building only 'en', I have the arrows etc for
navigation (in xml/en/images/ in the build dir) and I also have
using/wilber.png below that directory as well as in
images/C/using/wilber.png.

But when I look at gimp-first-steps.html the image is missing for
Figure 3.1. Wilber, the GIMP mascot.

And in the html for this I have:



With an empty src reference.  I've tried adding --enable-network,
but that made no difference (I've got a fairly full docbook-xslt
stack here).

Then I built pngnq (fun, but a simple sed lets it build) and
pngcrush : no difference.

But when I build the gimp against gvfs and read the online help I
can see that this image of Wilber appears.

ĸen
-- 
   Entropy not found, thump keyboard to continue

___
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] ANNOUNCE: GIMP 2.10.0-RC2 released

[Ken Moffat via gimp-developer-list]

On Fri, Apr 20, 2018 at 04:16:10AM +0100, Ken Moffat via gimp-developer-list 
wrote:
> On Wed, Apr 18, 2018 at 01:26:19AM +0200, Michael Natterer wrote:
> > Hi,
> > 
> > We just released the second release candidate on the way
> > to the final GIMP 2.10.0 release.
> > 
> > This is (still!) an unstable development release and might
> > crash or do whatever. If you try it for work, please save
> > your images more often.
> > 
> I had hoped to install this in a fresh all-from-source LFS/BLFS
> build (RC1 on a different machine worked, but a separate plugin
> rebooted the machine, which might well be a Ryzen problem) because I
> know that my own script-fu script needs to be updated.  But to my
> surprise it failed to build because pygtk-2.24.0 had no-longer
> installed its headers.

Fixed that (a change in how an earlier module needs to be
built/installed) but now when I fire it up the splash screen says
RC1 although Help -> About says RC2.  Trivial, but perhaps another
item for the pre-release checklist ?

ĸen
-- 
This email was written using 100% recycled letters.
___
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] ANNOUNCE: GIMP 2.10.0-RC2 released

[Ken Moffat via gimp-developer-list]

On Wed, Apr 18, 2018 at 01:26:19AM +0200, Michael Natterer wrote:
> Hi,
> 
> We just released the second release candidate on the way
> to the final GIMP 2.10.0 release.
> 
> This is (still!) an unstable development release and might
> crash or do whatever. If you try it for work, please save
> your images more often.
> 
I had hoped to install this in a fresh all-from-source LFS/BLFS
build (RC1 on a different machine worked, but a separate plugin
rebooted the machine, which might well be a Ryzen problem) because I
know that my own script-fu script needs to be updated.  But to my
surprise it failed to build because pygtk-2.24.0 had no-longer
installed its headers.

So, my general view is that python is even more of a PITA that I had
assumed (pygtk-2.24.0 installed its headers in previous builds, and
for this build my pygtk script and my toolchain had not changed),
but does anybody have any suggestions on this ?

Or maybe I should just give up, or else give up the snake (and swear
volubly at anyone who suggests that using python for scripts is
easier ;)

Meanwhile, congratulations to the developers, but I'm sorry that
I can't build/use this.

ĸen
-- 
In my seventh decade astride this planet, and as my own cells degrade,
there are some things I cannot do now: skydiving, marathon running,
calculus. I couldn't do them in my 20s either, so no big loss.
-- Derek Smalls, formerly of Spinal Tap
___
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] ANNOUNCE: GIMP 2.10.0-RC2 released

[Ken Moffat via gimp-developer-list]

On Wed, Apr 18, 2018 at 01:26:19AM +0200, Michael Natterer wrote:
> Hi,
> 
> We just released the second release candidate on the way
> to the final GIMP 2.10.0 release.
> 
> This is (still!) an unstable development release and might
> crash or do whatever. If you try it for work, please save
> your images more often.
> 
Asking here, just in case -

I was hoping to install this on a fresh linux build (LFS/BLFS, all
from source using my existing scripts) : -RC1 installed on another
machine, and from that I know that I need to modify my own script-fu
package.  BUT - the gimp barfed because 

-- 
In my seventh decade astride this planet, and as my own cells degrade,
there are some things I cannot do now: skydiving, marathon running,
calculus. I couldn't do them in my 20s either, so no big loss.
-- Derek Smalls, formerly of Spinal Tap
___
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] Using Gimp 2.8

[Ken Moffat via gimp-developer-list]

On Wed, Dec 13, 2017 at 08:20:55PM +0100, Ofnuts wrote:
> > 
> > I have nothing against DarkTable, RawTherapee, or Photozone - but
> > they are all different and set up to do things their own way.  For
> > somebody who mainly uses the gimp, ufraw or nufraw seem to have a
> > much less steep learning-curve.
> 
> Yes, but they have much more complete processing.

But this is a gimp list - I have no problem with using different
tools, but it takes a long time before a user can see how well they
support what that user wishes to do.

> > But some of that is the difference between people taking good photos
> > on good equipment, and a hacker taking snatched photos on "adequate"
> > equipment.  For example, in many of my W/A shots I have to correct
> > visible barrel distortion (subjects with a straight line in the
> > outer part of the view) and with zoom lenses I find that using the
> > gimp's lens distortion filter I can correct this with a negative
> > value in the first (main) field, but that value may differ between
> > shots taken at different times with the same recorded EXIF focal
> > length.  It's all horses for courses.
> 
> These days one uses the lensfun library that has correction data for most
> cameras and lenses (and you can create your own calibration data if needed).
> This  is faster and more accurate than eyeballing a correction. Gimp may
> have a lensfun plugin now,  but these apps all know how to use it natively.

I tried lensfun when it was first an option in ufraw, at that time
it had nothing for me.  But my main comments are apropos my
panasonic - I have the impression that perhaps the elements can move
slightly, particularly if the camera is tilted, and in any case the
*reported* focal lengths are discrete - perhaps it does zoom in a
series of steps, but my experience is that different photos need
different adjustments from the norm.

So, for me manual correction is the only way.  If the automatic
correction works for you and your cameras, be happy.

ĸen
-- 
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
 - Unseen Academicals
___
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] gcc-7 vs gcc-6

[Ken Moffat via gimp-developer-list]

On Fri, Nov 10, 2017 at 09:41:41PM -0500, Carol Spears wrote:
> On Fri, Nov 10, 2017 at 6:45 PM, Ken Moffat via gimp-developer-list <
> gimp-developer-list@gnome.org> wrote:
> 
> > On Fri, Nov 10, 2017 at 04:52:43PM -0500, Elle Stone wrote:
> > > On 11/10/2017 02:42 PM, Carol Spears wrote:
> > > > After a couple of catastrophes, I reinstalled my operating system ...
> > and
> > > > eventually rebuilt gimp.
> > > >
> > > > The gcc-7 gimp failed to open with a
> > > > gimp: symbol lookup error: gimp: undefined symbol:
> > > > gimp_convert_dither_type_compat_get_type
> > > >
> > > > The gcc-6 gimp works fine.
> > > >
[...]
> > I have no idea.  Her post implies that both gcc-6 and gcc-7 versions
> > are on the same machine, which seems an uncommon approach (assuming
> > both are the same version and this isn't just to test for gcc
> > regressions).
> >
> > Same machine.  Same updated clone for years.
> 
> I was also compiling with gimp with gcc-7 successfully before my couple of
> catastrophes, so I don't know why it would start to fail with the new os.
> 
> I was confused because I read something about compiler problems on
> this list, but I wasn't having them.

Sure.
> 
> ==multiple compilers installed==
> My software installer just announces that it is updating what it considers
> to be "gcc", copies that binary into the directory of its choice and simply
> ignores the previous gcc.  Compiler cruft!  When today started I had
> gcc-4 from the installer and gcc-7 which I installed with the "real"
> software.
> I was thinking about getting gcc-5 just so I would have a complete set.
> 
> I am pretty sure that each new number of compiler is a new version,
> hence the number.

Nowadays, a new major version each year - and that tends to mean
changes in which version of the c++ standard it supports.
> 
> I don't think I am the only person who has more than one version of gcc.
> 
> carol

Certainly not, my point was that building a current package with two
different versions of the compiler is unusual : most people install
applications into /usr, a few prefer BSD-style /usr/local.  But to
have both versions available you need to go out of your way to
ensure that the first install is not overwritten by the second.

ĸen
-- 
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
 - Unseen Academicals
___
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] gcc-7 vs gcc-6

[Ken Moffat via gimp-developer-list]

On Fri, Nov 10, 2017 at 04:52:43PM -0500, Elle Stone wrote:
> On 11/10/2017 02:42 PM, Carol Spears wrote:
> > After a couple of catastrophes, I reinstalled my operating system ... and
> > eventually rebuilt gimp.
> > 
> > The gcc-7 gimp failed to open with a
> > gimp: symbol lookup error: gimp: undefined symbol:
> > gimp_convert_dither_type_compat_get_type
> > 
> > The gcc-6 gimp works fine.
> > 
> > Were my problems related to gcc-7?
> 
> In case it might be relevant, this bug indicates a problem specifically with
> gcc-7.2:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=787222#c5
> 
> Best,
> Elle
> 
I can't comment on that specific bug (I haven't converted anything
to 16-bit float), but I've used gcc-7.2.0 to build both 2.9.6 and
2.8.22 on different machines without any problems (both using
gegl-0.3.20, 2.8.22 modified as in BLFS to do that) and both appear
to work, they certainly start OK.

My impression of symbol lookup errors (after a quick google) is that
they are caused by mismatched versions of libraries.

In one thread at an opensuse forum (for that same symbol)  the
problem was apparently caused by getting binaries from a differnt
repo, and soembody had to also get libgimp (they separate it!),
lcms, babl, and gegl from the other repo.

But if by 'rebuilding' Carol meant "recompiled on the same machine"
I have no idea.  Her post implies that both gcc-6 and gcc-7 versions
are on the same machine, which seems an uncommon approach (assuming
both are the same version and this isn't just to test for gcc
regressions).

But I haven't tried building applications with a newer version of
gcc on a system built with an older gcc for many years, perhaps I'm
overlooking something (e.g. changed calling conventions in the newer
C++ standard).

Looking at my 2.9 version, the symbol is in both libgimp-2.0.so and
libgimpbase-2.0.so, but not in any of the modules.  So I suppose the
way in is to use ldd to look at what those libs link to (and to
check that the gcc-7 versions are being used).

ĸen
-- 
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
 - Unseen Academicals
___
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] Masks not very effective in 2.9 scheme script

[Ken Moffat via gimp-developer-list]

On Sat, Jul 15, 2017 at 08:21:32AM -0400, Ell via gimp-developer-list wrote:
> On Tue, 11 Jul 2017 00:38:17 +0100
> Ken Moffat  wrote:
> 
> > Hi,
> > 
> > TL;DR - using masks in a 2.8 scheme script works as intended to
> > extract parts of an image, but after converting it for 2.9 it does
> > much less.
> 
> The most likely reason for the different results, is that in 2.9 masks
> use the pixels' linearized intensity as the alpha value, while in 2.8
> they use the gamma-corrected intensity.  The linearized intensity
> values are generally lower than the gamma-corrected ones, so the
> resulting mask values, after pasting a desaturated image into the mask,
> are lower in 2.9 than they would be in 2.8, resulting in a subtler
> effect.  Note that these sorts of interactions is something we're still
> working on.
> 

Thanks for the detailed reply.  I'll have to get back on the 2.9
machine at some point to work through the options.  Meanwhile, I've
saved a full copy of your mail in my notes.

Cheers.

ĸen
-- 
I live in a city. I know sparrows from starlings.  After that
everything is a duck as far as I'm concerned.  -- Monstrous Regiment
___
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