Re: Mono Develop C projects generate bad calls to gcc?

On 11/20/07, Chris Hamons < chris.hamonsgmail.com">chris.hamonsgmail.com> wrote:

I think I've found a bug in the call that monodevelop makes to gcc to
build C shared libraries. I'm having trouble getting a hold of a copy
of mono develop newer than .16, so forgive me if this is already
known/been fixed. It seems that monodevelop isn't wrapping the
project's directory in quotes, so directories with spaces are
mis-interpreted.

This Works Fine:

using: gcc &nbsp;-MMD
/home/donblas/Programming/HelloWorld/MonoCLibrary/mono- curses.c -g
-fPIC -O0 -DDEBUG -DMONODEVELOP
-I/home/donblas/Programming/HelloWorld/MonoCLibrary/.prec -c -o
/home/donblas/Programming/HelloWorld/MonoCLibrary/mono-curses.o

However, this doesn't:

using: gcc &nbsp;-MMD /home/donblas/Programming/HelloWorld/Mono C
Library/mono-curses.c -g -fPIC -O0 -DDEBUG -DMONODEVELOP
-I/home/donblas/Programming/HelloWorld/Mono C Library/.prec -c -o
/home/donblas/Programming/HelloWorld/Mono C Library/mono- curses.o
gcc: /home/donblas/Programming/HelloWorld/Mono: No such file or directory
gcc: C: No such file or directory
gcc: Library/mono-curses.c: No such file or directory
gcc: C: No such file or directory
gcc: Library/.prec: No such file or directory
gcc: C: No such file or directory
gcc: Library/mono-curses.o: No such file or directory
gcc: no input files



Is this a known/fixed issue, or should I file a bug report somewhere?

Thanks,
--Chris
_______________________________________________