Can you use a source dir/build dir style development to get around this?
autoconf and automake, for all their warts, do this very well.
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
Zack Weinberg [EMAIL PROTECTED] wrote:
GCC can't be built except in a separated build directory setup, and
the *other* fun part is making sure that the normal build process
never writes to the source directory (people actually use unwritable
source directories with GCC builds)
Not a bad idea,
mtn.EXE: switching to branch com.fortunet.altanik
mtn.EXE: warning: cannot drop non-empty directory
'src/fut/flashdrive/flashdrivetester'
mtn.EXE: misuse: 1 workspace conflicts
this is caused by creating a project with sources and building it,
which created objects and sub-directories in the
