site %load-compiled-path

site %load-compiled-path

[Andy Wingo]

Hi,

I realized in the discussion with Ian Hulin that a number of my projects
are installing their .go files in the wrong place -- to the datadir
instead of to the libdir.  That's silly, because the datadir isn't in
the load-compiled-path.

Consider the default load paths on this Guile installed to /opt/guile:

  scheme@(guile-user)> %load-compiled-path 
  $1 = ("/opt/guile/lib/guile/2.0/ccache")
  scheme@(guile-user)> %load-path 
  $2 = ("/opt/guile/share/guile/2.0" "/opt/guile/share/guile/site/2.0"
        "/opt/guile/share/guile/site" "/opt/guile/share/guile")

I'm installing my Scheme files to site/ or site/2.0/.  We probably need
a corresponding site dir for compiled files.  So if there are no
objections I will add $libdir/guile/site/2.0/ccache to the load-compiled
path.  (We don't need the site/ versus site/2.0/ distinction, as
compilation is naturally version-specific.)

Regards,

Andy
-- 
http://wingolog.org/

Re: site %load-compiled-path

[Ludovic Courtès]

Hi!

Andy Wingo <wingo@pobox.com> skribis:

> I realized in the discussion with Ian Hulin that a number of my projects
> are installing their .go files in the wrong place -- to the datadir
> instead of to the libdir.  That's silly, because the datadir isn't in
> the load-compiled-path.

To Guile’s datadir or the project’s datadir?

By default, it should be the latter, in which case you need to add it to
the load path anyway.

Thanks,
Ludo’.