Re: [Gimp-developer] Testers requested for our new Mac OS X DMG release!,

[Partha Bagchi]

Hi Alex,

While I am not against your policy, this is first I am hearing about
this agreement. Of course this may have been a verbal agreement within
the team.

Anyway, I am happy to provide any information the team needs about my builds.

Note that I provide my builds as a community service without asking
for any remuneration whatsoever in return.

Thanks,
Partha

On Mon, Dec 28, 2015 at 5:16 AM, Alexandre Prokoudine
 wrote:
> On Mon, Dec 28, 2015 at 12:19 PM, scl wrote:
>
>> How about mentioning the patched and extended builds of other eager
>> contributors like Partha and skl or even Gimp Paint Studio and
>> CinePaint in a separate fork section of the Download page?
>
> The general agreement in the team is that we don't feel comfortable
> promoting builds whose packagers do not provide information about
> changes they introduced (if any). To make this more transparent for
> the community, we are preparing a document on packaging requirements
> that we'd like (but don't demand) GIMP packagers to meet.
>
> GIMP Paint Studio is currently unmaintained.
>
> Cinepaint is an inactive project.
>
> Alex
> ___
> 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

Re: [Gimp-developer] Stock Windows and OS X builds of GIMP 2.9.2?

[Partha Bagchi]

Sven,

I use NSIS based installer. I can provide the code if necessary.

Forgot to say, Welcome back and a Happy New Year. :)

Thanks,
Partha


On Thu, Dec 31, 2015 at 11:21 AM, scl  wrote:
> Hi,
>
> I have to correct myself. There's also a Windows 64 bit installer from
> Partha at partha.com - thank you, Partha.
> It uses an installer visually similar to Jernejs release build.
> Is it based on that installer code so the problem of unifying the
> nightly and release Windows builds is a bit closer to a solution?
>
> Greetings
>
> Sven
>
>
___
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] CMYK in GIMP

[Partha Bagchi]

Hi Sven,

Happy New Year to you too!

Separate+ is implemented in my builds.

Thanks,
Partha

On Fri, Jan 1, 2016 at 3:44 AM, scl  wrote:
> Hi,
>
> first of all have all a happy new year!
> Professional users regularly ask for CMYK support in GIMP.
> I know the team's position about it and for time until it
> is implemented I'd like to point to the [plug-in Separate+].
> As it seems there is no Mac version yet. Does anybody have
> more information about where to find it?
>
> Greetings
>
> Sven
>
> [plug-in Separate+]
> http://registry.gimp.org/node/471
> ___
> 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

Re: [Gimp-developer] Missing from the roadmap

[Partha Bagchi]

Hi Sven,

Elle has published a 2-part article on using GIMP for high bit depth
at Pat David's Pixl.us.

I am linking to part 1 for your convenience:

https://pixls.us/articles/users-guide-to-high-bit-depth-gimp-2-9-2-part-1/

Hope that helps.

Thanks,
Partha


On Tue, Jan 12, 2016 at 1:26 AM, Sven Claussner  wrote:
> Hi,
>
> just for a better understanding:
> - Is it for something that goes beyond assigning and converting to
> other color spaces? I think of native support of larger gamut color
> spaces than sRGB in Babl, GEGL and GIMP, am I right?
> - What exactly means 'supporting gamma-encodings other than the sRGB
> TRC' for intense GIMP users (artists and scientists)?
> - Is it something that happens only in GEGL and Babl or would also
> GIMP's code need to be touched?
>
> Greetings
>
> Sven
> ___
> 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

Re: [Gimp-developer] Scanning coins

[Partha Bagchi]

Well, you can acquire an image from a scanner if you have twain plugin
built. :)

On Sun, Jan 17, 2016 at 9:32 AM, Ofnuts  wrote:
> On 13/01/16 18:11, billgoldbe...@frontier.com wrote:
>>
>>
>>
>>  Greetings, I have heard Gimp is great for scanning images of coins to
>> be sold internet. Can you tell me to set up Gimp to do this?Regard,William.
>> Sent from my Verizon 4G LTE Tablet
>>
>
> Gimp has no built-in scanning capabilities. Even if you can scan from Gimp,
> it will rely on some external application to do the scanner capture. Gimp is
> then used to edit the image. Most/all scanners come with a scanner
> application...
> ___
> 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

Re: [Gimp-developer] Adding better LCH support to GIMP 2.10

[Partha Bagchi]

First hit when you google:
http://www.colourphil.co.uk/lab_lch_colour_space.shtml


On Sun, Feb 14, 2016 at 6:33 PM, Elle Stone 
wrote:

> On 02/14/2016 03:56 PM, Sven Claussner wrote:
>
>> Hi,
>>
>> @Elle: you are speaking here of the JCH color model (or space) and
>> mentioned
>> on your website [1] that JAB and JCH have outdated LAB and LCH
>> (which are often considered the high end image editing color
>> spaces/models).
>> Searching a while for more information about JCH I found only very few
>> information, even not on other color management and FOSS graphics devel
>> mailing lists. Only on the PXLab website [2] I see a short description:
>>
>> JCH:=The CIE Color Appearance Model (1997) with viewing and scene
>> conditions
>> to be defined separately.
>>
>> I'm failing to understand all its implications.
>> Can you tell us more about JCH and JAB and why you consider it to
>> be a good choice, please? What about LAB and LCH then?
>>
>
> I can't tell you very much about JCH/JAB because I'm still trying to
> figure it all out myself.
>
> You might try plowing your way through this PDF:
> http://rit-mcsl.org/fairchild/PDFs/AppearanceLec.pdf
>
> This page has links to some equations:
> https://en.wikipedia.org/wiki/CIECAM02
>
> This page briefly talks about color appearance models in more
> down-to-earth terms:
> http://www.rit-mcsl.org/fairchild/WhyIsColor/Questions/4-8.html
>
> An internet search on terms like Color appearance model, Mark Fairchild,
> and CIECAM02 will turn up a lot of material. None of it is easy reading.
>
> LAB answers the question "how far apart do colors have to be before the
> average human observer will say 'those are different colors'". The "home"
> of LAB was for use with quality control for colors in textiles, printing,
> and such. LAB wasn't designed to be used as a color space for editing, but
> it works pretty well for a lot of different editing tasks.
>
> A full understanding of LAB would require understanding the kinds of
> experiments that were done to map out "when is color X different enough
> from color Y to be seen as visually different?" I have no idea what kind of
> experiments were done or how the mathematical model was constructed from
> the experimental results. But the resulting equations to convert from XYZ
> to LAB and then LCH are pretty straightforward.
>
> Color appearance models are designed to answer a very different and much
> more complicated set of questions. They try to answer questions like "How
> to describe colors?", "Why does the appearance of one color change when
> juxtaposed next to another color?", and "Why does a surface look the same
> color even when the light shining on it changes drastically (for example
> from bright daylight to deep shade or to tungsten lighting, or even in the
> shadow side of an object)?".
>
> These are complicated questions, being answered using complicated research
> and complicated resulting models described by complicated sets of
> equations. Also color appearance models are a very active area of ongoing
> research, so what's considered really good today might be superceded
> tomorrow.
>
> My reasons for suggesting that for use in GIMP (1)LAB/LCH is good and
> (2)JAB/JCH is probably better are so simplistic that you'll all just laugh:
>
> 1. Bruce MacEvoy's handprint.com website on watercolor pigments switched
> from using LCH to using JCH to give paint pigment colors, and I respect
> Bruce MacEvoy as an authority on giving useable values for paint pigments:
> http://handprint.com/HP/WCL/water.html,
> http://handprint.com/LS/CVS/color.html
>
> 2. Mark Fairchild seems to think CIECAM02 is a pretty good color apperance
> model, though again this is a field of active research, and much of what
> Mark Fairchild writes goes right over my head.
>
> 3. ArgyllCMS and LCMS already incorporate the equations for JAB/JCH in
> their code, as does RawTherapee, so it has to be not too difficult to code
> up for GIMP. But my (very limited) efforts to make sense of the
> ArgyllCMS/LCM/RT code have so far been unsuccessful.
>
> I find the LCH blend modes, color picker, and Hue-Chroma tool to be
> incredibly useful. The few people who've written to me about using my
> patched GIMP seem very enthusiastic.
>
> JCH apparently is more accurate than LCH for describing colors. I'm not
> sure how much difference the "more accurate" would make in the digital
> darkroom. It would be nice to be able to give JCH a try, but in the
> meantime I can't imagine going back to editing without LCH.
>
> Does somebody else here know more about it?
>>
>
> No doubt even my short description above needs a lot of corrections!
>
>
>
>> Thank you in advance
>>
>> Sven
>>
>>
>> [1]
>>
>> http://ninedegreesbelow.com/photography/high-bit-depth-gimp-tutorial-edit-tonality-color-separately.html
>>
>>
>> [2]
>>
>> http://irtel.uni-mannheim.de/pxlab/doc/api/de/pxlab/pxl/ColorSpaceCodes.html#CS_JCh
>>
>>
>> ___
>> gimp-dev

Re: [Gimp-developer] A new gimp plugin for extraction of image regions

[Partha Bagchi]

Google says your message could be dangerous. Something I should know?

Thanks,
Partha

On Fri, Feb 19, 2016 at 1:32 PM, Bérengère MATHIEU <
berengere.math...@irit.fr> wrote:

> Problem fixed!
> It should be accessible with the following link now :
> http://image.enfa.fr/scis/scis.zip
>
> Best regards,
>
> Bérengère
> On Friday, February 19, 2016 16:04 CET, Elle Stone <
> ellest...@ninedegreesbelow.com> wrote:
>
> > On 02/19/2016 09:30 AM, Bérengère MATHIEU wrote:
> > > I have only  tested my plugin on GImp 2.8. Concerning the problem when
> downloading the archive,  I have send an email to the image.enfa.fr
> admin. In the meantime,  you can download source code and executable for
> windows here :
> > > https://www.dropbox.com/s/vjcaq5j4t8yxl9f/scis.zip?dl=0. Sorry  for
> the inconvenience.
> >
> > Thanks! and no need to apologize! Actually I run Linux but there's no
> > rush, I can wait for the archive link to be fixed.
> >
> > Best,
> > Elle
> >
>
>
>
>
>
> ___
> 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

Re: [Gimp-developer] suggestions

[Partha Bagchi]

Totally agree with you. Color management would definitely be a priority for
high-end photo editing software. Also, I would think that nondestructive
editing would be high on the list (Photoshop's "Smart Objects").

If I am not mistaken, Alex has already mentioned adjustment layers numerous
times in past as a requirement/missing feature in GIMP.

On Mon, Apr 4, 2016 at 9:56 AM, Elle Stone 
wrote:

> On 03/27/2016 02:44 PM, C R wrote:
>
>> I've found that anything else would be a waste of
>> (everyone's) time. For some, nothing but Photoshop will work for their
>> graphics needs. It's no use arguing with them, because they have already
>> made up their mind, and it's more important to think they are correct than
>> it is to learn new things and expand your graphics tool-set.
>>
>
> Putting the serious limitations of 8-bit editing to one side, even high
> bit depth GIMP 2.9/2.10 lacks critically important components of the
> workflows of (lacking statistics, at least some) professional photographers
> currently using PhotoShop.
>
> For example, for at least some professional photographers, their workflow
> depends on:
>
> * The ability to edit in RGB working color spaces other than sRGB.
>
> * The ability to easily record and replay repetitive steps ("macros").
>  Without this ability, any degree of complexity in a high volume
> workflows means "high volume" isn't a realistic possibility unless you can
> figure out how to make the workday longer, in which case you are facing
> repetitive stress syndrome from typing in the same steps over and over, no
> doubt accompanied by mind-boggling amounts of tedious boredom.
>
> * The ability to use adjustment layers.
>  Without adjustment layers (or nodes which might even be better) for
> operations like Curves, Levels, Channel Mixer, etc the user canNOT go back
> and tweak intermediate results.
>
> However if you
>> can post a tutorial or links to show how the same effects can be done in
>> GIMP, it will go a long way to get others around to seeing what an
>> excellent tool GIMP is for pro-grade graphics work.
>>
>
> I am speaking specifically of photographic editing. I can't speak to
> graphics editing. In your estimation, is it the case that a pro-grade
> graphics workflow:
>
> * Doesn't ever require editing in RGB working spaces other than sRGB?
>
> * Doesn't ever require involve performing the same sequence of steps over
> and over again.
>
> * Wouldn't be made considerably more efficient by having adjustment layers?
>
> Best,
> Elle
>
> ___
> 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

Re: [Gimp-developer] Windows builds using MSYS2

[Partha Bagchi]

What have you tried so far to get Python working? All I see is "python is
not working".

Just as FYI, I've been providing Windows 64bit and Mac builds for almost 5
years now.

On Mon, May 9, 2016 at 7:47 AM, Petteri Soininen  wrote:

> I have a build working from latest master with Msys2, and I'm in progress
> of making notes to how to do it. Still haven't got python working ok as
> running Gimp gives me "Failed to execute child process (No such file or
> directory)" errors on every py script when launching, but I'll post my
> notes so far..
>
> http://pastebin.com/ZHT2A4K5
>
> Hopefully that helps.
> (and I'm using WIn10, 64bit)
>
> On 9.5.2016 13:03, Barney Holmes wrote:
>
>> Hi,
>>
>> I've also been working on building Gimp for Windows simply because for
>> one reason or another I have Windows on my main, faster machine, and I've
>> wanted to get some of the latest bug fixes. I also wanted to fix -
>> https://bugzilla.gnome.org/show_bug.cgi?id=757717
>>
>> I tried the Linux cross compile using the wiki Mingw64 instructions. I
>> was trying to retrieve the prebuilt library RPM's from, I think it's
>> OpenSUSE, but that seems to be outdated. Now I have Code::Blocks setup to
>> cross compile with MinGW-w64, I’ll try building those dependencies.
>>
>> I'm investigating MSYS2. It looks like a good project and a lot of other
>> projects seem to use it to provide releases for Windows, but its a slow to
>> compile even with multiple threads set.  Some of those projects may use
>> Python so they might be able to help with Python for Gimp.
>>
>> I attach my current "autogen" and "make" outputs. I am building with most
>> extras disabled as I just want to iron out the build process first.
>>
>> http://files.djbarney.org/autogen_output.txt
>> http://files.djbarney.org/make_output.txt
>>
>> Are you building from the main branch ?
>>
>> Do you get a successful build with Python disabled ?
>>
>> Cheers.
>>
>> Sent from Mail for Windows 10
>>
>> ___
>> 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

Re: [Gimp-developer] Error during Make - Last update of Git Master, today

[Partha Bagchi]

I just had this conversation with Mitch. Just do the following

touch libgimp/gimpenums.h


and do make again.

Hope that helps.


On Wed, Jun 8, 2016 at 4:32 PM, Americo Gobbo  wrote:

> On Wed, Jun 8, 2016 at 1:33 PM, Michael Schumacher 
> wrote:
>
> > Hi Americo,
> >
> > pasting this to https://paste.gnome.org/ will make it much easier to
> > access.
> >
>
>
> Hi Michael,
> I have updated now GIMP git master, but yet is with error on make.
> https://paste.gnome.org/pl0wgxbiu
> Thanks
> americo
>
> ===
> 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

Re: [Gimp-developer] Ctrl-Shift-clicking your way to a new layermask

[Partha Bagchi]

Seriously?? :) He is only the lead GIMP developer.

On Mon, Jun 13, 2016 at 6:21 AM, C R  wrote:

> Who is Mitch?
>
> On Mon, Jun 13, 2016 at 8:57 AM, Joseph Bupe 
> wrote:
>
> >
> > On 10 June 2016 at 18:06, C R  wrote:
> >
> >> [image: Boxbe]  This message is
> eligible
> >> for Automatic Cleanup! (caj...@gmail.com) Add cleanup rule
> >> <
> https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey%3DRRw%252FTGfa77MVzy4Es24l79Kzz81bHpclnptE9Jw49Dg%253D%26token%3DRy6i1LHoty9RBJJPXE3404aKmYWkEDB8WB1x89Nv9fRSNkmP8cB%252F0VSsrOKfTW%252Bcb0N6wDZgi1Sd%252BgKq2dBdM23BsIRW%252BKVdtpB1fCyu%252ByGeVuJHVsyYCCrjISZ73VhMTqfkPyiRHqw%253D&tc_serial=25714979786&tc_rand=526132613&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001
> >
> >> | More info
> >> <
> http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=25714979786&tc_rand=526132613&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001
> >
> >>
> >> Can I bribe someone to commit/add this to trunk (even on a trial basis)?
> >> :)
> >>
> >> -C
> >>
> >
> > Ask 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-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] Ctrl-Shift-clicking your way to a new layermask

[Partha Bagchi]

No, he is the lead developer. You do realize that GIMP is being actively
developed?

Maintainer means totally different thing.

On Mon, Jun 13, 2016 at 8:40 AM, Joseph Bupe  wrote:

>
>> Seriously?? :) He is only the lead GIMP developer.
>>
>
> Maintainer, to be more specific.
>
>
>
___
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 and Compiling gimp under Windows

[Partha Bagchi]

Feel free to contact me as well if you need help. Alex already pointed you
to my website.

Partha

On Fri, Jul 1, 2016 at 8:27 AM, Jehan Pagès 
wrote:

> Hi,
>
> On Thu, Jun 30, 2016 at 7:44 PM, Hashem Zavvari 
> wrote:
> > Hi gimp masters,
> >
> > I'm new in hacking the gimp. I spend a couple of days to get detail
> > information about modifying gimp program and customizing it as windows
> > application for my project, since it is a great and useful open source
> > image manipulation ever.
> > I googleing and wiki.gimp to begin this job, but I don't see any proper
> > detail guidance and enough resources for hacking. Purpose is hacking by
> my
> > experiences and tools in hand:
> > My OS is: Windows 10 x64
> > expert in: Visual studio, dot net, C#, WPF and so on (obviously I can't
> > hacking gimp under VS).
> > familiar with: C, C++, Java
> > don't know about gegl, gtk+, babl and so on.
> > First problem correct load and successful build gimp-master source from
> git
> > in local under eclipse-cpp-kepler-SR2-win32-x86_64 or NetBeans.IDE.8.1,
> > while I use cygwin 2.874 for them.
> > Second, after build and compile how to get port it for Windows and
> create a
> > install file, do I use the IDEs still for this? how to modifying and
> > customizing gimp environment it's UI or create the other tools for my
> gimp?
> >
> > I appreciate for any detail and step by step help to do this purpose.
>
> Unfortunately, we have no dedicated Windows developer so it's hard to
> give you step-by-step about anything you ask and confidently tell you
> "it will work". But what that means is that we are more than welcoming
> you if you wish to contribute to GIMP! Windows developers are really
> needed since most of us are daily Linux users. The result of this is
> that GIMP has much more issues (stability, bugs, UI weirdness…) under
> Windows than under Linux. Patches and bug fixes are very welcome! :-)
>
> Alexandre gave you some links which are where you should start, though
> once again, the sections to build under Windows may be outdated.  But
> that's a good start point. If you follow these steps and find that
> some points are not right, do not hesitate to tell us so that we can
> edit the wiki (or probably better, we could give you a wiki account).
> Actually reading your email, it sounds like you may already have built
> GIMP successfully. So you may already have some remarks about what we
> have on the wiki?
>
> Also I'm not sure I understand all your questions about customizing
> GIMP environment or "other tools" for GIMP. But once again, if it is
> about Windows development, not sure I could answer, even if I
> understood the questions.
> Anyway feel free to ask more detailed questions, though you likely
> know more than us about anything which is Windows-specific (and that's
> good, we would welcome your knowledge there!).
>
> Jehan
>
> > Thanks in advanced.
> >
> > --
> > ___
> > Hashem Zavvari, BSc SWE.
> > Present, MSc SWE student at Research & Science branch of IAU.
> > Islamic Republic of Iran, Mashhad.
> > ___
> > 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
>
>
>
> --
> ZeMarmot open animation film
> http://film.zemarmot.net
> Patreon: https://patreon.com/zemarmot
> Tipeee: https://www.tipeee.com/zemarmot
> ___
> 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

Re: [Gimp-developer] webp format?

[Partha Bagchi]

Elle,

Works fine here on my Mac McGimp latest build as available on my website. I
got the sample images from https://developers.google.com/speed/webp/gallery1

Thanks,
Partha


On Sun, Aug 21, 2016 at 4:15 PM, Elle Stone 
wrote:

> On 08/21/2016 06:01 AM, Owen Cook wrote:
>
>> I noticed in the latest git a lot of stuff which suggests that gimp
>> should open webp, and export to webp.
>>
>> Is this correct, and if so how do you activate it. Currently I get
>> "Unknown file type" on opening, and webp is not in the list of export
>> formats.
>>
>>
> On a possibly related note, libwebp-0.4.2 is installed on my system
> (Gentoo Linux), but when configuring GIMP this message is printed to the
> terminal: WebP: no (WebP not found)
>
> Thinking 0.4.2 might be too old, I downloaded libwebp-0.5.1 from
> https://developers.google.com/speed/webp/docs/compiling#building, and
> installed it in /usr/local, and then re-installed babl/gegl/libmypaint/gimp
> starting from "./autogen.sh". But GIMP still isn't finding WebP. GEGL finds
> WebP, but GIMP doesn't.
>
> Is there some other library that might be required before GIMP can find
> WebP on the system? Or a magic command that says "look here"?
>
> Best,
> Elle
>
> In case it's relevant, here's the configuration summary from compiling
> libwebp-0.5.1:
>
> WebP Configuration Summary
> --
>
> Shared libraries: yes
> Static libraries: yes
> Threading support: yes
> libwebp: yes
> libwebpdecoder: no
> libwebpdemux: no
> libwebpmux: no
> libwebpextras: no
>
> Tools:
> cwebp : yes
>Input format support
>
>JPEG : yes
>PNG  : yes
>TIFF : yes
>WIC  : no
> dwebp : yes
>Output format support
>=
>PNG  : yes
>WIC  : no
> GIF support : yes
> anim_diff   : no
> gif2webp: no
> webpmux : no
> vwebp   : no
>
> ___
> 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

Re: [Gimp-developer] GIMP development- What's the point?

[Partha Bagchi]

On Fri, Sep 23, 2016 at 9:14 AM, Marius Kjeldahl 
wrote:

> ...
> I've waited years for Gimp and Inkscape to support Macs, but sadly they
> still don't. They barely "run", but they aren't usable. I wrote a blog post
> with the details:
>
> https://medium.com/@kjeldahl/gimp-and-inkscape-on-retina-
> macs-do-not-work-9601c3052e86#.i3ys9rmhn
>
> So to your question, what's the point?
>

Can you tell me what's missing in the Mac GIMP support? I've been providing
Mac (and WIndows) builds for a long time and continuing to so.
___
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 development- What's the point?

[Partha Bagchi]

I see. I haven't noticed any ill-effects of using my GIMP build on my
Macbook pros Mid 2014 (retina display). But that's me.

On Fri, Sep 23, 2016 at 9:26 AM, Maurizio Loreti 
wrote:

>
> > On 23 set 2016, at 15:24, Partha Bagchi  wrote:
> >
> > Can you tell me what's missing in the Mac GIMP support? I've been
> providing
> > Mac (and WIndows) builds for a long time and continuing to so.
>
> I think he is speaking about the lack of support for retina displays.
>
> --
> Maurizio Loreti   -   maurizio.lor...@gmail.com
>
>
>
>
>
>
>
___
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] GMIC GIT-version doesn't compile with GIMP in GIT-version

[Partha Bagchi]

Just hold off for a few and will let you know.

Thanks,
Partha


On Tue, Jan 24, 2017 at 12:31 PM, Helmut Jarausch 
wrote:

> Hi,
>
> recent changes in Gimp (GIT) make compiling GMIC (GIT) fail.
> Has anybody patches for GMIC or information on how to upgrade packages
> with use libgimp?
>
> Many thanks from some hints,
> Helmut
> ___
> 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

Re: [Gimp-developer] GMIC GIT-version doesn't compile with GIMP in GIT-version

[Partha Bagchi]

No need to file a bug report then?

On Tue, Jan 24, 2017 at 5:30 PM, Michael Natterer  wrote:

> Try again with latest git master, it should work now.
>
> Regards,
> Mitch
>
> On Tue, 2017-01-24 at 12:56 -0500, Partha Bagchi wrote:
> > Just hold off for a few and will let you know.
> >
> > Thanks,
> > Partha
> >
> >
> > On Tue, Jan 24, 2017 at 12:31 PM, Helmut Jarausch  > >
> > wrote:
> >
> > > Hi,
> > >
> > > recent changes in Gimp (GIT) make compiling GMIC (GIT) fail.
> > > Has anybody patches for GMIC or information on how to upgrade
> > > packages
> > > with use libgimp?
> > >
> > > Many thanks from some hints,
> > > Helmut
> > > ___
> > > 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-lis
> > > t
> > >
> >
> > ___
> > gimp-developer-list mailing list
> > List address:gimp-developer-list@gnome.org
> > List membership: https://mail.gnome.org/mailman/listinfo/gimp-develop
> > er-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

Re: [Gimp-developer] GMIC GIT-version doesn't compile with GIMP in GIT-version

[Partha Bagchi]

You might want to consider git pull GIMP and rebuild.

Then git pull GMIC. Next get rid of your previous build from your gmic
build folder. Now use cmake and build again.

The above error should go away.


On Wed, Jan 25, 2017 at 6:32 AM, Helmut Jarausch  wrote:

> On 01/24/2017 11:30:03 PM, Michael Natterer wrote:
>
>> Try again with latest git master, it should work now.
>>
>> Hi Michael, it looks I have no luck.
> I've build GIMP (version 2017/01/25 12:12) and then I've tried to build
> GMIC (version 2017/01/25 12:25)
>
> Here just a fine error messages (there are a lot more)
>
> gmic_gimp.cpp:393:50: error: 'GimpLayerModeEffects' has not been declared
>  void get_output_layer_props(const char *const s, GimpLayerModeEffects
> &blendmode, double &opacity,
>   ^~~~
> gmic_gimp.cpp: In function 'void get_output_layer_props(const char*, int&,
> double&, int&, int&, cimg_library::CImg&)':
> gmic_gimp.cpp:406:39: error: 'GIMP_NORMAL_MODE' was not declared in this
> scope
>_get_output_layer_blendmode("alpha",GIMP_NORMAL_MODE);
>^
___
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] Windows 10 and Bash on Ubuntu

[Partha Bagchi]

Are you planning to cross build or a native build? I am not sure what you
are asking.

On Fri, Feb 3, 2017 at 9:20 PM, Petteri Soininen  wrote:

> Hi
>
> I was more like thinking if anyone has already done that so I could get
> some pointers and try it too. If that's not the case I probably can try
> building it myself and take notes to make a 'how to' so I can give advice
> to others who like to try the same. If during that I face problems, I'll
> probably try to ask help in IRC. That Bash shell probably is quite standard
> installation in WIn10, so making build instructions for that couldn't hurt
> (if that's even possible). :)
>
> - Petteri Soininen
>
> On 2.2.2017 22:13, Michael Schumacher wrote:
>
>>
>> On 02/02/2017 08:05 PM, Petteri Soininen wrote:
>>
>> Windows 10 introduced an Ubuntu Bash shell, so I'm interested if anyone
>>> has compiled GIMP using that environment. I tried, but I'm just a newbie
>>> and got into problems where gegl didn't see babl etc. so my environment
>>> variable settings were probably either wrong or not effective or I just
>>> messed up something.
>>>
>> Hi Petteri,
>>
>> this is the point where you should explain what you did in regard to the
>> environment variable - as detailed as it would be necessary for someone
>> to reproduce what you did, without knowing what you did.
>>
>>
>>
> ___
> 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

Re: [Gimp-developer] Windows 10 and Bash on Ubuntu

[Partha Bagchi]

On Fri, Feb 3, 2017 at 9:53 PM, Petteri Soininen  wrote:

> I'd probably try cross build since after 'sudo apt-get install gimp' and
> trying to run it, it fails on 'cannot open display' so I think that
> indicates the shell cannot run it under windows and gimp needs to be built
> as a cross build. But as said, I'm just a beginner.  :)
>
> - Petteri Soininen
>
> Well, GIMP is a graphical application and X11 are not officially supported
on WSL. So, first you'll need to install X11 and then set the display
appropriately. If you are familiar with Linux this should not be a problem.
I think the command is something like export display.

If you simply plan to cross build, I am not sure what you are gaining with
WSL.

Hope that helps.
___
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] script recording

[Partha Bagchi]

On Fri, Mar 10, 2017 at 1:17 PM, Paul Thompson  wrote:

> I am working on a script recorder for GIMP. I actually have a small grant
> for this from ORI.
>
> 1) I am trying to do a basic thing - determine the files that are opened
> for image source and image export. I found the name of the source file. I
> am now working on the export file name.
> a) This is done as best I can tell with a number of save_image calls. These
> all are in different places related to image encoding (jpeg, png, etc). I
> assume this is sort of an overloaded subroutine call. I cannot find where
> the save_image call is made. Once the name of the file is determined in the
> Export dialog, how is save_image called? And specifically where is the
> export dialog?
>
> 2) Is there a meta-level description of the GIMP event loop? This would be
> a listing of the main event handler, and a listing of what is called for
> each event which is raised in the event loop.
>
> Paul A. Thompson, Ph.D., PSTAT
>
I might be missing something. But have you looked at file-save.c in
app/file/?

If you are working on a script recorder, is it possible to mimic how "undo"
is done, since undo has to remember steps you took so that it can undo?

> ___
> 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

Re: [Gimp-developer] Layer color erase

[Partha Bagchi]

On Mon, Apr 24, 2017 at 1:26 AM, Julien Hardelin  wrote:

> Please,
>
> What is the equation for the color erase layer mode?
>
> I can't finf it on the web.
>
> Julien Hardelin
>
> Look into app/operations/layer-modes. The function blendfun_color_erase
starts around Line 2359
___
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 configure warning/error

[Partha Bagchi]

I am getting the following warning:

> WARNING: Your GTK+ version is 2.24.31.
>  The recommended GTK+ version under Windows is 2.24.32 or over.
>  If you continue without updating GTK+, shortcuts won't work with
>  non-latin locales, and vector icons will be disabled.


According to http://ftp.gnome.org/pub/GNOME/sources/gtk+/2.24/, the latest
version is 2.24.31. So, does gtk+ need to be compiled from git to make this
warning go away?

Secondly, I am getting the following error:

> Error: GIMP configuration failed.
>   - Error: missing dependency glib-networking
>   *** Test for glib-networking failed. This is required.


I am perplexed to see that we need glib-networking suddenly since my git
pull from a couple of days ago? Is there a reason to requiring glib
networking support?

Thanks,
Partha
___
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] New GIMP configure warning/error

[Partha Bagchi]

On Thu, May 11, 2017 at 2:49 PM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> On Thu, May 11, 2017 at 9:34 PM, Partha Bagchi wrote:
>
> > I am perplexed to see that we need glib-networking suddenly since my git
> > pull from a couple of days ago? Is there a reason to requiring glib
> > networking support?
>
> To quote from https://git.gnome.org/browse/gimp/commit/?id=
> bb196607693b2a8fa95f033966506cbf3c377d81
>
> "Use a code test inspired by libsoup configure test. This is a hard
> dependency because HTTPS should not be considered an option anymore.
> Nowadays most websites will use HTTPS by default, HTTP gives SEO
> penalties and browsers are starting to display various security
> warnings on HTTP websites. Also the experience will be significantly
> degraded without SSL/TLS support since the help browser will fail to
> load the manual remotely, and opening various remote files on secure
> protocols will fail. Note: the test cannot be performed while
> cross-compiling. In this case, we will just display a warning for
> packagers to be at least well aware of this dependency."
>
> Alex
>
> Yes, I read the quote but am still perplexed. the only (?) place we need
http/https support is to load images from an URI? Is it not sufficient to
make that optional instead of introducing one more dependency?
___
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] New GIMP configure warning/error

[Partha Bagchi]

On Thu, May 11, 2017 at 3:03 PM, Jehan Pagès 
wrote:

> Hi,
>
> On Thu, May 11, 2017 at 8:53 PM, Partha Bagchi  wrote:
> > On Thu, May 11, 2017 at 2:49 PM, Alexandre Prokoudine <
> > alexandre.prokoud...@gmail.com> wrote:
> >
> >> On Thu, May 11, 2017 at 9:34 PM, Partha Bagchi wrote:
> >>
> >> > I am perplexed to see that we need glib-networking suddenly since my
> git
> >> > pull from a couple of days ago? Is there a reason to requiring glib
> >> > networking support?
> >>
> >> To quote from https://git.gnome.org/browse/gimp/commit/?id=
> >> bb196607693b2a8fa95f033966506cbf3c377d81
> >>
> >> "Use a code test inspired by libsoup configure test. This is a hard
> >> dependency because HTTPS should not be considered an option anymore.
> >> Nowadays most websites will use HTTPS by default, HTTP gives SEO
> >> penalties and browsers are starting to display various security
> >> warnings on HTTP websites. Also the experience will be significantly
> >> degraded without SSL/TLS support since the help browser will fail to
> >> load the manual remotely, and opening various remote files on secure
> >> protocols will fail. Note: the test cannot be performed while
> >> cross-compiling. In this case, we will just display a warning for
> >> packagers to be at least well aware of this dependency."
> >>
> >> Alex
> >>
> >> Yes, I read the quote but am still perplexed. the only (?) place we need
> > http/https support is to load images from an URI? Is it not sufficient to
> > make that optional instead of introducing one more dependency?
>
> No, there are at least 2 features affected: open remote files indeed
> and the help browser (help will fail showing with an error since our
> websites are now https only). This last one was getting quite a lot of
> report on the tracker and was very bad experience.
> Anyway nowadays https is the standard for web access. Not supporting
> this is not acceptable IMO.
>
> Jehan
>

Hi,

You realize that for platforms other than Linux, that if you wish to
install glib-networking, you have to install gnutls which requires that you
install nettle which in turn requires that you install gmp? All this
because you want remote help files and remote images be accessed from GIMP?
Does this seem reasonable to you?

Thanks,
Partha
___
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] New GIMP configure warning/error

[Partha Bagchi]

On Sat, May 13, 2017 at 8:52 AM, Jehan Pagès 
wrote:

> Hi,
>
> On Sat, May 13, 2017 at 6:25 AM, Partha Bagchi  wrote:
> >
> >
>
> >> No, there are at least 2 features affected: open remote files indeed
> >> and the help browser (help will fail showing with an error since our
> >> websites are now https only). This last one was getting quite a lot of
> >> report on the tracker and was very bad experience.
> >> Anyway nowadays https is the standard for web access. Not supporting
> >> this is not acceptable IMO.
> >>
> >> Jehan
> >
> >
> > Hi,
> >
> > You realize that for platforms other than Linux, that if you wish to
> install
> > glib-networking, you have to install
>
> Yes I realize that dependencies have often dependencies themselves.
> Unless there is something which proves to be impossible to compile on
> other platforms, I don't see the problem.
>
> > gnutls which requires that you install
> > nettle which in turn requires that you install gmp?
>
> gnutls is a SSL/TLS lib (the feature we need). And from my searches,
> nettle is apparently a cryptographic library and gmp would be an
> arithmetic library. This does make total sense for a SSL/TLS lib
> (which is a cryptographic protocol, and cryptography usually needs a
> lot of arithmetic).
> I don't see your point. That doesn't seem at all far fetched
> dependencies for the feature we need, quite the opposite.
>
> > All this because you
> > want remote help files and remote images be accessed from GIMP? Does this
> > seem reasonable to you?
>
> It does seem absolutely reasonable, yes. I would even say that in
> 2017, not having support for TLS/SSL when we have web access
> requirement would be the thing which is absolutely non-reasonable.
>
For an image editor, I think this is unreasonable. I don't understand why
we are considering GIMP to be a network aware product due to 2 possible
usage when the rest of GIMP does not depend on it. Is it not possible to
ship the help files as PDFs while disabling URI if TLS/SSL is not installed
with the package?

>
> I am rerunning a crossbuild again to check that everything is all
> right, just to make sure. What I can say is that there exists
> pre-built packages for glib-networking (and all the dependencies) so I
> could install it and all its dependencies in about 10 seconds inside
> my crossbuild environment (using my tool called crossroad, with a
> single command: crossroad install glib-networking). So first it means
> that glib-networking is buildable for Windows and in you have the
> right tools, that's really not much of a hassle. Now on Windows, I
> have no idea how hard things are. But I assume you have various helper
> tools too.
>
You mean it's easy on Windows and then on Windows you have no idea how hard
things are? Did you mean Windows it's easy and Mac you don't know? I am not
sure I understand. In any case, as Kris mentioned below, you are talking
about bloating the application on both Windows and Mac.

>
> I really don't see the big deal here. And I don't see on which ground
> it may seem acceptable to not have secure protocols support when the
> whole internet is fighting these last few years for getting rid of
> non-secure protocols (for very obvious and understandable reasons).
> This is like trying to go against the flow.
>
The "internet is fighting is an interesting point of view for an image
editor. :)

>
> Jehan
>
> > Thanks,
> > Partha
>
>
>
> --
> ZeMarmot open animation film
> http://film.zemarmot.net
> Patreon: https://patreon.com/zemarmot
> Tipeee: https://www.tipeee.com/zemarmot
>
___
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] Problem with GIMP 2.9.x build dependencies

[Partha Bagchi]

On Thu, May 18, 2017 at 8:49 AM, Carmelo DrRaw 
wrote:

> Dear GIMP experts,
>
> I am having troubles to compile the dependencies required to build the
> latest GEGL/GIMP versions from GIT.
>
> The problem I am facing is the following:
>
> * on one hand, GEGL requires GLIB > 2.44.0
>
> * on the other hand, PyGTK (needed to have python support in GIMP) wants
> pygobject-2.0, whose latest version I could find is 2.28.6
> However, this version must be compiled against a gobject-introspection
> version prior to this commit: https://mail.gnome.org/
> archives/commits-list/2011-August/msg03069.html  archives/commits-list/2011-August/msg03069.html> (Deprecate ErrorDomain),
> otherwise one gets compilation errors due to undefined enum values. So this
> brings me to 1.29.16 as the latest usable gobject-introspection version (at
> least according to release dates, see http://ftp.gnome.org/pub/
> GNOME/sources/gobject-introspection/1.29/  GNOME/sources/gobject-introspection/1.29/>).
> However, gobject-introspection-1.29.16 cannot be compiled against
> glib-2.44.0 because of g_module_* functions having been moved into a sport
> library, which gobject-introspection-1.29.16 is not linking…
>
> Am I doing something wrong? Is there a recommended set of library versions
> for compiling GIMP? Or should I patch object-introspection to add the
> missing glib library?
>
> Thanks a lot in advance!
>

Use pygtk-2.24 and you should be fine.
___
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] Problem with GIMP 2.9.x build dependencies

[Partha Bagchi]

On Thu, May 18, 2017 at 11:04 AM, Carmelo DrRaw 
wrote:

> Carol, Partha,
>
> thanks for your help. I am already using PyGTK-2.24.0, however it searches
> for pygobject-2.0.pc in the PKG_CONFIG path, and that’s what forces me to
> use a version of pygobject not newer than 2.28.6…
>
> Partha, could you tell me which combination of library versions are you
> using for your windows and OS X builds?
>
> Thanks!
>
> I am guessing you mean the combination of python/pygtk etc.?

I use python version 2.7.5, pycairo 1.10.0, pygobject 2.28.6, pygtk-2.24.
___
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] Problem with GIMP 2.9.x build dependencies

[Partha Bagchi]

On Thu, May 18, 2017 at 11:26 AM, Carmelo DrRaw 
wrote:

>
> On 18 May 2017, at 17:23, Partha Bagchi  wrote:
>
>
>
> On Thu, May 18, 2017 at 11:04 AM, Carmelo DrRaw 
> wrote:
>
>> Carol, Partha,
>>
>> thanks for your help. I am already using PyGTK-2.24.0, however it
>> searches for pygobject-2.0.pc in the PKG_CONFIG path, and that’s what
>> forces me to use a version of pygobject not newer than 2.28.6…
>>
>> Partha, could you tell me which combination of library versions are you
>> using for your windows and OS X builds?
>>
>> Thanks!
>>
>> I am guessing you mean the combination of python/pygtk etc.?
>
> I use python version 2.7.5, pycairo 1.10.0, pygobject 2.28.6, pygtk-2.24.
>
>
> Could you also tell me which version of Glib you are using? That’s what is
> causing me troubles…
>
> Thanks!
>
>
> Sorry. :(

My glib version is  2.53.1
___
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] Problem with GIMP 2.9.x build dependencies

[Partha Bagchi]

On Thu, May 18, 2017 at 12:10 PM, Carmelo DrRaw 
wrote:

> Thanks!
>
> May I also ask your gobject-introspection version?
>

I don't use it.
___
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 set the python path for GIMP plug-ins when bundling into an AppImage

[Partha Bagchi]

On Sun, May 21, 2017 at 2:44 PM, Carmelo DrRaw 
wrote:

> Hi!
>
> I am facing a problem when trying to build a GIMP AppImage that bundles
> python to allow running the python-based plug-ins.
>
> As far as I understand, GIMP takes the python executable specified in
>
> PREFIX/lib/gimp/2.0/interpreters/pygimp.interp
>
> where the executable path has to be specified with an absolute way
> (otherwise GIMP throws an error “Bad binary format string in interpreter
> file …”).
>
> However, in the AppImage case the absolute path into which the package is
> extracted is random, and is only known after the AppImage has ben actually
> started. Moreover, configuration files inside the AppImage bundle cannot be
> modified because they are read-only.
>
> Hence my question: is there a way to dynamically specify the path to the
> python interpreter? In such situations one would typically use environment
> variables, but there seems to be no way in this case…
>
>
> Thanks a lot in advance!
>
> A,

Not wanting to starting some Linux "wars" :), I think of AppImage as
Linux's acknowledgement to Mac OSX Apps.

So in that vein, include a launcher in your AppImage which mounts your
support libs is a specific location (possibly /tmp) and then point the
python interpreter to something like /tmp/python/python or something
similar.

Maybe that will work?
___
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 set the python path for GIMP plug-ins when bundling into an AppImage

[Partha Bagchi]

On Sun, May 21, 2017 at 4:18 PM, Carmelo DrRaw 
wrote:

>
>
> This is what is already done by the AppImage, except that the mound
> directory is generated with a temporary name, different each time. This is
> not something under my control, and what is causing trouble in this
> specific case...
>
Why? You can select a name that would be highly unlikely to exist in /tmp
and just reuse that?
___
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] GIMP git build error on Mac

[Partha Bagchi]

Hi All,

A new wrinkle since May 22 (my last build). Did a pull today and now I am
now getting the following error on my Mac:

GEN  xgen-bec
> /bin/sh: -c: line 1: syntax error: unexpected end of file
> make[2]: *** [gimpbaseenums.c] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2


Thanks,
Partha
___
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 git build error on Mac

[Partha Bagchi]

On Thu, Jun 1, 2017 at 9:14 PM, Ell via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> On Thu, 1 Jun 2017 19:15:03 -0400
> Partha Bagchi  wrote:
>
> > Hi All,
> >
> > A new wrinkle since May 22 (my last build). Did a pull today and now
> > I am now getting the following error on my Mac:
> >
> > GEN  xgen-bec
> > > /bin/sh: -c: line 1: syntax error: unexpected end of file
> > > make[2]: *** [gimpbaseenums.c] Error 2
> > > make[1]: *** [all-recursive] Error 1
> > > make: *** [all] Error 2
>
> Can you please report the output of "make V=1"?
>
> --
> Ell
>
 Sure thing Ell. Here it is:

make[2]: Nothing to be done for `all'.

Making all in libgimpbase

if ! cmp -s xgen-bec gimpbaseenums.c; then \

cp xgen-bec gimpbaseenums.c; \

else \

# if the file hasn't changed, only update its timestamp, so that \

# the receipe doesn't get executed again next time, but allow this \

# to fail (e.g., when using a read-only source directory). \

touch gimpbaseenums.c 2> /dev/null \

|| true; \

fi

/bin/sh: -c: line 1: syntax error: unexpected end of file

make[2]: *** [gimpbaseenums.c] Error 2

make[1]: *** [all-recursive] Error 1

make: *** [all] Error 2
___
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 git build error on Mac

[Partha Bagchi]

On Fri, Jun 2, 2017 at 6:45 AM, Ell  wrote:

> On Thu, 1 Jun 2017 22:28:07 -0400
> Partha Bagchi  wrote:
>
> > > Can you please report the output of "make V=1"?
> > >
> > > --
> > > Ell
> > >
> >  Sure thing Ell. Here it is:
>
> Thanks :)
>
Anytime! :)

>
> > make[2]: Nothing to be done for `all'.
> >
> > Making all in libgimpbase
> >
> > if ! cmp -s xgen-bec gimpbaseenums.c; then \
> >
> > cp xgen-bec gimpbaseenums.c; \
> >
> > else \
> >
> > # if the file hasn't changed, only update its timestamp, so that \
> >
> > # the receipe doesn't get executed again next time, but allow this \
> >
> > # to fail (e.g., when using a read-only source directory). \
> >
> > touch gimpbaseenums.c 2> /dev/null \
> >
> > || true; \
> >
> > fi
> >
> > /bin/sh: -c: line 1: syntax error: unexpected end of file
> >
> > make[2]: *** [gimpbaseenums.c] Error 2
> >
> > make[1]: *** [all-recursive] Error 1
> >
> > make: *** [all] Error 2
>
> Hrmph, must be the comment in the middle of the recipe.  I was actually
> surprised it worked in the first place -- must be a bash thing.
>
Yeah me too. I had no problems on Windows though and so yes, it's most
probably a bash thing.

>
> Oh well, no comments it is then :P
>
Sounds good. Let me know when you upload a fix. Thanks in advance for such
a quick fix! :)

>
> --
> Ell
>
Partha
___
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 git build error on Mac

[Partha Bagchi]

On Fri, Jun 2, 2017 at 11:20 AM, Ell  wrote:

> On Fri, 2 Jun 2017 06:55:41 -0400
> Partha Bagchi  wrote:
>
> > Sounds good. Let me know when you upload a fix. Thanks in advance for
> > such a quick fix! :)
>
> Should be fixed now, by commit 3ca48a0b30a85cfc8a63912906dd483208c342fb.
>
And it is! :) Thanks!

>
> --
> Ell
>
___
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] Trouble with building Gimp 2.9.5 against libmypaint

[Partha Bagchi]

On Sat, Jun 24, 2017 at 7:26 AM, Thorsten Stettin <
thorsten.stet...@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
> 349060a472149ddabb57c
> 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.
___
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] plugin development on a mac

[Partha Bagchi]

On Sat, Jun 24, 2017 at 4:14 PM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> 24 июня 2017 г. 11:03 PM пользователь "Jason Scherer" <
> jason.sche...@gmail.com> написал:
>
> I'm emailing the list to ask: is there anyone else building plugins on a
> mac?  Did you have issues getting set up?  Is there really no way to build
> plugins other than by building all of gimp from source?
>
>
> We briefly discussed this a while ago. Ideally, we should provide some sort
> of SDK package for macOS. But our .dmg maintainer is a busy dude with not
> much spare time.
>
> I'm sure that Partha will share some knowledge on building plug-ins for
> macOS. He's been doing that for quite a while.
>
I'll be more than happy to. Please contact me offline and we can carry on
the discussion there.
Partha

>
> Alex
> ___
> 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

Re: [Gimp-developer] Odd problem

[Partha Bagchi]

On Fri, Jul 7, 2017 at 4:55 PM, Paul Thompson  wrote:

> I am working on a script recorder for gimp. I am writing out debug
> statements to attempt to learn this and that. The problem is that debug
> statements in some files print as expected, while the same statement placed
> into other files do not print to the calling window.
>
> I am working on a windows system, and have followed the direction in
>
> https://wiki.gimp.org/wiki/Hacking:Building/Windows
>
> These are well-written directions, and enable me to compile a running copy.
> So far so good.
>
> I am working with 2 files:
>
> File 1:
> gimp/libgimp/gimpimagemetadata.c
>
> All statements put into this file, such as
>
>   g_print("Test 1 - add new print statement\n");
>
> print as directed to the window
>
> File 2:
> gimp/app/file/file-open.c
>
> Statements put into this file, including a copy of the statement above, do
> not print, regardless of what printing function I use.
>
> I know that  I am going through the relevant section since I open and write
> to a file successfully in the section that I have the g_print statement.
>
> The compile is clean, although there are libtool warnings.
>
> Is there some overlooked flag which turns printing on and off in specific
> functions that I am unaware of? This is creating difficulties in my
> progress.
>
> Paul A. Thompson
>
> Paul,

You should be able to access gimp_message and friends and use those
functions to print messages to the error console.
___
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-user] Crash after Rotate

[Partha Bagchi]

You should submit this to the developer list or file a bug report.

There was a recent bugrepot like this for the Mac. It was fixed by Ell in
the master branch.

On Mon, Sep 25, 2017 at 10:21 AM, Wiel Aerts  wrote:

>
> Hello All,
>
> I'm using GIMP 2.9.7, an unstable development release
> commit 6dfe04e9283f8435979758ac7a1519481bc73694.
>
> I'm not shure this is the right place to tell about a new problem (at
> least for me the last couple of weeks).
>
> I load some picture (jpeg, tiff doesn't matter), from the toolbox choose
> "rotate", rotate some degrees (corrective).
> If rotation is complete start "Curves". Then GIMP immediately crashes.
>
> The last sentence from stderr/stdout was:
>
> gimp_color_transform_new: using babl for 'linear TRC variant generated by
> GIMP' -> 'GIMP built-in sRGB'
> using gegl copy
> gimp: fatal error: Segmentation fault
> gimp (pid:5664): [E]xit, [H]alt, show [S]tack trace or [P]roceed:
>
> When I immediately after rotate the file save (xcf file), that after
> opening apply "Curves" it also crashes.
>
> Hope I could help (you developers are doing great job).
>
> Greetings,
> Wiel
>
> ___
> gimp-user-list mailing list
> List address:gimp-user-l...@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-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

Re: [Gimp-developer] ufraw-gimp support?

[Partha Bagchi]

Are you building the plugin yourself? RAW handling had changed in recent
master updates.

I suggest you do the following:

1. Download the nufraw source from
https://sourceforge.net/projects/nufraw/files/
2. Open nufraw_main-gimp.c and add this line around Line 84 (in the
HAVE_GIMP_2_9 section)
gimp_register_file_handler_raw ("file_nufraw_load");
3. Compile nufraw against GIMP 2.9 and install.

Then you should be good to go. Now you can select nufraw in the preferences.



On Mon, Sep 25, 2017 at 12:07 PM, richard brown 
wrote:

> Hello,
>
>
> The most recent builds of gimp don't seem able to run the ufraw-gimp
> plugin.  This is a shame, as ufraw supports Sigma X3F files pretty well.
> The message is:
>
>
> There is no RAW loader installed to open 'Raw Sigma X3F' files
>
> GIMP currently supports these RAW loaders:
> -darktable, at least 1.7
> -RawTherapee, at least 5.2
>
>
> Have I done something silly, or have I missed a memo?
>
>
>
> R.
>
> ___
> 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] GIMP-get Compile Failure (Windows)

[Partha Bagchi]

Ell,

Issues with process_system_time (addition from yesterday?):

  CC   gimpdashboard.o
> gimpdashboard.c: In function 'gimp_dashboard_sample_cpu_usage':
> gimpdashboard.c:1559:27: error: 'process_system_time' undeclared (first
> use in this function); did you mean 'process_user_time'?
>   &process_system_time,
>^~~
>process_user_time
> gimpdashboard.c:1559:27: note: each undeclared identifier is reported only
> once for each function it appears in
> Makefile:1381: recipe for target `gimpdashboard.o' failed
> make[4]: *** [gimpdashboard.o] Error 1


I think you meant to say "process_kernel_time".

Window 10 64bit etc.

Thanks,
Partha
___
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-get Compile Failure (Windows)

[Partha Bagchi]

On Sat, Jan 20, 2018 at 6:11 PM, Ell via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> On Sat, 20 Jan 2018 16:06:46 -0500
> Partha Bagchi  wrote:
>
> > Ell,
> >
> > Issues with process_system_time (addition from yesterday?):
> >
> >   CC   gimpdashboard.o
> > > gimpdashboard.c: In function 'gimp_dashboard_sample_cpu_usage':
> > > gimpdashboard.c:1559:27: error: 'process_system_time' undeclared
> > > (first use in this function); did you mean 'process_user_time'?
> > >   &process_system_time,
> > >^~~
> > >process_user_time
> > > gimpdashboard.c:1559:27: note: each undeclared identifier is
> > > reported only once for each function it appears in
> > > Makefile:1381: recipe for target `gimpdashboard.o' failed
> > > make[4]: *** [gimpdashboard.o] Error 1
> >
> >
> > I think you meant to say "process_kernel_time".
>
> Indeed.  This is what happens when you push untested code :)
>
> Fixed in 4d3720baad3792a418f2d002b66440c1bda29cbb, thanks!
>
> --
> Ell
>

No problem. I tested it for you.
___
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] Gimp-git pull today fails to build - Mac

[Partha Bagchi]

Mitch,

I get the following error while building:

Making all in tools
>   CC   ../app/widgets/gimpdebug_2_0-gimpcriticaldialog.o
> In file included from ../app/widgets/gimpcriticaldialog.c:35:
> In file included from
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h:12:
> In file included from
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:8:
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:503:1:
> error:
>   expected identifier or '('
> @class NSString, Protocol;
> ^
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:505:9:
> error:
>   unknown type name 'NSString'; did you mean 'GString'?
> typedef NSString * NSExceptionName NS_EXTENSIBLE_STRING_ENUM;


Thanks,
Partha
___
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-git pull today fails to build - Mac

[Partha Bagchi]

On Fri, Feb 2, 2018 at 5:36 AM, Michael Natterer  wrote:

> Hi Partha,
>
> you might need the right CPPFLAGS and LDFLAGS in tools/Makefile.am,
> it doesn't look like they are there.
>
> Can you try that so it builds and then send a patch please?
>
> Thanks, Mitch
> ...
>

Hi Mitch,

I think the LDFLAGS is fine. However, we need to patch 2 files I believe:
tools/Makefile.am and app/widgets/Makefile.am

I've created a patch (attached), though I'm not sure if it's in the right
format? :(

Where should I upload it?

Thanks,
Partha
___
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] GEGL errors during 'make' process

[Partha Bagchi]

Americo,

I don't know about your system, but you need to make sure that you have
gexiv2 and exiv2 (including dev files) installed in your system.

Partha

On Fri, Feb 2, 2018 at 9:13 PM, Americo Gobbo  wrote:

> Hi All,
> I have upgrade my system to ubuntu gnome 16.04.3 and I have tried again
> compile GEGL.
> The 'autogen.sh' is finished OK, without problems.
> The 'make' process have these errors messages:
>
> gcc: error: /usr/local/lib/libexiv2.so: No such file or directory
> Makefile:571: recipe for target 'gegl' failed
> make[2]: *** [gegl] Error 1
> make[2]: Leaving directory '/home/jag/devel/gimp-default-master/gegl/bin'
> Makefile:634: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/jag/devel/gimp-default-master/gegl'
> Makefile:541: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Someone can give some suggestion?
>
>
>
> Thanks
> americo
> ___
> gimp-developer-list mailing list
> List membership:https://mail.gnome.org/mailman/listinfo/gimp-deve
> loper-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

Re: [Gimp-developer] GEGL errors during 'make' process

[Partha Bagchi]

I see. So what does

pkg-config --libs exiv2

or

pkg-config --libs gexiv2


say?


On Fri, Feb 2, 2018 at 10:11 PM, Americo Gobbo 
wrote:

> Hi Partha,
> thanks!
> So, in my system gexiv2 and exiv2 are installed.
>
> $ sudo apt-get install libexiv2-dev libgexiv2-dev
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> libgexiv2-dev is already the newest version (0.10.3-2).
> libexiv2-dev is already the newest version (0.25-2.1ubuntu16.04.1).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> It seems that doesn't find in the folder that the autogen.sh is indicating?
>
> libtool:   error: cannot find the library '/usr/local/lib/libexiv2.la' or
> unhandled argument '/usr/local/lib/libexiv2.la'
> Makefile:571: recipe for target 'gegl' failed
> make[2]: *** [gegl] Error 1
> make[2]: Leaving directory '/home/jag/devel/gimp-default-master/gegl/bin'
> Makefile:634: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/jag/devel/gimp-default-master/gegl'
> Makefile:541: recipe for target 'all' failed
> make: *** [all] Error 2
>
> On 03/02/2018 00:32, Partha Bagchi wrote:
>
>> Americo,
>>
>> I don't know about your system, but you need to make sure that you have
>> gexiv2 and exiv2 (including dev files) installed in your system.
>>
>> Partha
>>
>
>
___
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] GEGL errors during 'make' process

[Partha Bagchi]

Hi Americo,

What does
find / -name "libgexiv*.so"
say?

Since I don't know how your ld.conf is setup, I am trying to guess where
your shared objects are. Once you find them, instead of relying on the
system, you can pass them directly to GIMP/GEGL while making using
LDFLAGS="-L/usr/lib/lib64" etc.


On Fri, Feb 2, 2018 at 10:31 PM, Americo Gobbo 
wrote:

> Hi Partha,
>
> ~$ pkg-config --libs exiv2
> -lexiv2
> ~$ pkg-config --libs gexiv2
> -lgexiv2 -lgobject-2.0 -lglib-2.0
>
>
> On 03/02/2018 01:27, Partha Bagchi wrote:
>
>> I see. So what does
>>
>> pkg-config --libs exiv2
>>
>> or
>>
>> pkg-config --libs gexiv2
>>
>>
>> say?
>>
>
>
>
___
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] GEGL errors during 'make' process

[Partha Bagchi]

Americo,

Just make a symlink to get past the error. Something like:

ln -s /usr/lib/x86_64-linux-gnu/libgexiv2.so /usr/local/lib/libgexiv2.so

etc.

Though, linux systems use the silly "la" files, and so this may not work.
Better to check and see if it does work. Otherwise, yes, modify your
LDFLAGS.


On Fri, Feb 2, 2018 at 10:59 PM, Americo Gobbo 
wrote:

> Hi Partha,
> in my system these libraries are in:
>
> /usr/lib/x86_64-linux-gnu/libgexiv2.a
> /usr/lib/x86_64-linux-gnu/libgexiv2.so
>
> instead that in '/usr/local/lib/libexiv2.la'
>
> On 03/02/2018 01:46, Partha Bagchi wrote:
>
>> Hi Americo,
>>
>> What does
>> find / -name "libgexiv*.so"
>> say?
>>
>> Since I don't know how your ld.conf is setup, I am trying to guess where
>> your shared objects are. Once you find them, instead of relying on the
>> system, you can pass them directly to GIMP/GEGL while making using
>> LDFLAGS="-L/usr/lib/lib64" etc.
>>
> Perhaps I need modify my setup environment?
>
> my setup script is:
>
> less ../setup-master.sh
> PREFIX=/opt/gimp-default-master
> 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 GIO_EXTRA_MODULES=/usr/lib/x86_64-linux-gnu/gio/modules
> export SRC_DIR=$HOME/devel/gimp-default-master/gimp-2.9/build
> export CFLAGS='-std=gnu99 -fPIC'
> export LESS="-F -X -R"
>
>
___
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] GEGL errors during 'make' process

[Partha Bagchi]

On Sun, Feb 4, 2018 at 8:17 AM, Americo Gobbo  wrote:

> Hi Jehan,
>
> On 03/02/2018 22:47, Jehan Pagès wrote:
>
>> Well there is nothing in the command line itself which relates to
>> libexiv2. It looks like there is something wrong in the libtool script
>> wrapper generated by the build system. Delete the file "libtool" which
>> you will find in the root of the git repository. Then run the
>> configure script again (this will create again the libtool wrapper),
>> then make and let's see what happens.
>>
> Is the same behavior... very strange.
>
> libtool:   error: cannot find the library '/usr/local/lib/libexiv2.la' or
> unhandled argument '/usr/local/lib/libexiv2.la'
> Makefile:571: recipe for target 'gegl' failed
> make[2]: *** [gegl] Error 1
> make[2]: Leaving directory '/home/jag/devel/gimp-default-master-/gegl/bin'
> Makefile:634: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/jag/devel/gimp-default-master-/gegl'
> Makefile:541: recipe for target 'all' failed
> make: *** [all] Error 2
>
> ---
>
> This is my 'autogen.sh' output:
>
> config.status: creating po/Makefile
>
> Building GEGL with prefix=/opt/gimp-default-master
>
> Optional features:
>   GEGL docs:   yes
>   Build workshop:  no
>   Build website:   yes
>   SIMD:sse:yes mmx:yes
>   Vala support:yes
>
> Optional dependencies:
>   asciidoc:yes
>   enscript:no  (enscript not found)
>   mrg: no  (mrg not found)
>   Ruby:yes
>   Lua: yes
>   Cairo:   yes
>   Pango:   no  (usable pango not found)
>   pangocairo:  no  (usable pangocairo not found)
>   GDKPixbuf:   no  (gdk-pixbuf not found)
>   JPEG:yes
>   PNG: yes
>   OpenEXR: yes
>   rsvg:yes
>   SDL: yes
>   libraw:  no  (libraw library not found)
>   Jasper:  yes
>   graphviz:no  (graphviz not found)
>   avformat:no  (sufficiently new libavformat / libavcodec or
> libswcale not found)
>   V4L: no   (v4l library not found)
>   V4L2:no  (usable libv4l2 not found)
>   spiro:   yes
>   EXIV:yes
>   gexiv2:  yes
>   umfpack: yes
>   TIFF yes
>   webp:no  (webp library not found)
>   poly2tri-c:  yes (internal)
>
> We have optional dependencies not resolved... it seems that they are
> 'optional', correct!
> ciao e thanks
> americo
>
> Americo,

You're going to have serious issues since pango, gdk-pixbuf are not found
on your system. This is really strange.

Partha
___
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 get color tag of layer in python plugin script?

[Partha Bagchi]

According to ./libgimp/gimpitem_pdb.c:879, gimp_item_get_color_tag gets the
color tag of the specified item.

Does that help?

On Wed, Feb 21, 2018 at 9:38 PM, John Tapsell  wrote:

> Here's a screenshot :
>
> https://goo.gl/images/FE4f5M
>
> On 22 Feb 2018 11:32 am, "Carol Spears"  wrote:
>
> >
> >
> > On Wed, Feb 21, 2018 at 9:16 PM, John Tapsell 
> wrote:
> >
> >> Hi,
> >>
> >>   How can I get the color tag of a layer in a python plugin script
> please?
> >>
> >>
> > Not sure what you mean by "color tag" but the color picker can be invoked
> > with:
> > color = pdb.gimp_image_pick_color(image, drawable, x, y, sample_merged,
> > sample_average, average_radius)
> >
> > carol
> >
> ___
> 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

Re: [Gimp-developer] GEGL make error - Fedora 27

[Partha Bagchi]

On Thu, Mar 8, 2018 at 9:43 AM, Americo Gobbo  wrote:

> Hi All,
> I am trying create the environment on Fedora 27 to GIMP devel... But, I
> have found problems on 'make' process:
>
> Making all in gcut
> make[2]: Entering directory '/home/jag/devel/gimp-git-master/gegl/gcut'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory '/home/jag/devel/gimp-git-master/gegl/gcut'
> Making all in tools
> make[2]: Entering directory '/home/jag/devel/gimp-git-master/gegl/tools'
>   CCLD introspect
>   CCLD operation_reference
>   CCLD detect_opencl
>   CCLD gegl-tester
>   CXX  exp_combine-exp_combine.o
>   CCLD operations_html
> ../depcomp: line 772: exec: g++: not found
> make[2]: *** [Makefile:716: exp_combine-exp_combine.o] Error 127
> make[2]: *** Waiting for unfinished jobs
> make[2]: Leaving directory '/home/jag/devel/gimp-git-master/gegl/tools'
> make[1]: *** [Makefile:633: all-recursive] Error 1
> make[1]: Leaving directory '/home/jag/devel/gimp-git-master/gegl'
> make: *** [Makefile:540: all] Error 2
> ===
> the autogen.sh is OK, all dependencies are completed (less mrg ;)
> Someone can help me?
>
> Thanks
> americo
>
Seems clear to me americo. :) It says g++ not found. What happens when you
type g++ in your GIMP shell environment?

> ___
> gimp-developer-list mailing list
> List membership:https://mail.gnome.org/mailman/listinfo/gimp-deve
> loper-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

Re: [Gimp-developer] GEGL make error - Fedora 27

[Partha Bagchi]

Elle,

g++ is the C++ compiler. In your case, it's installed on your system.

Thanks,
Partha

On Thu, Mar 8, 2018 at 10:28 AM, Elle Stone 
wrote:

> On 03/08/2018 09:58 AM, Partha Bagchi wrote:
>
>> It says g++ not found. What happens when you
>> type g++ in your GIMP shell environment?
>>
>
> Hi Partha - thanks! that was interesting. I didn't have a clue what "g++"
> might be, but here's what happened when I typed it into a terminal:
>
> $ g++
> g++: fatal error: no input files
> compilation terminated.
>
> Which seemed mysterious. So I asked Gentoo to tell me which package this
> "g++" thing was part of:
>
> $ equery belongs g++
>  * Searching for g++ ...
> sys-devel/gcc-6.4.0-r1 (/usr/x86_64-pc-linux-gnu/gcc-bin/6.4.0/g++ ->
> x86_64-pc-linux-gnu-g++)
>
> I always thought of "gcc" as the "gnu c compiler". But apparently that's
> no longer the case, instead "gcc" now stands for "gnu compiler collection",
> which includes c++:
>
> https://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/G_002b_002b-and-GCC.html
>
> Best,
> Elle
>
> ___
> 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] Windows gimp-spawn.c compile Error

[Partha Bagchi]

Hi Ell,

This one has me stumped. I get the following compile error:

gimp-spawn.c: In function 'gimp_spawn_set_cloexec':
> gimp-spawn.c:244:26: error: 'HANDLE' undeclared (first use in this
> function)
>SetHandleInformation ((HANDLE) _get_osfhandle (fd),
> HANDLE_FLAG_INHERIT, 0);
>   ^~
> gimp-spawn.c:244:26: note: each undeclared identifier is reported only
> once for each function it appears in
> gimp-spawn.c:244:34: error: expected ')' before '_get_osfhandle'
>SetHandleInformation ((HANDLE) _get_osfhandle (fd),
> HANDLE_FLAG_INHERIT, 0);


I think this means that the includes windows.h and io.h are not seen. If I
change Line 34

> #ifdef G_OS_WIN32

to

> #ifdef __WIN32__


then it works for me. What do you think is going wrong?

Thanks,
Partha
___
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] GNU++11 not allowed with Objective-C code

[Partha Bagchi]

Ell my friend, it's me again. :)

We can't use gnu++11 with objective-c code.

  CXX  gimp-parallel.o

error: invalid argument '-std=gnu++11' not allowed with 'Objective-C'

make[3]: *** [gimp-parallel.o] Error 1

So, how do we fix this? Also, shouldn't we be using c++11 or c++14 to be
generic?

Thanks,
Patha
___
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] GNU++11 not allowed with Objective-C code

[Partha Bagchi]

On Sat, Apr 7, 2018 at 1:24 PM, Ell via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> On Sat, 7 Apr 2018 12:41:10 -0400
> Partha Bagchi  wrote:
>
> > Ell my friend, it's me again. :)
> >
> > We can't use gnu++11 with objective-c code.
> >
> >   CXX  gimp-parallel.o
> >
> > error: invalid argument '-std=gnu++11' not allowed with 'Objective-C'
> >
> > make[3]: *** [gimp-parallel.o] Error 1
> >
> > So, how do we fix this? Also, shouldn't we be using c++11 or c++14 to
> > be generic?
>
> The specific compiler flag is chosen by some configure magic, so it
> should generally be ok.  A little googling shows that people are
> getting the same error with -std=c++11 too.
>
> I'm not sure why clang tries to compile this as objective-c, though.
> Can you post the output of $ make V=1 ?
>
> --
> Ell
>
> My apologies. I should have framed that as 2 different issues. One about
the compilation and the other that we should probably be using C++14 (or
11) instead of gnu++11.

In any case, the verbose mode may not be particularly helpful:

 g++ -DHAVE_CONFIG_H -I. -I../..  -DGIMPDIR=\""GIMP"\"
-DGIMP_APP_VERSION=\"2.10\" -DGIMP_USER_VERSION=\"2.10\"
-DG_LOG_DOMAIN=\"Gimp-Core\" -I../.. -I../.. -I../../app -I../../app
-I/Users/partha/local10.9/include/cairo
-I/Users/partha/local10.9/include/pixman-1
-I/Users/partha/local10.9/include
-I/Users/partha/local10.9/include/freetype2
-I/Users/partha/local10.9/include
-I/Users/partha/local10.9/include/libpng16
-I/Users/partha/local10.9/include/harfbuzz
-I/Users/partha/local10.9/include/glib-2.0
-I/Users/partha/local10.9/lib/glib-2.0/include
-I/Users/partha/local10.9/include
-I/Users/partha/local10.9/include/freetype2
-I/Users/partha/local10.9/include/harfbuzz
-I/Users/partha/local10.9/include/glib-2.0
-I/Users/partha/local10.9/lib/glib-2.0/include
-I/Users/partha/local10.9/include/libpng16
-I/Users/partha/local10.9/include -D_REENTRANT
-I/Users/partha/local10.9/include/json-glib-1.0
-I/Users/partha/local10.9/include/gio-unix-2.0/
-I/Users/partha/local10.9/include/glib-2.0
-I/Users/partha/local10.9/lib/glib-2.0/include
-I/Users/partha/local10.9/mcgimp-std/Contents/Resources/include/gegl-0.3
-I/Users/partha/local10.9/mcgimp-std/Contents/Resources/include/babl-0.1
-D_REENTRANT -I/Users/partha/local10.9/include/gdk-pixbuf-2.0
-I/Users/partha/local10.9/include/libpng16
-I/Users/partha/local10.9/include
-I/Users/partha/local10.9/include/glib-2.0
-I/Users/partha/local10.9/lib/glib-2.0/include
-I/Users/partha/local10.9/include/libmypaint
-I/Users/partha/local10.9/include/json-c
-I/Users/partha/local10.9/include/glib-2.0
-I/Users/partha/local10.9/lib/glib-2.0/include
-I/Users/partha/local10.9/include
-I/Users/partha/local10.9/include/glib-2.0
-I/Users/partha/local10.9/lib/glib-2.0/include
-I/Users/partha/local10.9/mcgimp-std/Contents/Resources/include
"-xobjective-c" -I/Users/partha/local10.9/include -DGIMP_DISABLE_DEPRECATED
-DBABL_DISABLE_DEPRECATED -DGSEAL_ENABLE -DGDK_DISABLE_DEPRECATED
-DGTK_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE
-std=c++14 -O3 -ffast-math -ftree-vectorize -mmacosx-version-min=10.9 -MT
gimp-parallel.o -MD -MP -MF .deps/gimp-parallel.Tpo -c -o gimp-parallel.o
gimp-parallel.cc
error: invalid argument '-std=c++14' not allowed with 'Objective-C'
make: *** [gimp-parallel.o] Error 1

In there you can see "-xobjective-c" is being used to compile
gimp-parallel.cc. Also, you're seeing -std=c++14 because I have CXXFLAGS
defined that way.

Thanks,
Partha
___
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] GNU++11 not allowed with Objective-C code

[Partha Bagchi]

On Sat, Apr 7, 2018 at 3:43 PM, Partha Bagchi  wrote:

>
>
> On Sat, Apr 7, 2018 at 1:24 PM, Ell via gimp-developer-list <
> gimp-developer-list@gnome.org> wrote:
>
>> On Sat, 7 Apr 2018 12:41:10 -0400
>> Partha Bagchi  wrote:
>>
>> > Ell my friend, it's me again. :)
>> >
>> > We can't use gnu++11 with objective-c code.
>> >
>> >   CXX  gimp-parallel.o
>> >
>> > error: invalid argument '-std=gnu++11' not allowed with 'Objective-C'
>> >
>> > make[3]: *** [gimp-parallel.o] Error 1
>> >
>> > So, how do we fix this? Also, shouldn't we be using c++11 or c++14 to
>> > be generic?
>>
>> The specific compiler flag is chosen by some configure magic, so it
>> should generally be ok.  A little googling shows that people are
>> getting the same error with -std=c++11 too.
>>
>> I'm not sure why clang tries to compile this as objective-c, though.
>> Can you post the output of $ make V=1 ?
>>
>> --
>> Ell
>>
>> My apologies. I should have framed that as 2 different issues. One about
> the compilation and the other that we should probably be using C++14 (or
> 11) instead of gnu++11.
>
> In any case, the verbose mode may not be particularly helpful:
>
>  g++ -DHAVE_CONFIG_H -I. -I../..  -DGIMPDIR=\""GIMP"\"
> -DGIMP_APP_VERSION=\"2.10\" -DGIMP_USER_VERSION=\"2.10\"
> -DG_LOG_DOMAIN=\"Gimp-Core\" -I../.. -I../.. -I../../app -I../../app
> -I/Users/partha/local10.9/include/cairo 
> -I/Users/partha/local10.9/include/pixman-1
> -I/Users/partha/local10.9/include -I/Users/partha/local10.9/include/freetype2
> -I/Users/partha/local10.9/include -I/Users/partha/local10.9/include/libpng16
> -I/Users/partha/local10.9/include/harfbuzz 
> -I/Users/partha/local10.9/include/glib-2.0
> -I/Users/partha/local10.9/lib/glib-2.0/include 
> -I/Users/partha/local10.9/include
> -I/Users/partha/local10.9/include/freetype2 
> -I/Users/partha/local10.9/include/harfbuzz
> -I/Users/partha/local10.9/include/glib-2.0 
> -I/Users/partha/local10.9/lib/glib-2.0/include
> -I/Users/partha/local10.9/include/libpng16 -I/Users/partha/local10.9/include
> -D_REENTRANT -I/Users/partha/local10.9/include/json-glib-1.0
> -I/Users/partha/local10.9/include/gio-unix-2.0/ 
> -I/Users/partha/local10.9/include/glib-2.0
> -I/Users/partha/local10.9/lib/glib-2.0/include -I/Users/partha/local10.9/
> mcgimp-std/Contents/Resources/include/gegl-0.3 -I/Users/partha/local10.9/
> mcgimp-std/Contents/Resources/include/babl-0.1 -D_REENTRANT
> -I/Users/partha/local10.9/include/gdk-pixbuf-2.0
> -I/Users/partha/local10.9/include/libpng16 -I/Users/partha/local10.9/include
> -I/Users/partha/local10.9/include/glib-2.0 
> -I/Users/partha/local10.9/lib/glib-2.0/include
> -I/Users/partha/local10.9/include/libmypaint 
> -I/Users/partha/local10.9/include/json-c
> -I/Users/partha/local10.9/include/glib-2.0 
> -I/Users/partha/local10.9/lib/glib-2.0/include
> -I/Users/partha/local10.9/include -I/Users/partha/local10.9/include/glib-2.0
> -I/Users/partha/local10.9/lib/glib-2.0/include -I/Users/partha/local10.9/
> mcgimp-std/Contents/Resources/include "-xobjective-c"
> -I/Users/partha/local10.9/include -DGIMP_DISABLE_DEPRECATED
> -DBABL_DISABLE_DEPRECATED -DGSEAL_ENABLE -DGDK_DISABLE_DEPRECATED
> -DGTK_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE
> -std=c++14 -O3 -ffast-math -ftree-vectorize -mmacosx-version-min=10.9 -MT
> gimp-parallel.o -MD -MP -MF .deps/gimp-parallel.Tpo -c -o gimp-parallel.o
> gimp-parallel.cc
> error: invalid argument '-std=c++14' not allowed with 'Objective-C'
> make: *** [gimp-parallel.o] Error 1
>
> In there you can see "-xobjective-c" is being used to compile
> gimp-parallel.cc. Also, you're seeing -std=c++14 because I have CXXFLAGS
> defined that way.
>
> Thanks,
> Partha
>
> As a further test, I tried this:

 c++ -std=c++14 -O3 -ffast-math -ftree-vectorize -mmacosx-version-min=10.9
-c gimp-parallel.cc -I. -I../.. `pkg-config --cflags glib-2.0` `pkg-config
--cflags gegl-0.3` -I..

It compiles fine. Hope that's helpful.
___
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] GNU++11 not allowed with Objective-C code

[Partha Bagchi]

On Sat, Apr 7, 2018 at 5:03 PM, Ell  wrote:

> On Sat, 7 Apr 2018 15:43:30 -0400
> Partha Bagchi  wrote:
>
> > My apologies. I should have framed that as 2 different issues. One
> > about
> > the compilation and the other that we should probably be using C++14
> > (or 11) instead of gnu++11.
>
> The exact flag we use is not hard coded, it's determined by
> AX_CXX_COMPILE_STDCXX() during configure.  We *could* ask it for a
> strictly standard-compliant mode, but we're not that concerned about
> it.  We might want to use some GCC extension, based on some other
> configure test, or whatnot.
>
> >
> > In any case, the verbose mode may not be particularly helpful:
> >
> > [...]
> >
> > In there you can see "-xobjective-c" is being used to compile
> > gimp-parallel.cc. Also, you're seeing -std=c++14 because I have
> > CXXFLAGS defined that way.
>
> Thanks.  So, we've been passing "-xobjective-c" unconditionally to all
> compiled files on Mac.  Commit 06950be7f0 should fix that, only passing
> it when compiling C files.
>
> --
> Ell
>

I was about to post that!!

Anyway, I did a git pull and something went haywire. I don't know what! I
even did make distclean. I am getting realms of text starting with:

  Making all in tools
>  cd .. && /bin/sh
> /Users/partha/projects/src/gimp/gitsource/std/gimp/missing automake-1.15
> --gnu tools/Makefile
>  cd .. && /bin/sh ./config.status tools/Makefile depfiles
> config.status: creating tools/Makefile
> config.status: executing depfiles commands
>   CCLD gimptool-2.0
> gimptool.o:1:1: error: source file is not valid UTF-8
>
> ...
> ^
> gimptool.o:1:2: error: source file is not valid UTF-8
>
> ...
> ^
> gimptool.o:1:3: error: source file is not valid UTF-8
>
> ...
> ^
> gimptool.o:1:4: error: source file is not valid UTF-8
>
> ...
> ^
> gimptool.o:1:5: error: expected identifier or '('
>
> ...
> ^
> gimptool.o:1:6: warning: null character ignored [-Wnull-character]
>
> ...
> ^
> gimptool.o:1:7: warning: null character ignored [-Wnull-character]
>
> ...
>

???
___
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] GNU++11 not allowed with Objective-C code

[Partha Bagchi]

On Sat, Apr 7, 2018 at 5:17 PM, Partha Bagchi  wrote:

>
>
> On Sat, Apr 7, 2018 at 5:03 PM, Ell  wrote:
>
>> On Sat, 7 Apr 2018 15:43:30 -0400
>> Partha Bagchi  wrote:
>>
>> > My apologies. I should have framed that as 2 different issues. One
>> > about
>> > the compilation and the other that we should probably be using C++14
>> > (or 11) instead of gnu++11.
>>
>> The exact flag we use is not hard coded, it's determined by
>> AX_CXX_COMPILE_STDCXX() during configure.  We *could* ask it for a
>> strictly standard-compliant mode, but we're not that concerned about
>> it.  We might want to use some GCC extension, based on some other
>> configure test, or whatnot.
>>
>> >
>> > In any case, the verbose mode may not be particularly helpful:
>> >
>> > [...]
>> >
>> > In there you can see "-xobjective-c" is being used to compile
>> > gimp-parallel.cc. Also, you're seeing -std=c++14 because I have
>> > CXXFLAGS defined that way.
>>
>> Thanks.  So, we've been passing "-xobjective-c" unconditionally to all
>> compiled files on Mac.  Commit 06950be7f0 should fix that, only passing
>> it when compiling C files.
>>
>> --
>> Ell
>>
>
> I was about to post that!!
>
> Anyway, I did a git pull and something went haywire. I don't know what! I
> even did make distclean. I am getting realms of text starting with:
>
>   Making all in tools
>>  cd .. && /bin/sh /Users/partha/projects/src/gimp/gitsource/std/gimp/missing
>> automake-1.15 --gnu tools/Makefile
>>  cd .. && /bin/sh ./config.status tools/Makefile depfiles
>> config.status: creating tools/Makefile
>> config.status: executing depfiles commands
>>   CCLD gimptool-2.0
>> gimptool.o:1:1: error: source file is not valid UTF-8
>> <
>> U+><
>> U+0004>...
>> ^
>> gimptool.o:1:2: error: source file is not valid UTF-8
>> <
>> U+><
>> U+0004>...
>> ^
>> gimptool.o:1:3: error: source file is not valid UTF-8
>> <
>> U+><
>> U+0004>...
>> ^
>> gimptool.o:1:4: error: source file is not valid UTF-8
>> <
>> U+><
>> U+0004>...
>> ^
>> gimptool.o:1:5: error: expected identifier or '('
>> <
>> U+><
>> U+0004>...
>> ^
>> gimptool.o:1:6: warning: null character ignored [-Wnull-character]
>> <
>> U+><
>> U+0004>...
>> ^
>> gimptool.o:1:7: warning: null character ignored [-Wnull-character]
>> <
>> U+><
>> U+0004>...
>>
>
> ???
>
>
Confirmed. It's something you did!! :) :)

Anyway, reverted back to previous head and c++14 error is back but all the
above is gone.
___
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] GNU++11 not allowed with Objective-C code

[Partha Bagchi]

On Sun, Apr 8, 2018 at 7:07 AM, Ell via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> On Sat, 7 Apr 2018 18:00:57 -0400
> Ell via gimp-developer-list  wrote:
>
> > On Sat, 7 Apr 2018 17:35:20 -0400
> > Partha Bagchi  wrote:
> >
> > > Confirmed. It's something you did!! :) :)
> > >
> > > Anyway, reverted back to previous head and c++14 error is back but
> > > all the above is gone.
> >
> > Ha, of course it is :)  The commit caused -xobjective-c to be passed
> > during linking too, and this apparently causes the object file to be
> > treated as a source file.  We'll need to untangle this mess, but not
> > today :)
>
> This should be fixed now, by commit 6ebc3f1b09.  Hopefully, for real
> this time :)
>
> --
> Ell
>
> Ha! We'll see! :)

OK, ok, it's seems fixed now. Have a great Sunday. :)
___
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] 2.10 RC2 Crash on Mac

[Partha Bagchi]

I'm getting what would be possibly a kernel panic when I launch RC2.

lldb gives me the following back trace:

(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
  * frame #0: 0x7fff5d2acb6e libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x7fff5d477080 libsystem_pthread.dylib`pthread_kill + 333
frame #2: 0x7fff5d2081ae libsystem_c.dylib`abort + 127
frame #3: 0x7fff5d306822 libsystem_malloc.dylib`free + 521
frame #4: 0x000100427bab
gimp-2.10`gimp_core_config_class_intern_init + 1099
frame #5: 0x0001019548cd libgobject-2.0.0.dylib`g_type_class_ref +
1197
frame #6: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref +
285
frame #7: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref +
285
frame #8: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref +
285
frame #9: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref +
285
frame #10: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref +
285
frame #11: 0x000101940dab
libgobject-2.0.0.dylib`g_object_new_valist + 91
frame #12: 0x000101940aba libgobject-2.0.0.dylib`g_object_new + 154
frame #13: 0x0001004307eb gimp-2.10`gimp_rc_new + 187
frame #14: 0x0001002e51ad gimp-2.10`gimp_load_config + 349
frame #15: 0x0001f31c gimp-2.10`app_run + 364
frame #16: 0x00010001210f gimp-2.10`main + 975
frame #17: 0x7fff5d15c015 libdyld.dylib`start + 1
(lldb)

Mitch, I cced you. I hope you don't mind.

Thanks,
Partha
___
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] 2.10 RC2 Crash on Mac

[Partha Bagchi]

I cleaned out my tree and started from scratch. The above issue has
disappeared.

Please ignore.

On Wed, Apr 18, 2018 at 11:16 AM, Partha Bagchi  wrote:

> I'm getting what would be possibly a kernel panic when I launch RC2.
>
> lldb gives me the following back trace:
>
> (lldb) bt
> * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
>   * frame #0: 0x7fff5d2acb6e libsystem_kernel.dylib`__pthread_kill +
> 10
> frame #1: 0x7fff5d477080 libsystem_pthread.dylib`pthread_kill +
> 333
> frame #2: 0x7fff5d2081ae libsystem_c.dylib`abort + 127
> frame #3: 0x7fff5d306822 libsystem_malloc.dylib`free + 521
> frame #4: 0x000100427bab gimp-2.10`gimp_core_config_class_intern_init
> + 1099
> frame #5: 0x0001019548cd libgobject-2.0.0.dylib`g_type_class_ref
> + 1197
> frame #6: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref
> + 285
> frame #7: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref
> + 285
> frame #8: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref
> + 285
> frame #9: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref
> + 285
> frame #10: 0x00010195453d libgobject-2.0.0.dylib`g_type_class_ref
> + 285
> frame #11: 0x000101940dab libgobject-2.0.0.dylib`g_object_new_valist
> + 91
> frame #12: 0x000101940aba libgobject-2.0.0.dylib`g_object_new +
> 154
> frame #13: 0x0001004307eb gimp-2.10`gimp_rc_new + 187
> frame #14: 0x0001002e51ad gimp-2.10`gimp_load_config + 349
> frame #15: 0x0001f31c gimp-2.10`app_run + 364
> frame #16: 0x00010001210f gimp-2.10`main + 975
> frame #17: 0x7fff5d15c015 libdyld.dylib`start + 1
> (lldb)
>
> Mitch, I cced you. I hope you don't mind.
>
> Thanks,
> Partha
>
___
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

[Partha Bagchi]

On Fri, Apr 20, 2018 at 4:25 PM, Ken Moffat via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> 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
>
Yeah. I was going to parody that. :) But it was updated. Do another pull if
you are using git.
___
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] File-Rawtherapee

[Partha Bagchi]

Platform Windows 10, 64bit

I'm stumped in terms of using RawTherapee (RT) as the default raw editor
within GIMP. The RT version in question is 5.4.

In checking the source file-rawtherapee.c, I see that the function
"file_raw_get_executable_path" will return the exe_path using the
environment variable "RAWTHERAPEE_EXECUTABLE" or as a last resort, using
Windows PATH environment variable. It does not utilize the Windows registry.

I'm not sure what the format for the environment variable is, while adding
the folder where RT is installed to the PATH variable results in a command
prompt during GIMP startup process and will not go away till you "Press any
key" and RT is not found.

Unlike darktable, there are no debugging abilities built into
file-rawtherapee.c.

I suspect it works on Linux boxes since g_spawn utility probably outputs to
the default stdout.

Thanks,
Partha
___
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] GIMP 2.10 Unable to read tile data from swap

[Partha Bagchi]

GIMP 2.10, Windows 64-bit

I seem to be getting the following errors when using some brushes:

"Unable to read tile data from swap: No such file or directory (0/xxx bytes
read) --"

twice, followed by

"Unable to read tile data from swap: No error (0/xxx bytes read) --"

etc. followed by
"Too many error messages!"
"Messages are redirected to stderr."

Any ideas on what is going wrong here for me?

Thanks,
Partha

PS: I was not getting these swap errors for sometime now and suddenly in
the final release, they are back again.
___
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 2.10 Unable to read tile data from swap

[Partha Bagchi]

On Wed, May 2, 2018 at 2:47 AM, Ell  wrote:

> On Tue, 1 May 2018 16:17:12 -0400
> Partha Bagchi  wrote:
>
> > GIMP 2.10, Windows 64-bit
> >
> > I seem to be getting the following errors when using some brushes:
> >
> > "Unable to read tile data from swap: No such file or directory (0/xxx
> > bytes read) --"
> >
> > twice, followed by
> >
> > "Unable to read tile data from swap: No error (0/xxx bytes read) --"
> >
> > etc. followed by
> > "Too many error messages!"
> > "Messages are redirected to stderr."
> >
> > Any ideas on what is going wrong here for me?
> >
> > Thanks,
> > Partha
> >
> > PS: I was not getting these swap errors for sometime now and suddenly
> > in the final release, they are back again.
>
> How long ago did it start?  Does disabling the separate paint thread
> fixes this?  It can be disabled by setting the GIMP_NO_PAINT_THREAD
> environment variable.
>
> --
> Ell
>

Thanks for responding Ell!

It started again after the final release. It was not there in RC1.  I
didn't know about the env. variable. I'll check it out and let you know.

This may be a affect of the transition from gegl 0.3 to 0.4?

In the past, it was related to complicated images with high resolution and
usually setting GEGL_CACHE_SIZE to 2048 or thereabouts fixed it. Now, it
does not.

Partha
___
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 2.10 Unable to read tile data from swap

[Partha Bagchi]

On Wed, May 2, 2018 at 6:22 AM, Partha Bagchi  wrote:

>
>
> On Wed, May 2, 2018 at 2:47 AM, Ell  wrote:
>
>> On Tue, 1 May 2018 16:17:12 -0400
>> Partha Bagchi  wrote:
>>
>> > GIMP 2.10, Windows 64-bit
>> >
>> > I seem to be getting the following errors when using some brushes:
>> >
>> > "Unable to read tile data from swap: No such file or directory (0/xxx
>> > bytes read) --"
>> >
>> > twice, followed by
>> >
>> > "Unable to read tile data from swap: No error (0/xxx bytes read) --"
>> >
>> > etc. followed by
>> > "Too many error messages!"
>> > "Messages are redirected to stderr."
>> >
>> > Any ideas on what is going wrong here for me?
>> >
>> > Thanks,
>> > Partha
>> >
>> > PS: I was not getting these swap errors for sometime now and suddenly
>> > in the final release, they are back again.
>>
>> How long ago did it start?  Does disabling the separate paint thread
>> fixes this?  It can be disabled by setting the GIMP_NO_PAINT_THREAD
>> environment variable.
>>
>> --
>> Ell
>>
>
> Thanks for responding Ell!
>
> It started again after the final release. It was not there in RC1.  I
> didn't know about the env. variable. I'll check it out and let you know.
>
> This may be a affect of the transition from gegl 0.3 to 0.4?
>
> In the past, it was related to complicated images with high resolution and
> usually setting GEGL_CACHE_SIZE to 2048 or thereabouts fixed it. Now, it
> does not.
>
> Partha
>
> Hi Ell,

I did the following. I set the following environment variables:
GEGL_SWAP=C:\Users\partha\AppData\Local\Temp\gegl
GIMP_NO_PAINT_THREAD="Y"

It didn't make any difference. Matter of fact, GEGL_SWAP was unused. So, I
removed it and reran GIMP. No change.

Thanks,
Partha
___
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 2.10 Unable to read tile data from swap

[Partha Bagchi]

On Wed, May 2, 2018 at 9:59 AM, Ell  wrote:

> On Wed, 2 May 2018 09:16:46 -0400
> Partha Bagchi  wrote:
>
> > > It started again after the final release. It was not there in RC1.
>
> So it only started at some point after RC1, but before 2.10? (days?
> weeks?)  I'm trying of think of things that changed during that time
> that might have caused this.  Did you change something on your end?
>
No, I mean that the change was related to the final release 2.10.0 and not
before. I had no reports prior to final release.

My changes are cosmetic. For example, I modify
./app/widgets/gimppanedbox.c
// #define INSTRUCTIONS_TEXT _("You can drop dockable dialogs here")
#define INSTRUCTIONS_TEXT _("")

I don't modify anything in babl or gegl.
My compiler is gcc 7.1

>
> > > This may be a affect of the transition from gegl 0.3 to 0.4?
>
> Not likely, especially if it already happened before 2.10.  The 0.4
> switch happened right before the release.
>
See above. As you say, 0.4 switch was literally before the final release.
In fact gimp.pc.in was changed after the release.

>
> > > In the past, it was related to complicated images with high
> > > resolution and usually setting GEGL_CACHE_SIZE to 2048 or
> > > thereabouts fixed it. Now, it does not.
>
> This sounds like you might have ran out of cache and swap space, in
> which case you'd start getting write errors.  These are read errors,
> which are much more surprising.
>
You are right. These are read errors.

>
> > I did the following. I set the following environment variables:
> > GEGL_SWAP=C:\Users\partha\AppData\Local\Temp\gegl
> > GIMP_NO_PAINT_THREAD="Y"
> >
> > It didn't make any difference.
>
> Ok, so it's not the separate paint thread.  That's a good thing :)
> What's the rest of your GEGL setup like?  Are you using any other
> environment variables?  What's the thread count?
>
My GEGL compilation of simply what environment variables? I only have one
GEGL variable active now: gpu usage.
My configure from the config.log is:

$ ./configure --prefix=/opt/gimp/std --build=x86_64-w64-mingw32
> CPPFLAGS=-I/opt/include -I/usr/python/include -I/opt/SuiteSparse/include
> LIBS=-L/opt/lib -L/usr/python/Lib -L/opt/SuiteSparse/lib --disable-docs
> --without-libavformat --without-sdl --enable-workshop
> build_alias=x86_64-w64-mingw32 CC=gcc CFLAGS=-O3 -ffast-math
> -ftree-vectorize CXX=g++ CXXFLAGS=-std=c++14 -DMS_WIN64 -O3 -ffast-math
> -ftree-vectorize
> PKG_CONFIG_PATH=/opt/lib/pkgconfig:/usr/python/Lib/pkgconfig:/opt/share/pkgconfig:/opt/gimp/libmypaint/lib/pkgconfig:/opt/gimp/std/lib/pkgconfig
> --no-create --no-recursion

My thread count is 8. I've tried with thread count set to 1 with the same
result.

>
> > Matter of fact, GEGL_SWAP was unused.
> > So, I removed it and reran GIMP. No change.
>
> Do you mean that GEGL wasn't using the swap?  Can you use the dashboard
> to see if anything "interesting" is going on while this happens?  Is
> the cache full?  Is the swap nearly full?  Do the reported cache/swap
> size limits make sense?
>
OK. When I start the dashboard, I have the following:
Cache:

Occupied: 0 bytes (0%)

Limit: 7.9 GiB

Swap:

Occupied: 0 bytes (0%)

Size: 0 bytes (0%)

Limit:114.7 GiB

CPU (0%)

Opened image (RGB Color 16-bit gamma integer, MelissaRGB 1 layer) 7378x4924
(D800 36MP image)
Duplicate Layer.
Dashboard:
Cache:

Occupied: 751.6 MiB (9%)
Limit: 7.9 GiB

Swap (no change)

Start painting on the layer:
Cache:

Occupied: 818.7 MiB (10%)

Limit: 7.9 GiB

Swap:

Occupied: 512.0 Kib (0%)

Size: 4.0 MiB (0%)

Limit: 114.7 GiB

CPU (0%)

But, we have:
GEGL Message

unable to read tile data from swap: No such file or directory (0/130568
bytes read) --

GEGL Message

unable to read tile data from swap: No such file or directory (0/130568
bytes read) --

GEGL Message

unable to read tile data from swap: No error (0/130568 bytes read) --

 Too many error messages etc.

>
> --
> Ell
>

Thanks,
Partha
___
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 2.10 Unable to read tile data from swap

[Partha Bagchi]

On Wed, May 2, 2018 at 2:18 PM, Øyvind Kolås  wrote:

> On Wed, May 2, 2018 at 4:36 PM, Partha Bagchi  wrote:
> > My GEGL compilation of simply what environment variables? I only have one
> > GEGL variable active now: gpu usage.
>
> GPU usage meaning OpenCL?
>
I was using the following:
  GEGL_USE_OPENCL=gpu;
Is that what you mean?


>
> GEGL has stopped enabling opencl by defult now, since GEGL-0.3.24 of
> 2017-11-24 it no longer being enabled by default since it relies on
> good results from the varying quality different opencl
> implementations,.. may also have generic race conditions resulting
> from new code not manifest during regular testing either, so trying
> without OpenCL enabled.
>
> /pippin
>
I removed the above environment variable but no change with my 36MP image.
The moment I put the brush on the screen, I get the error messages above.

Then I experimented with some more pictures and it seems to be related to
the size of the image.

I open a 1 megabyte (MB), and 4MB image and no error. Then I open a 74MB
image without error. But when I opened an 300 MB Tiff, I started getting
the error.

I repeated the experiment with GEGL_CACHE_SIZE = 2048 with the same result.

For all all images, I first fit to window > duplicate layer > paint on
duplicate layer.

Thanks,
Partha
___
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 2.10 Unable to read tile data from swap

[Partha Bagchi]

On Wed, May 2, 2018 at 3:04 PM, Partha Bagchi  wrote:

>
>
> On Wed, May 2, 2018 at 2:18 PM, Øyvind Kolås  wrote:
>
>> On Wed, May 2, 2018 at 4:36 PM, Partha Bagchi  wrote:
>> > My GEGL compilation of simply what environment variables? I only have
>> one
>> > GEGL variable active now: gpu usage.
>>
>> GPU usage meaning OpenCL?
>>
> I was using the following:
>   GEGL_USE_OPENCL=gpu;
> Is that what you mean?
>
>
>>
>> GEGL has stopped enabling opencl by defult now, since GEGL-0.3.24 of
>> 2017-11-24 it no longer being enabled by default since it relies on
>> good results from the varying quality different opencl
>> implementations,.. may also have generic race conditions resulting
>> from new code not manifest during regular testing either, so trying
>> without OpenCL enabled.
>>
>> /pippin
>>
> I removed the above environment variable but no change with my 36MP image.
> The moment I put the brush on the screen, I get the error messages above.
>
> Then I experimented with some more pictures and it seems to be related to
> the size of the image.
>
> I open a 1 megabyte (MB), and 4MB image and no error. Then I open a 74MB
> image without error. But when I opened an 300 MB Tiff, I started getting
> the error.
>
> I repeated the experiment with GEGL_CACHE_SIZE = 2048 with the same result.
>
> For all all images, I first fit to window > duplicate layer > paint on
> duplicate layer.
>
> Thanks,
> Partha
>
> One additional piece of data that may or may not be relevant. The When I
change the layer to mode something other than normal and change it back,
the painting shows up fine.

Here is the before image:
https://www.partha.com/downloads/GIMP/Screen-painting-before.jpg
and here is the after switching layer modes to something and back to
normal: https://www.partha.com/downloads/GIMP/Screen-painting-after.jpg
___
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 2.10 Unable to read tile data from swap

[Partha Bagchi]

On Wed, May 2, 2018 at 3:49 PM, Ell  wrote:

> On Wed, 2 May 2018 15:04:01 -0400
> Partha Bagchi  wrote:
>
> > On Wed, May 2, 2018 at 2:18 PM, Øyvind Kolås  wrote:
> >
> > >
> > > GEGL has stopped enabling opencl by defult now, since GEGL-0.3.24 of
> > > 2017-11-24 it no longer being enabled by default since it relies on
> > > good results from the varying quality different opencl
> > > implementations,.. may also have generic race conditions resulting
> > > from new code not manifest during regular testing either, so trying
> > > without OpenCL enabled.
> > >
> > > /pippin
> > >
> > I removed the above environment variable but no change with my 36MP
> > image. The moment I put the brush on the screen, I get the error
> > messages above.
> >
> > Then I experimented with some more pictures and it seems to be
> > related to the size of the image.
> >
> > I open a 1 megabyte (MB), and 4MB image and no error. Then I open a
> > 74MB image without error. But when I opened an 300 MB Tiff, I started
> > getting the error.
> >
> > I repeated the experiment with GEGL_CACHE_SIZE = 2048 with the same
> > result.
> >
> > For all all images, I first fit to window > duplicate layer > paint on
> > duplicate layer.
>
> My guess is that this is related to the zoom level (being <= 50%),
> rather than to the size of the image per se.  There were some changes
> to the mipmapped tiles code recently, and there was indeed a subtle bug
> there.  GEGL commit 3557811a5527bccbfef2006046a05047b6edd480 should fix
> it.
>
You may be right! I changed the zoom level to 51% and didn't see that
error. I'll have to experiment some more of course.

For GEGL, I'll git pull and rebuild to see what the effect is.

>
> Note that the actual bug was the swap being used in the first place.
> I'm still not sure why you're getting read errors, though.  Since the
> swap shouldn't be used anymore (in this particular case) after the
> above commit, the errors will probably go away, but the issue causing
> them might still be there.  I'd try to set a very low cache size, in
> order to force the swap to become very active, and see if you're
> getting any more errors.
>
I should do this after update gegl and gimp, correct?

>
> --
> Ell
>
Thanks!
Partha
___
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 2.10 Unable to read tile data from swap

[Partha Bagchi]

On Wed, May 2, 2018 at 3:58 PM, Ell  wrote:

> On Wed, 2 May 2018 15:56:12 -0400
> Partha Bagchi  wrote:
>
> > On Wed, May 2, 2018 at 3:49 PM, Ell  wrote:
> > > Note that the actual bug was the swap being used in the first place.
> > > I'm still not sure why you're getting read errors, though.  Since
> > > the swap shouldn't be used anymore (in this particular case) after
> > > the above commit, the errors will probably go away, but the issue
> > > causing them might still be there.  I'd try to set a very low cache
> > > size, in order to force the swap to become very active, and see if
> > > you're getting any more errors.
> > >
> > I should do this after update gegl and gimp, correct?
>
> Yep.
>
> --
> Ell
>
Sounds good.

I think your hypothesis that it's related to the zoom level may be correct.
I restarted GIMP with no GEGL environment variables. I opened image >
duplicated layer. I set the zoom level to 50.1% and I saw the same
artifacts. Then I increased the zoom to 50.5% and it went away.

You realize that for large images, it would be unwieldy to be painting at
that zoom level?

Thanks again to you and pippin for resolving this.

Partha

PS: Did you see the screenshots I posted?
___
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] Please help me with dependency details to build GIMP 2.10 on CentOS 7

[Partha Bagchi]

On Thu, May 17, 2018 at 3:15 AM Deft Developer  wrote:

> ...
> Here is what I have bash source before I run "autogen.sh
> --prefix=$INSTALL_PREFIX" or "configure --prefix=$INSTALL_PREFIX" for each
> dependency:
>
> source /usr/bin/scl_source enable devtoolset-7
>
>
>
> export GIMP_BLD_HOME=$HOME/projects/3rdparty/gimp_world/gimp
>
> export SRC_DIR=$GIMP_BLD_HOME/src
>
> export INSTALL_PREFIX=$HOME/opt/gimp-10
>
> export LD_LIBRARY_PATH=$INSTALL_PREFIX/lib:/usr/local/lib:$LD_LIBRARY_PATH
>
> export PKG_CONFIG_PATH=$INSTALL_PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH
>
> export PATH=$INSTALL_PREFIX/bin:$PATH
>
> export CFLAGS="-march=native -O3"
>
>
>
> All the above dirs  exist.
>
> With  gexiv2, I run "./configure" - - - "sudo make install" without error,
> but GIMP 2.10 autogen still fails with:
>
> Error: missing dependency gexiv2 >= 0.10.6 .
>
> what does pkg-config --modversion gexiv2 say?
___
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] Please help me with dependency details to build GIMP 2.10 on CentOS 7

[Partha Bagchi]

On Thu, May 17, 2018 at 12:19 PM, Deft Developer  wrote:

> Here is the output from  pkg-config, and locate
>
>
>
> > pkg-config --modversion gexiv2
>
> Package gexiv2 was not found in the pkg-config search path.
>
> Perhaps you should add the directory containing `gexiv2.pc'
>
> to the PKG_CONFIG_PATH environment variable
>
> No package 'gexiv2' found
>
>
>
> > locate gexiv2.pc
>
> /usr/exports/projects/3rdparty/gimp_world/archives/gexiv2-0.10.6/
> gexiv2.pc.in
>
> /usr/exports/projects/3rdparty/gimp_world/deps/gexiv2/gexiv2.pc
>
> /usr/exports/projects/3rdparty/gimp_world/deps/gexiv2/gexiv2.pc.in
>
> /usr/exports/projects/3rdparty/gimp_world/tree/gexiv2-0.10.6/gexiv2.pc
>
> /usr/exports/projects/3rdparty/gimp_world/tree/gexiv2-0.10.6/gexiv2.pc.in
>
> /usr/local/lib/pkgconfig/gexiv2.pc
>
>
>

I guess you can figure out the rest from here? :)
___
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] Please help me with dependency details to build GIMP 2.10 on CentOS 7

[Partha Bagchi]

On Thu, May 17, 2018 at 8:12 PM Deft Developer  wrote:

> YES! Thank you!
>
You are welcome. Feel free to reach out anytime.
___
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] GIMP git Glib Issues

[Partha Bagchi]

Platform Windows 10 64bit

I'm getting circular logic regarding glib-2.0 requirements with configure.

If I provide glib-2.0 version 2.56.1 then we are stopped by the Windows bug
that requires glib-2.0 to be 2.54.x.

If I provide glib-2.0 2.54.x then I get the error:

Error: GIMP configuration failed.

  - Error: missing dependency glib >= 2.56.0
  *** Test for GLIB failed


When I check the log, I see:

configure:22742: checking for GLIB - version >= 2.56.0
configure:22949: result: no
configure:22977: gcc -o conftest.exe -DMS_WIN64 -O3 -ffast-math
-ftree-vectorize -Wall -Wdeclaration-after-statement -Wmissing-prototypes
-Werror=missing-prototypes  -Wmissing-declarations -Winit-self
-Wpointer-arith  -Wmissing-format-attribute -Wformat-security -Wlogical-op
-Wtype-limits -fno-common -fdiagnostics-show-option -Wreturn-type
 -mms-bitfields  -I/opt/include -I/usr/python/include
-I/opt/include/glib-2.0  conftest.c -L/opt/lib -L/usr/python/Lib
-L/opt/include/lib -lglib-2.0 -lintl  >&5
configure:22977: $? = 0
configure:23004: Ek! Missing dep: glib >= 2.56.0


Really, Eeeek? :)
___
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] GIMP git gimpinputdevicestore-dx.c

[Partha Bagchi]

Hi Mitch,

You may or may not remember I sent you a patch for the above mentioned
file. :)

Anyway on Windows gdk_win32_drawable_get_handle is not exported. We have to
use gdk_win32_window_get_handle. I can send the patch again or put it the
new bug tracking system?

Thanks,
Partha
___
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] GIMP Git gimp_too_cursors_get_resource error MacOS

[Partha Bagchi]

I get the following:

Undefined symbols for architecture x86_64:
  "_gimp_tool_cursors_get_resource", referenced from:
 -u command line option
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
make[3]: *** [gimp-console-2.99] Error 1


This is due to this line in ./app/Makefile

#\
# -Wl,-u,$(SYMPREFIX)gimp_tool_cursors_get_resource


I think this should not be there. After I comment it out, it compiles
normally.

Thanks,
Partha
___
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 Git gimp_too_cursors_get_resource error MacOS

[Partha Bagchi]

On Fri, Jun 8, 2018 at 2:56 AM Michael Natterer  wrote:

> On Thu, 2018-06-07 at 11:28 -0400, Partha Bagchi wrote:
> > I get the following:
> >
> > Undefined symbols for architecture x86_64:
> >   "_gimp_tool_cursors_get_resource", referenced from:
> >  -u command line option
> > ld: symbol(s) not found for architecture x86_64
> > clang: error: linker command failed with exit code 1 (use -v to see
> > invocation)
> > make[3]: *** [gimp-console-2.99] Error 1
> >
> >
> > This is due to this line in ./app/Makefile
> >
> > #\
> > # -Wl,-u,$(SYMPREFIX)gimp_tool_cursors_get_resource
> >
> >
> > I think this should not be there. After I comment it out, it compiles
> > normally.
>
> But you probably have no cursors :)
>
How do I verify that? Wouldn't I have had this issue when I was compiling
GIMP 2.10? Little confused. :)

>
> The symbol must be there is the resource file was properly generated.
>
I assume the resource file is ./app/widgets/gimp-tool-cursors.c? This file
is identical to GIMP-2.10/cursors/gimp-tool-cursors.c. So, does that mean
it was generated properly?

I also noticed that GIMP 2.10 Makfile.am didn't include that line while
GIMP 2.99.1 does.

>
> --Mitch
>
Thanks,
Partha
___
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 Git gimp_too_cursors_get_resource error MacOS

[Partha Bagchi]

On Fri, Jun 8, 2018 at 6:42 AM Michael Natterer  wrote:

> On Fri, 2018-06-08 at 06:36 -0400, Partha Bagchi wrote:
> > On Fri, Jun 8, 2018 at 2:56 AM Michael Natterer 
> > wrote:
> >
> > > On Thu, 2018-06-07 at 11:28 -0400, Partha Bagchi wrote:
> > > > I get the following:
> > > >
> > > > Undefined symbols for architecture x86_64:
> > > >   "_gimp_tool_cursors_get_resource", referenced from:
> > > >  -u command line option
> > > > ld: symbol(s) not found for architecture x86_64
> > > > clang: error: linker command failed with exit code 1 (use -v to
> > > > see
> > > > invocation)
> > > > make[3]: *** [gimp-console-2.99] Error 1
> > > >
> > > >
> > > > This is due to this line in ./app/Makefile
> > > >
> > > > #\
> > > > # -Wl,-u,$(SYMPREFIX)gimp_tool_cursors_get_resource
> > > >
> > > >
> > > > I think this should not be there. After I comment it out, it
> > > > compiles
> > > > normally.
> > >
> > > But you probably have no cursors :)
> > >
> >
> > How do I verify that? Wouldn't I have had this issue when I was
> > compiling
> > GIMP 2.10? Little confused. :)
>
> Cursor resource genration was changed in master, we now generate
> them in the directory where they are compiled , but they have
> to be linked in by force because nothing in the source references
> the symbol.
>
> Just check if you tools have different cursors.
>
> Sorry for the late response Mitch. Due to change in the App structure, it
took me a while to create a MacOS app.

Anyway, I'm not exactly sure how to check if the tools have different
cursors.  Do you mean for instance that If I've selected the lasso tool,
then the cursor turns to a lasso? In my case it does.

However, I do have the following message:

gimp_devices_restore: set default tool on loaded GimpDeviceInfo without
> tool options: Quartz Cursor
> gimp_devices_restore: set default tool on loaded GimpDeviceInfo without
> tool options: Quartz Eraser
> gimp_devices_restore: set default tool on loaded GimpDeviceInfo without
> tool options: Quartz Pen


There there's more to this?

Thanks,
Partha
___
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 Git gimp_too_cursors_get_resource error MacOS

[Partha Bagchi]

On Wed, Jun 13, 2018 at 12:33 PM Michael Natterer  wrote:

> On Wed, 2018-06-13 at 09:42 -0400, Partha Bagchi wrote:
> > On Fri, Jun 8, 2018 at 6:42 AM Michael Natterer 
> > wrote:
> >
> > > On Fri, 2018-06-08 at 06:36 -0400, Partha Bagchi wrote:
> > > > On Fri, Jun 8, 2018 at 2:56 AM Michael Natterer 
> > > > wrote:
> > > >
> > > > > On Thu, 2018-06-07 at 11:28 -0400, Partha Bagchi wrote:
> > > > > > I get the following:
> > > > > >
> > > > > > Undefined symbols for architecture x86_64:
> > > > > >   "_gimp_tool_cursors_get_resource", referenced from:
> > > > > >  -u command line option
> > > > > > ld: symbol(s) not found for architecture x86_64
> > > > > > clang: error: linker command failed with exit code 1 (use -v
> > > > > > to
> > > > > > see
> > > > > > invocation)
> > > > > > make[3]: *** [gimp-console-2.99] Error 1
> > > > > >
> > > > > >
> > > > > > This is due to this line in ./app/Makefile
> > > > > >
> > > > > > #\
> > > > > > # -Wl,-u,$(SYMPREFIX)gimp_tool_cursors_get_resource
> > > > > >
> > > > > >
> > > > > > I think this should not be there. After I comment it out, it
> > > > > > compiles
> > > > > > normally.
> > > > >
> > > > > But you probably have no cursors :)
> > > > >
> > > >
> > > > How do I verify that? Wouldn't I have had this issue when I was
> > > > compiling
> > > > GIMP 2.10? Little confused. :)
> > >
> > > Cursor resource genration was changed in master, we now generate
> > > them in the directory where they are compiled , but they have
> > > to be linked in by force because nothing in the source references
> > > the symbol.
> > >
> > > Just check if you tools have different cursors.
> > >
> > > Sorry for the late response Mitch. Due to change in the App
> > > structure, it
> >
> > took me a while to create a MacOS app.
> >
> > Anyway, I'm not exactly sure how to check if the tools have different
> > cursors.  Do you mean for instance that If I've selected the lasso
> > tool,
> > then the cursor turns to a lasso? In my case it does.
>
> Then it's good :)
>
That's good to know from my perspective too! :)

Then we have to remove Line 134 from ./app/Makefile.am. Otherwise, GIMP
won't compile. Do you agree?


> > However, I do have the following message:
> >
> > gimp_devices_restore: set default tool on loaded GimpDeviceInfo
> > without
> > > tool options: Quartz Cursor
> > > gimp_devices_restore: set default tool on loaded GimpDeviceInfo
> > > without
> > > tool options: Quartz Eraser
> > > gimp_devices_restore: set default tool on loaded GimpDeviceInfo
> > > without
> > > tool options: Quartz Pen
> >
> >
> > There there's more to this?
>
> No this should happen only when reading devicerc that was written by
> an older version, the messages just indicate that importing the old
> format worked. Save devices once (or on each exit) and it will be
> silent.
>
Ahh, yes, OK. Since it's reading the devicerc from GIMP 2.10.2.

>
> Regards,
> Mitch
>

Thanks,
Partha

>
>
___
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 Git gimp_too_cursors_get_resource error MacOS

[Partha Bagchi]

On Wed, Jun 13, 2018 at 1:37 PM Michael Natterer  wrote:

> On Wed, 2018-06-13 at 19:33 +0200, Michael Natterer wrote:
> > On Wed, 2018-06-13 at 19:31 +0200, Michael Natterer wrote:
> > > On Wed, 2018-06-13 at 12:47 -0400, Partha Bagchi wrote:
> > > > On Wed, Jun 13, 2018 at 12:33 PM Michael Natterer  > > > >
> > > > wrote:
> > > >
> > > > > On Wed, 2018-06-13 at 09:42 -0400, Partha Bagchi wrote:
> > > > > > On Fri, Jun 8, 2018 at 6:42 AM Michael Natterer  > > > > > rg
> > > > > > >
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > On Fri, 2018-06-08 at 06:36 -0400, Partha Bagchi wrote:
> > > > > > > > On Fri, Jun 8, 2018 at 2:56 AM Michael Natterer  > > > > > > > mp
> > > > > > > > .o
> > > > > > > > rg>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Thu, 2018-06-07 at 11:28 -0400, Partha Bagchi wrote:
> > > > > > > > > > I get the following:
> > > > > > > > > >
> > > > > > > > > > Undefined symbols for architecture x86_64:
> > > > > > > > > >   "_gimp_tool_cursors_get_resource", referenced from:
> > > > > > > > > >  -u command line option
> > > > > > > > > > ld: symbol(s) not found for architecture x86_64
> > > > > > > > > > clang: error: linker command failed with exit code 1
> > > > > > > > > > (use
> > > > > > > > > > -v
> > > > > > > > > > to
> > > > > > > > > > see
> > > > > > > > > > invocation)
> > > > > > > > > > make[3]: *** [gimp-console-2.99] Error 1
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > This is due to this line in ./app/Makefile
> > > > > > > > > >
> > > > > > > > > > #\
> > > > > > > > > > # -Wl,-u,$(SYMPREFIX)gimp_tool_cursors_get_resource
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I think this should not be there. After I comment it
> > > > > > > > > > out,
> > > > > > > > > > it
> > > > > > > > > > compiles
> > > > > > > > > > normally.
> > > > > > > > >
> > > > > > > > > But you probably have no cursors :)
> > > > > > > > >
> > > > > > > >
> > > > > > > > How do I verify that? Wouldn't I have had this issue when
> > > > > > > > I
> > > > > > > > was
> > > > > > > > compiling
> > > > > > > > GIMP 2.10? Little confused. :)
> > > > > > >
> > > > > > > Cursor resource genration was changed in master, we now
> > > > > > > generate
> > > > > > > them in the directory where they are compiled , but they
> > > > > > > have
> > > > > > > to be linked in by force because nothing in the source
> > > > > > > references
> > > > > > > the symbol.
> > > > > > >
> > > > > > > Just check if you tools have different cursors.
> > > > > > >
> > > > > > > Sorry for the late response Mitch. Due to change in the App
> > > > > > > structure, it
> > > > > >
> > > > > > took me a while to create a MacOS app.
> > > > > >
> > > > > > Anyway, I'm not exactly sure how to check if the tools have
> > > > > > different
> > > > > > cursors.  Do you mean for instance that If I've selected the
> > > > > > lasso
> > > > > > tool,
> > > > > > then the cursor turns to a lasso? In my case it does.
> > > > >
> > > > > Then it's good :)
> > > > >
> > > >
> > > > That's good to know from my perspective too! :)
> > > >
> > > > Then we have to remove Line 134 from ./app/Makefile.am.
> > > > Otherwise,
> > > > GIMP
> > > > won't compile. Do you agree?
> > >
> > > If we remove that line, we don't have cursors at all, it simply
> > > won't link in the file that's not referenced from anywhere,
> > > on linux, gcc and standard ld.
> >
> > Sent too early...
> >
> > Does the linker error happend for gimp-console or gimp?
>
I think gimp-console, but I'll have to check again tonight and will let you
know.

>
> Well... git pull :)
>
Will do. :) Thanks!
___
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 Git gimp_too_cursors_get_resource error MacOS

[Partha Bagchi]

On Wed, Jun 13, 2018 at 1:54 PM Partha Bagchi  wrote:

>
>
> On Wed, Jun 13, 2018 at 1:37 PM Michael Natterer  wrote:
>
>> On Wed, 2018-06-13 at 19:33 +0200, Michael Natterer wrote:
>> > On Wed, 2018-06-13 at 19:31 +0200, Michael Natterer wrote:
>> > > On Wed, 2018-06-13 at 12:47 -0400, Partha Bagchi wrote:
>> > > > On Wed, Jun 13, 2018 at 12:33 PM Michael Natterer > > > > >
>> > > > wrote:
>> > > >
>> > > > > On Wed, 2018-06-13 at 09:42 -0400, Partha Bagchi wrote:
>> > > > > > On Fri, Jun 8, 2018 at 6:42 AM Michael Natterer > > > > > > rg
>> > > > > > >
>> > > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > On Fri, 2018-06-08 at 06:36 -0400, Partha Bagchi wrote:
>> > > > > > > > On Fri, Jun 8, 2018 at 2:56 AM Michael Natterer > > > > > > > > mp
>> > > > > > > > .o
>> > > > > > > > rg>
>> > > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > > On Thu, 2018-06-07 at 11:28 -0400, Partha Bagchi wrote:
>> > > > > > > > > > I get the following:
>> > > > > > > > > >
>> > > > > > > > > > Undefined symbols for architecture x86_64:
>> > > > > > > > > >   "_gimp_tool_cursors_get_resource", referenced from:
>> > > > > > > > > >  -u command line option
>> > > > > > > > > > ld: symbol(s) not found for architecture x86_64
>> > > > > > > > > > clang: error: linker command failed with exit code 1
>> > > > > > > > > > (use
>> > > > > > > > > > -v
>> > > > > > > > > > to
>> > > > > > > > > > see
>> > > > > > > > > > invocation)
>> > > > > > > > > > make[3]: *** [gimp-console-2.99] Error 1
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > This is due to this line in ./app/Makefile
>> > > > > > > > > >
>> > > > > > > > > > #\
>> > > > > > > > > > # -Wl,-u,$(SYMPREFIX)gimp_tool_cursors_get_resource
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > I think this should not be there. After I comment it
>> > > > > > > > > > out,
>> > > > > > > > > > it
>> > > > > > > > > > compiles
>> > > > > > > > > > normally.
>> > > > > > > > >
>> > > > > > > > > But you probably have no cursors :)
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > > How do I verify that? Wouldn't I have had this issue when
>> > > > > > > > I
>> > > > > > > > was
>> > > > > > > > compiling
>> > > > > > > > GIMP 2.10? Little confused. :)
>> > > > > > >
>> > > > > > > Cursor resource genration was changed in master, we now
>> > > > > > > generate
>> > > > > > > them in the directory where they are compiled , but they
>> > > > > > > have
>> > > > > > > to be linked in by force because nothing in the source
>> > > > > > > references
>> > > > > > > the symbol.
>> > > > > > >
>> > > > > > > Just check if you tools have different cursors.
>> > > > > > >
>> > > > > > > Sorry for the late response Mitch. Due to change in the App
>> > > > > > > structure, it
>> > > > > >
>> > > > > > took me a while to create a MacOS app.
>> > > > > >
>> > > > > > Anyway, I'm not exactly sure how to check if the tools have
>> > > > > > different
>> > > > > > cursors.  Do you mean for instance that If I've selected the
>> > > > > > lasso
>> > > > > > tool,
>> > > > > > then the cursor turns to a lasso? In my case it does.
>> > > > >
>> > > > > Then it's good :)
>> > > > >
>> > > >
>> > > > That's good to know from my perspective too! :)
>> > > >
>> > > > Then we have to remove Line 134 from ./app/Makefile.am.
>> > > > Otherwise,
>> > > > GIMP
>> > > > won't compile. Do you agree?
>> > >
>> > > If we remove that line, we don't have cursors at all, it simply
>> > > won't link in the file that's not referenced from anywhere,
>> > > on linux, gcc and standard ld.
>> >
>> > Sent too early...
>> >
>> > Does the linker error happend for gimp-console or gimp?
>>
> I think gimp-console, but I'll have to check again tonight and will let
> you know.
>
>>
>> Well... git pull :)
>>
> Will do. :) Thanks!
>

OK! You fixed it! Now it compiles. :)

Thanks!!
___
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] Problem with running GIMP (xc0000005)

[Partha Bagchi]

On Sun, Jun 17, 2018 at 5:20 PM Patryk Patryk  wrote:

> I have a problem as in title. Just had a fresh download of GIMP 2.10 stable
> version, from official site, from mirrors, other sites, I tried
> reinstall and right at the end of loading procces error message pop up,
> that it was imposible to run GIMP, it had xc005 in it. I tried to find
> solution but nobody had this problem with GIMP, and I just dont know what
> to do, right when I have some free time. I have to mention previous ver.
> 2.8 worked good as hell. Im using Win10 Insider at the moment.
> English is not my native language, if I wrote to wrong email or smth
> please, tell me where to find help
>
> Go into your personal GIMP folder -
C:\Users\YourUserName\AppData\Roaming\GIMP\2.10\plug-ins. If you find any
"exe" and "DLL" files, delete them. If you are attached to these files for
some reason, move them some place else.

Now restart your GIMP executable.

See if that fixes your issues.
___
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] Problem with running GIMP (xc0000005)

[Partha Bagchi]

On Mon, Jun 18, 2018 at 2:35 PM Patryk Patryk  wrote:

>  I dont know if I reply to Partha it will be good so I replying to develper
> list. Well, this folder is empty xD it should ? I have all drivers
> up-to-date, as I know netframework for windows is auto updated in my
> system, I think I have deleted all trashes which gimp 2.8 left, i cleaned
> registry with CCleaner, i have no idea whats wrong.
>
> Well, yes, please reply to the list as well. I personally don't mind if
you also CC me, but some others do seem to mind.

This error usually means that some DLL is loading itself when it shouldn't.
Hence my previous suggestion. You claim you have no such DLLs.

Windows will load DLLs as it encounters them in an application's startup
requirement.

To find these DLLs, it uses an algorithm whereby, first it looks into the
folder containing the executable, the current folder, the Windows System
folder, The Windows folder itself and finally the PATH environment
variable.

To locate which DLL is causing this violation, start GIMP with the verbose
option from a command window and see where you get the error.

My builds automatically create a logfile with this information to make it
easier for me to respond to these types issues. You can try my portable
build to see if you get the same error.

HTH,
Partha
___
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] Problem with running GIMP (xc0000005)

[Partha Bagchi]

On Mon, Jun 18, 2018 at 6:12 PM Patryk Patryk  wrote:

> Missing fast-path babl conversion detected, Implementing missing babl fast
> paths
> accelerates GEGL, GIMP and other software using babl, warnings are printed
> on
> first occurance of formats used where a conversion has to be synthesized
> programmatically by babl based on format description
>
> *WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
>
> ^ and this is what shows up in console
>
This is normal. So, GIMP itself is loading properly.

>
>
> wt., 19 cze 2018 o 00:07 Patryk Patryk  napisał(a):
>
> >
> > wavelet-decompose.exe.debug - Błąd aplikacji
>
I don't know about this. Try to locate this file and delete it.

I'm not totally sure why you have files with .debug extension. Perhaps
someone else can help you with this.
___
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] Problem with running GIMP (xc0000005)

[Partha Bagchi]

On Mon, Jun 18, 2018 at 6:51 PM Patryk Patryk  wrote:

> Ok, so I found both applications that I have problem with, web-page and
> wavelet-decompose. Both are applications, and both have their debug files.
> I have to delete debug files or applications, or all of them? Btw, its in
> GIMP 2>lib>gimp>2.0>plug-ins. Is this plug-ins folder you mentioned earlier
> ?

No,  the folder I mentioned is
C:\Users\YourUserName\AppData\Roaming\GIMP\2.10\plug-ins

Obviously, YourUserName = your login name on your computer.
___
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] Problem with running GIMP (xc0000005)

[Partha Bagchi]

On Mon, Jun 18, 2018 at 7:23 PM Patryk Patryk  wrote:

> Edit: Im sitting here just like WTF XD I deleted all the files (apps and
> their debug files) in this folder, except "python-console", and..
> Everything works XD loading screen goes to end and I have workspace and
> tools before me. I tried to make new, ee.. "canvas", you know, and its
> fine. I created new layer, and used some tools, works without crash. Can
> you guys tell me what happened ?
>
> wt., 19 cze 2018 o 01:13 Patryk Patryk  napisał(a):
>
> > Ok, so I deleted both applications with their debug files anyway, and ...
> > when I run gimp, i get same error as before, but now with other apps in
> > title xD Every hit on OK to end button bring up next error message with
> > next other app, to be honest, every app that this folder with plug-ins
> > contains. Earlier there was just one that i had problem with :/
> >
>

Yes, you probably lost all ability to open any files such as jpeg, tiff,
webp etc. Most likely you have some antivirus program or something that
either deletes all DLLs or quarantines them.  I don't recall where standard
Windows GIMP packages support DLLs, but check your application to see
whether you have any DLLs lib libtiff-x.x.dll libjpeg.dll etc.

Hope that helps,
Partha
___
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 can run two GIMP instances ?

[Partha Bagchi via gimp-developer-list]

On Fri, Jun 22, 2018 at 3:42 PM sebul via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> Hello, I'm a Korean GIMP user.
> I read https://www.gimp.org/downloads/ and
> I installed gimp by flatpak.
>
> I want run two GIMP instances, so one has English Menu and the other
> Korean.
>
> The following link does not help me.
>
> https://docs.gimp.org/2.10/en/gimp-fire-up.html#gimp-concepts-running-command-line
>
> In command line
> $ gimp
> not work.
>
> Help me please.
>
> gimp -n
___
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] GIMP Git UI Usability Issue MacOS

[Partha Bagchi via gimp-developer-list]

There is an UI usability issue that I thought might be worth reporting.

I prefer to keep only the tools on the left side in the single window mode.
So, if I take the lower half of the docked tabs to the right side and am
left with only the tools, the UI immediately extends far beyond the lower
half of the screen with no way to resize it. It also immediately glues
itself to the top.

The only way back is to go into Windows management and reset to default.

OS: MacOS.
Git pulled from last night.

Thanks,
Partha
___
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] GIMP 2.10.6 on Mac OS

[Partha Bagchi via gimp-developer-list]

There seems to be some recent changes that I cannot figure out. I'm
bundling 2.10.6 as I've done before (see McGimp 2.10.4 etc.). However, now
there is a new twist. All plug-ins results in the following error message:

babl-model.c:362 const Babl *babl_model(const char *)()
const Babl *babl_model(const char *)("RGBA"): you must call
babl_init first
sh: gdb: command not found


I don't know why this is happening only in 2.10.6 and didn't happen in
2.10.4. Also, why is it looking for gdb on a Mac? The usual Mac debugger is
lldb.

I know my build is fine and I can launch from the command line. But that's
not an App bundle.

Any help on how I can rectify this?

Thanks,
Partha
___
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] Xsane with Gimp on Mac OS X

[Partha Bagchi via gimp-developer-list]

At one point, I was thinking the same thing! Also for Windows, use the
native libraries.

Can you share your code offline with me? I'm not promising obviously since
I'm not at all a good programmer.


On Mon, Dec 31, 2018 at 4:22 AM Kristian Rietveld  wrote:

>
> > On 29 Dec 2018, at 18:56, Brion Vibber via gimp-developer-list <
> gimp-developer-list@gnome.org> wrote:
> >
> > Hmm... is something broken with the TWAIN scanner plugin on Mac, or
> perhaps
> > have scanner drivers moved away from using the TWAIN system and so that's
> > not picking up your driver?
>
> The TWAIN driver had issues on macOS. I think that for macOS the right way
> forward is to implement a plugin that uses the ImageCapture libraries. This
> will give you imports from scanners as well as cameras (including
> iphones/ipads) for all devices that ship with appropriate macOS drivers.
>
> I once started working on such a plugin but I have no interest in
> finishing it at this moment. It is not in a good enough shape to put in
> git. If anyone wants to continue working on this, let me know and I will
> happily share the code that I wrote as a starting point.
>
>
> regards,
>
> -kris.
>
> ___
> 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

Re: [Gimp-developer] Building babl & gegl with meson

[Partha Bagchi via gimp-developer-list]

Ofnut,

You are pretty well versed in this stuff. :)

This should get you started:

1. Babl:
git clone https://gitlab.gnome.org/GNOME/babl.git
meson builddir --prefix=$PREFIX/babl -Denable-gir=false -Dwith-docs=false
&& cd builddir
ninja install

2. GEGL
git clone https://gitlab.gnome.org/GNOME/gegl.git
meson builddir --prefix=$PREFIX/gegl -Dintrospection=false && cd builddir
ninja install

Obviously adjust the parameters as per your environment.

Also, I define the various flags up front. For example:

export PREFIX=$HOME/local
export CFLAGS='-g -O3 -ffast-math -ftree-vectorize'
export CPPFLAGS="-I$PREFIX/include -I$PREFIX/SuiteSparse/include"
export CXXFLAGS='-std=c++14 -O3 -ffast-math -ftree-vectorize'
export LDFLAGS="-L$PREFIX/lib -L$PREFIX/SuiteSparse/lib"
export LIBS="$LDFLAGS"
export
PATH=$HOME/local/bin:$HOME/local/python/bin:$PREFIX/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:$PREFIX/gegl/bin
export
PKG_CONFIG_PATH=$HOME/local/lib/pkgconfig:$PREFIX/lib/pkgconfig:$PREFIX/share/pkgconfig:/opt/X11/lib/pkgconfig:$PREFIX/babl/lib/pkgconfig:$PREFIX/babl/lib/pkgconfig

Hope this helps!

Partha



On Thu, Mar 5, 2020 at 6:09 PM Ofnuts  wrote:

> Is there a write-up somewhere indicating how to build Babl & Gegl? They
> seem to be using meson/ninja and all the indications I can find look
> fairly old and assume that they are built using autoconf+make.
>
> Cheers
>
>
> ___
> 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

Re: [Gimp-developer] EDIT > PREFERENCES on Mac OS X

[Partha Bagchi via gimp-developer-list]

Like every other Mac software (assuming it's built like that), it should be
under the name of the application.

On Sun, Jun 21, 2020 at 2:10 PM jEsuSdA 8)  wrote:

> Hi!
>
> Sorry, but can anyone tell me where I can find the "preferences" dialog
> on Gimp 2.10 for Mac OS X?
>
> It is not in EDIT menú.
>
> Thanks a lot!
>
>
> ___
> 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

Re: [Gimp-developer] EDIT > PREFERENCES on Mac OS X

[Partha Bagchi via gimp-developer-list]

See where it says "GIMP-2.10", click on it. :)

On Sun, Jun 21, 2020 at 6:08 PM jEsuSdA 8)  wrote:

> El 21/6/20 a las 20:10, jEsuSdA 8) escribió:
> > Hi!
> >
> > Sorry, but can anyone tell me where I can find the "preferences" dialog
> > on Gimp 2.10 for Mac OS X?
> >
> > It is not in EDIT menú.
> >
> > Thanks a lot!
> >
>
>
> I forgot send you a screenshot:
>
> https://pasteall.org/media/c/f/cf1877d01e122871d9d3c009be009cb8.png
>
> As you can see, some options I can find in my Windows and Linux version
> does not appear in mac one.
>
> ¿?¿?¿?
>
> Thanks!
> ___
> 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] GEGL build failure

[Partha Bagchi via gimp-developer-list]

partha@Parthas-MacBook-Pro gegl % ninja install
[1/722] Linking static target subprojects/poly2tri-c/libpoly2tri-c.a
FAILED: subprojects/poly2tri-c/libpoly2tri-c.a
rm -f subprojects/poly2tri-c/libpoly2tri-c.a && ar csr
subprojects/poly2tri-c/libpoly2tri-c.a ar: no archive members specified
usage:  ar -d [-TLsv] archive file ...
ar -m [-TLsv] archive file ...
ar -m [-abiTLsv] position archive file ...
ar -p [-TLsv] archive [file ...]
ar -q [-cTLsv] archive file ...
ar -r [-cuTLsv] archive file ...
ar -r [-abciuTLsv] position archive file ...
ar -t [-TLsv] archive [file ...]
ar -x [-ouTLsv] archive [file ...]
[10/722] Compiling C object 'libs/rgbe/2e83b36@@rgbe@sta/rgbe.c.o'
ninja: build stopped: subcommand failed.


This will work on Linux and Windows but not on Mac. I work around it but
probably better to fix it at the source.

Thanks,
Partha
___
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] GEGL build failure

[Partha Bagchi via gimp-developer-list]

Thanks for pointing that out.

Yes, empty archives cannot be compiled on Mac. So, you can use an empty
dummy file or combine the 2 lines in ninja. It's not a meson bug.

On Sun, Sep 27, 2020 at 6:04 AM Gregory Reshetniak  wrote:

> Hi Partha
>
> Have a look at this issue, seems to be related
> https://gitlab.gnome.org/GNOME/gegl/-/issues/214
>
>
>
> On Sun, 27 Sep 2020 at 05:08, Partha Bagchi via gimp-developer-list <
> gimp-developer-list@gnome.org> wrote:
>
>> partha@Parthas-MacBook-Pro gegl % ninja install
>> [1/722] Linking static target subprojects/poly2tri-c/libpoly2tri-c.a
>> FAILED: subprojects/poly2tri-c/libpoly2tri-c.a
>> rm -f subprojects/poly2tri-c/libpoly2tri-c.a && ar csr
>> subprojects/poly2tri-c/libpoly2tri-c.a ar: no archive members specified
>> usage:  ar -d [-TLsv] archive file ...
>> ar -m [-TLsv] archive file ...
>> ar -m [-abiTLsv] position archive file ...
>> ar -p [-TLsv] archive [file ...]
>> ar -q [-cTLsv] archive file ...
>> ar -r [-cuTLsv] archive file ...
>> ar -r [-abciuTLsv] position archive file ...
>> ar -t [-TLsv] archive [file ...]
>> ar -x [-ouTLsv] archive [file ...]
>> [10/722] Compiling C object 'libs/rgbe/2e83b36@@rgbe@sta/rgbe.c.o'
>> ninja: build stopped: subcommand failed.
>>
>>
>> This will work on Linux and Windows but not on Mac. I work around it but
>> probably better to fix it at the source.
>>
>> Thanks,
>> Partha
>> ___
>> 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
>>
>
>
> --
>
> <https://about.me/gregory.reshetniak?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
> Gregory Reshetniak
> about.me/gregory.reshetniak
> <https://about.me/gregory.reshetniak?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
>
___
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.22

[Partha Bagchi via gimp-developer-list]

I'm working on my McGimp build as we speak. So, it should be out soon.

On Thu, Oct 8, 2020 at 4:57 PM Alexandre Prokoudine via gimp-developer-list
 wrote:

> Hi,
>
> GIMP 2.10.22 is out. Release highlights:
>
> - Improved HEIC and newly added AVIF support
> - Numerous improvements in the PSP file format support
> - Improved multi-layer TIFF exporting
> - Better handling of the Exif “Orientation” metadata
> - New “Sample merged” option in the GEGL operation tool
>
> Details: https://www.gimp.org/news/2020/10/07/gimp-2-10-22-released/
>
> Windows installer is available, so is the flatpak for Linux.
> Unfortunately, we won't have a build for macOS until someone steps up
> and contributes it.
>
> Alex
> ___
> 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