[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] C_INSTALL_* surprises
From: |
felix winkelmann |
Subject: |
Re: [Chicken-users] C_INSTALL_* surprises |
Date: |
Wed, 19 Jul 2006 07:48:29 +0200 |
On 7/19/06, Brandon J. Van Every <address@hidden> wrote:
In the ./configure build of chicken-defaults.h:
#ifndef C_INSTALL_HOME
# define C_INSTALL_HOME "/cygdrive/c/Program Files/cygchicken/share/chicken"
#endif
I thought it would have been "/cygdrive/c/Program Files/cygchicken"
I have no clue what this is supposed to by on cygwin.
#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. ???
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.
C_INSTALL_BIN_HOME has a sane and straightforward value.
#define C_INSTALL_BIN_HOME "/cygdrive/c/Program Files/cygchicken/bin"
I note, however, that it is defined unconditionally. Is that intended?
I'd say it is. This one isn't overridden, IIRC.
cheers,
felix
--
http://galinha.ucpel.tche.br:8081/blog/blog.ssp