Am Dienstag, 3. Juli 2018, 12:03:57 CEST schrieb Reepca Russelstein: > Currently there are two places gforth will check for already-existing > compiled wrapper code: > > 1. ~/.gforth/<machine-type>/libcc-named > 2. $libccdir or, if that isn't set, the value of $libccdir at the time > gforth was compiled. > > This presents an issue if we have wrapper code we want to go somewhere > else and want gforth to still be able to find its own wrapper code - > we can't set libccdir for this purpose. For example, if I want to > install a separate package that provides wrapper code - maybe I'll > call it gforth-glfw - I'd want to put it in > PREFIX/lib/gforth/site-forth/libcc-named. > > Could we change libccdir to specify a search path instead of a single > directory, with build-time $libccdir implicitly prepended to that > path?
Yes, that's easy to do. I would suggest however to keep libccdir as is, and add a GFORTHCCPATH the way you want to. Public visible environment variables controlling Gforth should be in uppercase and have a GFORTH in their name. > I see that libcc.fs already uses a search path internally for > it. The only complication I could foresee is saving the build-time > path as opposed to a single string. No complication. A path is also just a string (with '\0' as separating character). -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/
signature.asc
Description: This is a digitally signed message part.
