unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Lee Thomas <leet22303be@gmail.com>
Cc: Jessica Tallon <tsyesika@tsyesika.se>, 57379@debbugs.gnu.org
Subject: bug#57379: GUI toolkit for Guile 3.0?
Date: Mon, 29 Aug 2022 13:54:37 -0300	[thread overview]
Message-ID: <20220829135437.1b5cd442@aicha> (raw)
In-Reply-To: <CANYin9WkASN=Y8yEbUctCoBKxNbDeNWFXaXUY9p2v9PckOA90Q@mail.gmail.com>

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

Hello Lee,

> Thanks again, David.

Welcome.

> I was able to use a solution from Ricardo to get guile-gi to run
> under guix

I hope Ricardo, possibly with the help of other guix contributor's will
find a solution so that g-golf may also run 'out of the box' on guix.

> guile 3.0.7, which I hope would be OK.

Yes, you need guile 2.0, 2.2 or 3.0, in which case it must be >= 3.0.7

> For g-golf, would you > recommend I clone your github repo and
> compile it . . . ?

Yes, installing from the source tree instructions are here:

	https://www.gnu.org/software/g-golf/install.html

	[ just 'stick' to the master branch, although I may recommend
	[ to use the devel branch 'in the future', at this moment the
	[ devel branch is in a wip stage.

Two things to add to those instructions:

1.
	to run the checks, 'make check', you'd need two additional
	dependencies:

		gir1.2-clutter-1.0:amd64
		gir1.2-gtk-3.0:amd64

	I'll get rid of those dependencies before the first official
	release, but for now, some tests use either clutter or gtk-3

2.

	to run g-golf examples, you need to install

		gir1.2-gtk-4.0:amd64

	you may try the examples before installing, like this:

	cd  <...g-golf-tree...>/examples/gtk-4
	../../pre-inst-env ./hello-world.scm

This page shows a screenshot for each example:

	https://www.gnu.org/software/g-golf/learn.html

Let me kow how it goes,
Thanks,
David

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

  parent reply	other threads:[~2022-08-29 16:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  2:35 bug#57379: GUI toolkit for Guile 3.0? Lee Thomas
2022-08-24 12:29 ` Jessica Tallon
2022-08-24 16:05   ` Lee Thomas
2022-08-24 18:55     ` Jessica Tallon
2022-08-24 20:03   ` David Pirotte
2022-08-24 21:49     ` Lee Thomas
2022-08-26  2:27       ` David Pirotte
2022-08-26 20:03         ` Lee Thomas
2022-08-26 20:35           ` Ricardo Wurmus
2022-08-26 21:11             ` Lee Thomas
2022-08-27  8:30               ` Ricardo Wurmus
2022-08-28 23:04                 ` David Pirotte
2022-08-28 22:42           ` David Pirotte
2022-08-29  2:32             ` Lee Thomas
2022-08-29  9:11               ` Ricardo Wurmus
2022-08-29  9:12               ` Ricardo Wurmus
2022-08-29 16:54               ` David Pirotte [this message]
2022-08-29 18:22                 ` Lee Thomas
2022-08-29 23:23                   ` David Pirotte
2022-08-30 18:33                     ` Lee Thomas
2022-09-01  7:17                       ` adriano
2022-09-03  4:26                       ` David Pirotte
2022-08-29 19:55                 ` Ricardo Wurmus
2022-08-30 18:24                   ` Lee Thomas
2022-09-03  4:15                     ` 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=20220829135437.1b5cd442@aicha \
    --to=david@altosw.be \
    --cc=57379@debbugs.gnu.org \
    --cc=leet22303be@gmail.com \
    --cc=tsyesika@tsyesika.se \
    /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).