Re: [Chicken-users] Cmake broken again: paths are not quoted

[Brandon J. Van Every]

John Cowan wrote:
> The pathnames in chicken-paths.h are not in quotation marks, so compiling
> eval.c (and other things, probably) produces fatal errors when gcc gets
> all confused.
>   

Ah, thanks for this testing.  It behaves differently because you're 
building with Cygwin, which has a Unix style path environment, not 
Windows native.  I've been fixing Windows native paths and have 
neglected the Unix path.  A simple application of quotes should fix it.  
I will have a patch in Darcs shortly; I will e-mail then.

> This has got to be fixed if CMake is ever going to be the standard build
> process as opposed to just the Windows build process.
>   

Look, please have a little more patience with the CMake build.  I don't 
know if you've noticed, but I've made progress on every issue you've 
brought up within a timeframe of like 2 days.  Yes, not a final 
solution, and that bugs me to no end as well, which is why I'm cranking 
out the code.  I need to ship this thing solid pronto so I can stick it 
on my resume and re-enter the computer industry after an 8 year 
absence.  I've got no $ coming in so the job's gotta happen quick.  In 
short, every effort is being applied.  Remember that this is open 
source, and I'm not paid a dime for it.  Your testing is valuable, I do 
consider it a contribution to the cause.  Please realize your 
frustration is pretty much required for progress.  It's not like I've 
announced a 100% rock solid build to the world; that's the goal I'm 
working towards, and I believe nearly in sight of.  It's not like I have 
the manpower and testing resources to shake out all test coverages.  
Sure I'd like an automated nightly build that tests every permutation.  
That takes time to develop; you up to it?


Cheers,
Brandon Van Every