From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: David Pirotte <david@altosw.be>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-rc-3 available for testing
Date: Wed, 01 May 2024 10:17:27 +0200 [thread overview]
Message-ID: <87r0em7xpk.fsf@pelzflorian.de> (raw)
In-Reply-To: <20240430215102.2f6f74b7@tintin> (David Pirotte's message of "Tue, 30 Apr 2024 21:51:02 -0300")
Hello David,
David Pirotte <david@altosw.be> writes:
> fwiw, g-golf doesn't load/import/invoke/call nor the GdkPixbuf
> typelib, nor any of its functions/methods 'on its own', nor
> does any example, this occurs as part of the Gtk/Gdk/Gsk
> 'engine' - it is not g-golf that 'runs g_typelib_symbol on
> GdkPixbuf functions;
I had not known that g-golf does not call g_typelib_symbol. I will
have to read more what calls it initially.
The initial calls are to a GdkPixbuf path listed in environment
variables, later calls are to a GdkPixbuf path referenced in the files
that are part of GTK. Yes, Guix should make it so the two are the same.
> Fwiw, debian 'generally' has two pkg for 'those situations', one with
> the library itself and one for the debug symbols:
Guix does the same, but for GTK, it runs a different GdkPixbuf build
entirely without debug symbols, with different build steps, therefore a
different hash, therefore a different file path. Guix has bug#48907
filed, because debug symbols do not work, that Guix should not create
two paths or that debug symbols should work despite Guix doing that.
> You (the guix team) should fix Guix, not the g-golf app(s).
Yes.
>> The second issue is the vfuncs when running
>> examples/gtk-4/drawing-widget.scm. This segfaults at
>> gtk_widget_snapshot_child when run.
This I will investigate firdy.
> […]
> What about pygobject?
pygobject GTK3 examples are working. I will experiment and try to write
Vala/C code that breaks now.
> 1- fix guix to have one gdk-pixbuf module
> 2- let's try to fix the vfunc problem in guix, using the
> examples/gtk-4/drawing-widget.scm ... or some even easier vfunc
> test code i could write if necessary
I will look at 2 in the next days.
Regards,
Florian
next prev parent reply other threads:[~2024-05-01 8:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 5:56 GNU G-Golf 0.8.0-rc-3 available for testing David Pirotte
2024-04-17 22:30 ` pelzflorian (Florian Pelz)
2024-04-18 22:21 ` David Pirotte
2024-04-19 17:00 ` pelzflorian (Florian Pelz)
2024-04-20 4:51 ` David Pirotte
2024-04-20 8:35 ` pelzflorian (Florian Pelz)
2024-04-30 17:51 ` pelzflorian (Florian Pelz)
2024-05-01 0:51 ` David Pirotte
2024-05-01 8:17 ` pelzflorian (Florian Pelz) [this message]
2024-05-07 1:39 ` David Pirotte
2024-05-07 9:36 ` pelzflorian (Florian Pelz)
2024-05-07 23:53 ` David Pirotte
2024-05-08 10:49 ` pelzflorian (Florian Pelz)
2024-05-08 21:51 ` David Pirotte
2024-05-02 18:50 ` pelzflorian (Florian Pelz)
2024-05-02 21:57 ` David Pirotte
2024-05-03 5:00 ` David Pirotte
2024-05-03 11:35 ` pelzflorian (Florian Pelz)
2024-05-04 5:59 ` David Pirotte
2024-05-04 14:31 ` pelzflorian (Florian Pelz)
2024-05-04 18:08 ` pelzflorian (Florian Pelz)
2024-05-04 22:11 ` David Pirotte
2024-05-04 22:23 ` David Pirotte
2024-05-04 21:39 ` David Pirotte
2024-05-05 1:43 ` pelzflorian (Florian Pelz)
2024-05-05 21:30 ` David Pirotte
2024-05-06 9:45 ` pelzflorian (Florian Pelz)
2024-05-06 9:53 ` Basile Starynkevitch
2024-05-06 13:08 ` pelzflorian (Florian Pelz)
2024-05-03 0:17 ` David Pirotte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0em7xpk.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=david@altosw.be \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).