[Chicken-users] incorrect csc.scm.in assumptions?

[Brandon J. Van Every]

I notice that csc.scm.in has things like %CHICKEN_HOME% in it that are 
supposed to be substituted.  Makefile.am performs these substitutions.  
Do I understand correctly that %SOMETHING% syntax is just there for 
sed's benefit in Makefile.am, and does not represent some kind of 
special Chicken syntax to pull values out of the environment or some 
such?  If so, then when those substitutions are not performed, as in the 
case of the current CMake build, the values left in there are spurious.  
I haven't tested csc.exe at all in the past, so it's quite possible that 
the problem has always been there and I've never noticed it.  That's an 
argument for a testing suite, incidentally.  Just making sure the 
Chicken banner comes up isn't really testing.

It also strikes me as wholly incorrect to assume that the CHICKEN_HOME 
at build time is going to be the same as CHICKEN_HOME 
post-installation.  I'm not in the habit of overwriting my old Chicken 
installation directories.  Sometimes I just keep the old build in an old 
directory, change CHICKEN_HOME to point at a new one, and then off we 
go.  Especially since I'm verifying bootstraps from old Chickens and 
building for 3 different platforms on Windows.


Cheers,
Brandon Van Every