> On 31 Dec 2018, at 14:32, Partha Bagchi wrote:
>
> At one point, I was thinking the same thing! Also for Windows, use the native
> libraries.
Perhaps there could even be one UI that works with both backends; not sure
though.
>
> Can you share your code offline with me? I'm not promising
> On 29 Dec 2018, at 18:56, Brion Vibber via gimp-developer-list
> 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
> On 22 May 2018, at 16:01, Jehan Pagès wrote:
>
> There is another issue which was raised these days by GTK+ developers who
> discussed GIMP port: apparently GTK+3.99 (to become GTK+4) has currently no
> macOS backend! Basically that means we'd lose GIMP on macOS.
> On 12 May 2018, at 14:00, Philip Lehmann-Böhm wrote:
>
> I've read in the FAQs that the guy with the Mac is a bit busy at the moment
> and so there is hardly any time left for creating the DMG. Maybe I could help
> here and do the build? I would just need some directions
> On 28 Mar 2018, at 15:27, Carmelo DrRaw wrote:
>
>
> I am using homebrew to install the dependencies, honestly I find it more
> practical than jhbuild.
> When creating the bundle, the libraries installed via homebrew are included
> so that the bundle is
Forgot to CC the mailing list ...
On Wed, Mar 28, 2018 at 2:58 PM, Kristian Rietveld <k...@loopnest.org> wrote:
> On Wed, Mar 28, 2018 at 7:51 AM, Carmelo DrRaw <aferrero1...@gmail.com> wrote:
>> There are actually two major things I can offer:
>> * try to fix OSX-sp
> On 27 Mar 2018, at 03:25, Jehan Pagès wrote:
>
> But right now, we are discussing paying to distribute a version of GIMP
> which is barely kept alive. This is a bit doing things in the wrong order
> IMO.
In fact, I think this is the main point. Even in the case we
> On 13 May 2017, at 15:21, Jehan Pagès wrote:
>> A potential solution could be to write a Mac-specific GIO TLS backend that
>> depends on macOS system libraries which can be shipped instead of the
>> default TLS backend that depends on gnutls.
>
> Of course, this
Try to disable introspection while building pygobject-2, add the following
configure option:
--enable-introspection=no
regards,
-kris.
> On 18 May 2017, at 18:10, Carmelo DrRaw wrote:
>
> Thanks!
>
> May I also ask your gobject-introspection version?
>
>>>
>>>
Hi all,
We have a 2.8.18 DMG now that will be hitting the mirrors (and website) soon.
For this DMG I have updated almost all of the the dependencies. Also the issues
with icons in the file chooser have been (mostly) resolved.
I did not yet get to fixing the other reported issues, such as
Hello everybody,
At LGM I got dragged into GIMP's Python plug-in. The main question
regarding GIMP's Python plug-in is how to incorporate support for GEGL
for the GIMP 2.10 release. This may seem rather trivial, but unfortunately
this is not the case. In this e-mail I will briefly explain the
> On 31 Dec 2015, at 14:13, scl wrote:
>
>
>> And the steps after that are to automate the process
>
> This reminds me of my attempts to integrate an OS X build slave
> into the Jenkins continuous build environment. Sam Gleske or
> Tobias Vogel might be able to tell you
Hi Sven,
Thanks for your feedback!
> On 28 Dec 2015, at 10:19, scl wrote:
>
> 2. Is this build with the latest dependency versions?
No, the first step was to reproduce a build using your instructions on my
system. Your detailed instructions have been very helpful, thanks
Hi all,
I am looking for people that would like to volunteer to test our Mac OS X DMG
releases. We have a freshly baked 2.8.16 DMG ready for testing now at:
http://download.gimp.org/pub/gimp/v2.8/osx/testing/gimp-2.8.16-x86_64.dmg
It should run on Mac OS X 10.6 and higher.
If you find any
14 matches
Mail list logo