From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: David Pirotte <david@altosw.be>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-a.1 available for testing!
Date: Fri, 16 Dec 2022 15:50:24 -0800 [thread overview]
Message-ID: <CA+XASoUHrhqeUa6e1Odcmi=qG6+2BdZDNjn-iE1QcwBhh=njLw@mail.gmail.com> (raw)
In-Reply-To: <20221213173720.58a48002@aicha>
[-- Attachment #1: Type: text/plain, Size: 3742 bytes --]
Great! Thank you David!
I was able to add g-golf to Guile Homebrew. So it now runs on macOS (see
images here [1]). I had to do a couple of changes, see line 33, 34, 35 and
also two simple patches at the end of:
https://github.com/aconchillo/homebrew-guile/blob/master/Formula/g-golf.rb
The changes are:
- We need the full path of glib, gobject, etc. They are not always in
/usr/lib. For example, guile-gcrypt solves this by specifying
--with-libgcrypt-prefix and we can point to /opt/homebrew/ for example.
That's what those inreplace lines do.
- The configure.ac patch fixes SITEDIR and SITECACHEDIR when
--with-guile-site=no. Btw, this is also the case for guile-lib (has the
same code). I believe the right paths should be:
SITEDIR="$datadir/guile/site/$GUILE_EFFECTIVE_VERSION";
SITECCACHEDIR="$libdir/guile/$GUILE_EFFECTIVE_VERSION/site-ccache";
- The Makefile.am patch places libg-golf in the Guile extensions directory
$(libdir)/guile/$(GUILE_EFFECTIVE_VERSION)/extensions, which I believe is
the right thing to do.
I hope this helps. If all this makes sense I can send patches.
Best,
Aleix
[1] https://emacs.ch/@aconchillo/109519735429741042
On Tue, Dec 13, 2022 at 12:37 PM David Pirotte <david@altosw.be> wrote:
> Hello Guilers,
>
> The first alpha release of the upcoming 0.8.0 release is now available
> for testing:
>
> Tarball and a GPG detached signature [*]:
>
> http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-a.1.tar.gz
> http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-a.1.tar.gz.sig
>
> Dependencies and complete installation instructions are given
> in the distributed INSTALL file, or here:
>
> https://www.gnu.org/software/g-golf/install.html
>
> You can help by:
>
> 1. Testing by installing from the tarball, or from the source if you
> prefer, on the distro of your choice.
>
> 2. By running the distributed examples.
>
> Ultimately, one of the best way to test, and participate, is to select
> G-Golf to develop the next application of your dream! Here is an
> overview of the GNOME platform libraries [1], accessible using G-Golf.
> In particular, libadwaita [2] provides a number of widgets that change
> their layout based on the available space. This can be used to make
> applications adapt their UI between desktop and mobile devices.
>
> Contact [3]
>
> Before you email, or bug report, you could join us on irc, and ping
> me there: be patient, I also need to eat, sleep, rest ... but I always
> answer, and this my preferred way to quickly interact and fix potential
> G-Golf problem(s).
>
> On irc, we chat :), so please do not write code snipsets there unless 2
> or 3 lines of code, nor error messages of course - for more then 2 or 3
> lines of code, or error messages, always use a tor-friendly paste
> service (avoid those that tracks us an require javascript, thanks!)
>
> However, if you prefer:
>
> G-Golf uses Guile's mailing lists
> Report bugs to bug-g-golf@gnu.org
>
> Thanks!
> David
>
> [*] Use a .sig file to verify that the corresponding file (without the
> .sig suffix) is intact. First, be sure to download both the .sig
> file and the corresponding tarball. Then, run a command like this:
>
> gpg --verify g-golf-0.8.0-a.1.tar.gz
>
> If that command fails because you don't have the required public
> key, then run this command to import it:
>
> gpg --keyserver keys.gnupg.net --recv-keys A3057AD7
>
> and rerun the 'gpg --verify' command
>
>
> [1]
> https://developer.gnome.org/documentation/introduction/overview/libraries.html
> [2] https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/
> [3] https://www.gnu.org/software/g-golf/contact.html
>
[-- Attachment #2: Type: text/html, Size: 6434 bytes --]
next prev parent reply other threads:[~2022-12-16 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 20:37 GNU G-Golf 0.8.0-a.1 available for testing! David Pirotte
2022-12-14 12:55 ` Luis Felipe
2022-12-16 23:50 ` Aleix Conchillo Flaqué [this message]
2023-03-25 4:18 ` David Pirotte
2023-04-30 4:18 ` Aleix Conchillo Flaqué
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='CA+XASoUHrhqeUa6e1Odcmi=qG6+2BdZDNjn-iE1QcwBhh=njLw@mail.gmail.com' \
--to=aconchillo@gmail.com \
--cc=david@altosw.be \
--cc=guile-devel@gnu.org \
--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).