>
> Sorry, I can't follow this at all: vcbuild.bat doesn't use CHICKEN_HOME,
> also makefile.vc doesn't. For Windows platforms built via makefile.vc,
> csc.scm
> uses CHICKEN_HOME, as this seems to be the only decent way of
> specifiying an
> installation destination.
What I mean is, csc built from vcbuild.bat or makefile.vc relies on a
hardwired behavior for CHICKEN_HOME. ./configure builds and
installations do not appear to depend on CHICKEN_HOME for anything,
either at build time or runtime, although I could be mistaken.