Re: [Chicken-users] Msys install and \

2006-12-14 Thread Matthew David Parker
Alright I got it working in msys. I had to install it to c:\Program Files\Chicken using CMake and then make sure that it was in my msys PATH, which it was by default, and then I deleted the previous ones I had installed in /local/bin. Now it runs well, but unfortunately I think MSYS pipes stdout

Re: [Chicken-users] Msys install and \

2006-12-14 Thread Brandon J. Van Every
Matthew David Parker wrote: Alright I got it working in msys. I had to install it to c:\Program Files\Chicken using CMake and then make sure that it was in my msys PATH, which it was by default, and then I deleted the previous ones I had installed in /local/bin. Now it runs well, but

Re: [Chicken-users] Msys install and \

2006-12-11 Thread Matthew David Parker
Well, I actually just wrote that wrong, it's installed to /usr/local/bin The reason why I don't want it in C:\program files\chicken is because I have everything else I need for my project installed in msys, such as SDL and all its varients. The autoconf setup in msys works very well, except

[Chicken-users] Msys install and \

2006-12-09 Thread Matthew David Parker
I'm trying to install chicken-2.5 on windows in MSYS. I tried using cmakeSetup to make MSYS makefiles, and then I compiled them from within MSYS by typing make and make install. I had it install to /bin within msys. For some reason, the binaries don't seem to read any command-line arguments.

Re: [Chicken-users] Msys install and \

2006-12-09 Thread Brandon J. Van Every
Matthew David Parker wrote: I'm trying to install chicken-2.5 on windows in MSYS. I tried using cmakeSetup to make MSYS makefiles, and then I compiled them from within MSYS by typing make and make install. I had it install to /bin within msys. For some reason, the binaries don't seem to read