On Sun, 2015-02-15 at 11:40 +0100, Murray Cumming wrote:
> However, while getting these screenshots I noticed that the change is
> caused by different GTK+ versions, regardless of what API I use. I'll
> try to narrow down what caused the change and file a bug.
I was wrong again. The problem was in
I’ve been working through the instructions on
http://wiki.gnucash.org/wiki/MacOSX/Quartz for building gnucash on MacOS, in
particular the section
> Go to the GTK-OSX Build Instructions and follow the instructions up through
> running jhbuild bootstrap.
Which redirected me to
https://wiki.g
On Fri, Feb 20, 2015 at 09:40:25AM -0500, R. Victor Klassen wrote:
> I found a version of gtkversion.h elsewhere, but it was quite old.
> Presumably there should be a gtkversion.h in gtk/include/gtk after the
> git checkout implicitly run by jhbuild?
It's a generated file (from gtk/gtkversion.h.in
If that’s the case, then the question is why I didn’t get gtk/gtkversion.h.in
On Feb 20, 2015, at 10:29 AM, David Nečas wrote:
> On Fri, Feb 20, 2015 at 09:40:25AM -0500, R. Victor Klassen wrote:
>> I found a version of gtkversion.h elsewhere, but it was quite old.
>> Presumably there should be
Hi, I'm still struggling with GTK+ compilation and it looks I found a
problem (or bug) but I'm not sure how to solve it and seek your
recommendation or hint on what to do...
I compiled both x86 and x64 stable GTK+ binaries and *all* it's
dependencies with MSVC, today for testing purposes I even al
Hi, guys! Please excuse me, but I figured out what was the problem and now
most recent msvc GTK+ WORKS!!
indeed it was a problem with libffi, to be more precize it was my fault
because of the way I was building the libffi library in wrong way lol.
according to the libffi readme on GitHub there is
