From: David Pirotte <david@altosw.be>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
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: Sat, 25 Mar 2023 01:18:40 -0300 [thread overview]
Message-ID: <20230325011840.5140a21c@aicha> (raw)
In-Reply-To: <CA+XASoUHrhqeUa6e1Odcmi=qG6+2BdZDNjn-iE1QcwBhh=njLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
Hello Aleix,
I am sorry it took me so long to answer.
> ...
> I was able to add g-golf to Guile Homebrew. So it now runs on macOS
> ...
> The changes are:
>
> - We need the full path of glib, gobject, etc.
Certainly not, never ever :) - This is a distro thing, Upstream gnu
tool chained pkg(s) should never ever do that.
> - The configure.ac patch fixes SITEDIR and SITECACHEDIR when
> --with-guile-site=no ...
No,
Exactly the opposite, that is, their setting is correct, both in
g-golf, guile-lib and guile-cv fwiw
when a user does not configure passing the --with-guile-site=yes
then _nothing_, nor the pkg scm modules, nor the .go files, nor
any lib should be installed in the 'guile installed dirs'
> - 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.
you mean the libg-golf/Makefile.am i guess
[ and you probably don't mean
[ $(libdir)/guile/$(GUILE_EFFECTIVE_VERSION)/extensions
[ but GUILE_EXTENSION (provided by guile.m4
I agree with you that when a g-golf user calls configure passing the
--with-guile-site=yes, then libg-golf could be installed in
GUILE_EXTENSION dir.
Cheers,
David
If not, then the current- g-golf setting is correct
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-25 4:18 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é
2023-03-25 4:18 ` David Pirotte [this message]
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=20230325011840.5140a21c@aicha \
--to=david@altosw.be \
--cc=aconchillo@gmail.com \
--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).