Re: [Chicken-users] C_INSTALL_* surprises

[felix winkelmann]

On 7/19/06, Brandon J. Van Every <address@hidden> wrote:
> >>
> >> #ifndef C_INSTALL_LIB_HOME
> >> # define C_INSTALL_LIB_HOME "/cygdrive/c/Program
> >> Files/cygchicken/lib/chicken/1"
> >>
> >> I thought this was going to be for Chicken libraries, not for eggs, i.e.
> >> "/cygdrive/c/Program Files/cygchicken/lib/chicken"
> >
> > Shouldn't these actually all be UNIXish pathnames, i.e. "/usr/lib",
> > etc. ???
>
> That's not important.  I used --prefix="/cygdrive/c/Program
> Files/cygchicken" in this instance.  A user can specify anything he
> likes for a ./configure --prefix.

Indeed - I didn't see that, my bad.

> The question is whether
> C_INSTALL_LIB_HOME is for Chicken libraries or for Eggs.

for eggs, it specifies the default location of installed extensions
and is used by the runtime-system ("require-extension" in the end).

> >
> >>
> >> C_INSTALL_INCLUDE_HOME appears to have been expunged from the build.
> >> Yet, csc.scm.in still takes a substitution of %includedir% from
> >> ./configure.  For consistency, shouldn't this remain available?
> >
> > If we don't need it, it might as well be gone.
>
> But it makes the build more obscure.  %includedir% isn't going away.

It is, if I want it to... :-)


--
http://galinha.ucpel.tche.br:8081/blog/blog.ssp