Re: G-Golf - Callback segmentation fault

[David Pirotte <david@altosw.be>]

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

Hi Florian,

> Hello David.  Thank you for this important groundwork that g-golf is.

Thanks for the nice words - I hope that some day, with the help of
Guix/Nix maintainer(s), we can identify and solve the problem.

> Sorry to say, I have not developed any GUI and had no time as planned.
> It will not happen with me.  But Debian is not the problem; all is
> fine there (unlike G-Golf on Guix on Debian).

It's ok, i just wanted to know if you had given it a try, and see
for yourself that using debian, everything works fine.

> I also failed to put a libg-golf-tests library to actually test
> gobject libraries in g-golf’s tests and link it with libtool ...

I don't follow you here, in order to run the g-golf test-suite, all
you need to do, in a build tree, is to run 'make check'

> The feedback I can give: guile-zlib in its build system autodetects
> ...

Not sure i want to do this.

> I’m missing an entry point to debug if the problem is ...
> ...
> which I cannot understand at the moment.  I suspect you’d need similar
> work.

I have no idea what guix/nix 'need' so g-golf works there as well, this
is a question you have to raise with guix/nix maintainers ...

> Then, I see on docs.gtk.org there is a girepository 3.0 (likely a typo
> and meant to say 2.0)

Nope, this is explained in the migration doc

> migration which will make it hard to try the latest girepository
> version with g-golf ...

Don't worry, i'll deal with the migration, in due time ...

> So indeed you regard it as unrelated, too.

Yes.

> Could you document this purpose of vfunc-checks in
> g-golf/hl-api/vfunc.scm?

Not in any foreseen future.

Thanks,
David


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]