unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: guile-devel <guile-devel@gnu.org>
Subject: source and compiled file installtion locations
Date: Thu, 3 May 2018 02:15:34 -0300	[thread overview]
Message-ID: <20180503021534.0abd1de5@capac> (raw)

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

Hello Guilers,

I'm still in doubt wrt guile-lib (as a matter of fact, could be any project) source
and compiled file location, and would like to hear what people think.

Most of us (if not all, copying each other I guess) install our project files either
in:

	GUILE_SITE			[ source files
	GUILE_SITE_CCACHE	[ compiled files
or
	$(datarootdir)/guile/site/GUILE_EFFECTIVE_VERSION		[ source
	$(libdir)/guile/GUILE_EFFECTIVE_VERSION/site-ccache	[ compiled

	[ for those of us who have a proper implementation and follow a --prefix
	[ given by the user ...

	[ other files (doc, libs if C coe...) follow GNU standards and honor
	[ --prefix if given ...

In my opinion, unless the project defines a user option, --use-guile-site [1], all
these locations are incorrect (except 'other files..], let me explain:

1-	no --use-guile-site

in this case, imo, locations should be

	$(datarootdir)/<project-name>						[ source
	$(libdir)/<project-name>/guile-GUILE_EFFECTIVE_VERSION/site-ccache
	[ compiled

2-	--use-guile-site

in this case, imo, location should be

	GUILE_GLOBAL_SITE	[2]	[ source files
	GUILE_SITE_CCACHE		[ compiled files

Wrt the former, it is because I think, unless the s/w source is not 2.0 and 2.2
compatible, there is no reason it should land in a GUILE_EFFECTIVE_VERSION
subdir. If indeed the s/w is guile version dependent, then the former would be
GUILE_SITE ...

WDYT?
Thanks,

David

[1]	I see some uses --with-guilesitedir

I have two remarks (quiz) wrt this: (a) in the doc (autoconf), you see that
--with-foo, defined using AC_ARG_WITH is related to enable the 'foo' external
lbrary, which is not our case; (b) --with-guilesitedir refers to GUILE_SITE_DIR,
which actually is the name of the m4 macro, the variable this macro defines is
GUILE_SITE, so I opted for --use-guile-site

[2]	see %global-site-dir in the manual

I defined a few guile-ext.m4 ('extensions '), here

	http://git.savannah.gnu.org/cgit/guile-cv.git/tree/m4/guile-ext.m4

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

             reply	other threads:[~2018-05-03  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  5:15 David Pirotte [this message]
2018-05-06  0:03 ` source and compiled file installtion locations David Pirotte
2018-05-06  8:56   ` Chris Vine
2018-05-06 22: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=20180503021534.0abd1de5@capac \
    --to=david@altosw.be \
    --cc=guile-devel@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).