>* You can't clean a project with spaces in the name. The arguments to
>rm aren't quoted. Cleaning appears to succeed (no error), but the
>binaries are still there.
>
>* If you build a project then rename a file, the linker is given both
>the old .o file and the new one. It fails with a duplicate symbol
>error.
>
>* Cosmetic: The build console doesn't handle spaces gracefully; it
>prints out things like "gcc -oHello World.exe src/Hello World.o", but
>behind the scenes it runs the right command.
>
>* Cygwin-specific: The internal builder doesn't work "out of the box"
>because Cygwin uses symlinks for /usr/bin/gcc. If you have Cygwin
>make in your path and use the external builder, this works fine.
>
>So, before we chase down these bugs (at least, those that matter to
>us), are folks using the internal builder in products? Does it work?
We are using the internal builder for our products. We have a common code base for different plattforms (projects). We don't have spaces in the project names, but it's true, the clean command doesn't removes the build output reliable. But
this not a real problem (maybe confusing) because it can be done external.
For use it's sometimes erroneus, when we a add new sources to the common code base, than we have to exclude this manually in some projects to prevent the compilation of the added sources. It would be fine, if new sources should be added
explicit to the project, not excluded explicit.
We have our own tool chain.
--Harald
