Re: [Chicken-users] CMake testing

[Graham Fawcett]

On 10/24/05, felix winkelmann <address@hidden> wrote:
> On 10/21/05, Graham Fawcett <address@hidden> wrote:
> > Running `cmake -G "NMake Makefiles"` didn't Just Work. I used
> > cmakesetup.exe, which is a GUI for writing a configuration cache.
> > Before running this, I had to add the MSVC toolchain to my PATH. I
> > don't normally have them on PATH; and without them, cmakesetup
> > wouldn't work properly. IOW, you cannot just run cmakesetup from the
> > Start..Programs menu unless you have your tools on the PATH. Note that
> > `cmake -G "NMake Makefiles"` did not work even when my tools were on
> > the path.
> Having the tools in your path should be mandatory. Without them,
> most of the chicken-tools will fail anyway.

Eminently obvious, upon reflection. :-)

I'm trying again, after setting up my path/environment correctly, and
`cmake -G "NMake Makefiles" && nmake` now appears to work as
advertised. I must have messed something up during my Friday test.

> > Testing the built binaries: csi and csc worked fine. Chicken_setup
> > worked, but this is MSVC-land, and the lack of gzip et. al. means that
> > chicken_setup usually fails to build anything. (These GNU-toolchain
> > dependencies are something I would *love* to see fixed for the MSVC
> > platform, if I had my two cents, or enough time to tackle it!).
>
> You could try these:
> http://unxutils.sourceforge.net/

Yes, I've used those before; MSYS also provides decent copies of the
tools. Certainly, using chicken-setup on Windows is frustrating at
times on Windows, and is inconsistent across the msvc/mingw/cygwin
platforms. I know not every egg is going to build on msvc, but key
ones like http would be nice to have "out of the box". But I'll try to
be a good citizen and provide patches rather than complaints next
time. :-)

Graham