From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mike Gran <spk121@yahoo.com>
Cc: guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: [ANN] guile-gi v0.0.1 released
Date: Tue, 04 Jun 2019 21:47:05 +0200 [thread overview]
Message-ID: <87tvd5t9om.fsf@gnu.org> (raw)
In-Reply-To: <20190604144501.GA14845@spikycactus.attlocal.net> (Mike Gran's message of "Tue, 4 Jun 2019 07:45:01 -0700")
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Mike Gran writes:
Hi!
> Both guile-gnome and my hack have two parts
> - an introspection layer
> - a gobject-to-guile binding
>
> I had a chat with Wingo at the last FOSDEM, and he thinks the
> gobject-to-guile binding could be reused, and that I could just swap
> the gwrap GTK+2 introspection layer with a GObject introspection
> layer. I began analyzing that path a few months before life
> intervened.
Okay, good.
>> I'm quite new to all this, I cannot see the great difference in gtk+2
>> and gtk+3 here, even...
>>
>> >> Patches also on my `wip' branch: https://gitlab.com/janneke/guile-gi.git
>
> I incorporated these, and fixed the bug that caused your editor example
> to fail. Thanks!
Oh great, and that's fast. Thanks! You maybe even did a bit too well,
the `bytes_new_null_size.scm' test now passes. I added that to
XFAIL_TEST because it fails -- now make check fails because this test is
fixed.
The attach patch removes that workaround again. If you apply this or
something equivalent, I will update the Guix package to point to your
updated repo.
Greetings,
jannneke
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-test-Update-for-passing-bytes_new_null_size.scm.patch --]
[-- Type: text/x-patch, Size: 701 bytes --]
From 810baa9427145d08b4c9ff46ee442e296eb1911b Mon Sep 17 00:00:00 2001
From: Jan Nieuwenhuizen <janneke@gnu.org>
Date: Tue, 4 Jun 2019 21:40:34 +0200
Subject: [PATCH] test: Update for passing bytes_new_null_size.scm.
* test/Makefile.am (XFAIL_TESTS): Remove bytes_new_null_size.
---
test/Makefile.am | 3 ---
1 file changed, 3 deletions(-)
diff --git a/test/Makefile.am b/test/Makefile.am
index e647105..3cca48f 100644
--- a/test/Makefile.am
+++ b/test/Makefile.am
@@ -39,9 +39,6 @@ TESTS = \
gapplication_2.scm \
softerror_create.scm
-XFAIL_TESTS = \
- bytes_new_null_size.scm
-
SCM_LOG_COMPILER = \
${top_builddir}/libtool \
--dlopen=${top_builddir}/src/libguile-gi.la \
--
2.21.0
[-- Attachment #3: Type: text/plain, Size: 152 bytes --]
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2019-06-04 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181115144125.GA23468@joshua.dnsalias.com>
2019-06-01 9:02 ` [ANN] guile-gi v0.0.1 released Jan Nieuwenhuizen
2019-06-02 16:15 ` Ludovic Courtès
2019-06-02 18:22 ` Jan Nieuwenhuizen
2019-06-03 14:46 ` Mike Gran
2019-06-03 16:41 ` Jan Nieuwenhuizen
2019-06-04 14:45 ` Mike Gran
2019-06-04 19:47 ` Jan Nieuwenhuizen [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvd5t9om.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=spk121@yahoo.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).