Re: [gforth] Configuring multiple libccdirs

[Bernd Paysan]

Am Dienstag, 3. Juli 2018, 18:05:21 CEST schrieb Anton Ertl:
> The question is if it makes sense.  The files in these directories are
> cached intermediate results produced from Forth source files
> containing C-interface stuff.

Actually, the libcc API has stabilized, and the need to recompile the libcc 
interfaces for every Gforth snapshot isn't there anymore.

So it makes sense to install programs with precompiled libcc-named files, and 
keep them separate from the Gforth directory, which is updated every week or 
so (if they use my snapshot Debian repository).

> We have two directories for the
> following reasons:
> 
> 2) $libccdir for files created by the superuser at Gforth
> installation, so the user does not need a C compiler when using the
> source C-interface files; it also allows sharing these files between
> different users, without one user being able to attack another user by
> providing a Trojan intermediate file.
> 
> 1) For C-interface stuff beyond libccdir, each user produces his own
> intermediate files in ~/.gforth/<machine-type>/libcc-named.
> 
> For what purpose would one use more directories?

As I can see the request, for third-party programs using Gforth as Forth 
engine, who want to install their files in a different directory.   The source 
files installed in some other directory can be dealt with GFORTHPATH, the 
libcc-named files installed not — they have to go to a version specific Gforth 
directory.

We can also discuss if we add the $prefix/lib/.../site-forth path into the 
libcc-path by default.

-- 
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o id: kQusJzA;address@hidden(dQ*
https://net2o.de/

signature.asc
Description: This is a digitally signed message part.