Re: [Chicken-users] chicken & MinGW - path issue and work-around

[Felix]

> In this environment, things like "/usr/local" work normally (from a
> Unix point of view). Most of the build process worked flawlessly using
> Unix style commands and paths.
> 
> MinGW and MSYS translate things in the background. The one error
> appears to be caused by a failure to use this translation
> process. When chicken- install tried to access the library directory,
> instead of going through this translation
> 
>   /usr/local/lib/chicken/6  ->  C:\MinGW\msys\1.0\local\lib\chicken\6
> 
> it tried to access this
> 
>   /usr/local/lib/chicken/6
> 
> which Windows interpreted as
> 
>   C:\usr\local\lib\chicken\6
> 
> This is why the work-around works.

The translation only takes place through the MSYS shell, file-system operations
inside chicken, which end up in win32 operating-system functions are not
translated. So the PREFIX given at build-time must be a valid Windows path.


cheers,
felix