Дмитрий wrote: > [...] > ""\usr\local\bin\csc"" -feature compiling-extension -setup-mode -S -O3 > -d0 -feature standalone chicken-spock.scm -o chicken-spock > "chicken-spock" -library-path spock -optimize -library -o library.js > cat config.js runtime.js library.js > spock/spock-runtime.js > ""\usr\local\bin\csc"" -feature compiling-extension -setup-mode -S -O3 > -d0 -feature standalone chicken-spock.scm -o chicken-spock > [...]
Hello, this output indicates that the Spock compiler is actually built and runs without crashing but the build system still tries to recompile the executable after it has already been built and eventually gives up. My guess is that this has something to do with Windows file naming conventions: Probably the generated executable is named "chicken-spock.exe" but the build system expects to find a target called "chicken-spock" without any extension, which simply doesn't appear no matter how often the executable is recompiled ;-) This can likely be worked around manually without too much trouble. Ciao, Thomas -- When C++ is your hammer, every problem looks like your thumb. _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
