Using Bison

[mcesare]

seems that "out of the box" the build process knows about bison.
Working on windows vista machine.
I named a file New.y and seems to run bison on that file.

then I get these errors....

||=== Build: Debug in New (compiler: GNU GCC Compiler) ===|
 cannot open `Files\GnuWin32\share\bison'||No such file or directory|
\Program'||No such file or directory|
 cannot open `Files\GnuWin32\share\bison\m4sugar\m4sugar.m4'||No such file or directory|
\Program'||No such file or directory|
 cannot open `Files\GnuWin32\share\bison\bison.m4'||No such file or directory|
\Program'||No such file or directory|
 cannot open `Files\GnuWin32\share\bison\c-skel.m4'||No such file or directory|
\Users\Mark\Desktop\Test\New\New.parser.cc||No such file or directory|
||=== Build failed: 8 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|


sound odd but it almost looks like the space on "Programs Files" is causing an isses

[BlueHazzard]

sound odd but it almost looks like the space on "Programs Files" is causing an isses

this is normal for gnu programs. I personally also think that spaces make things more difficult. The solution is simple: don't use spaces in paths.