On Mon, Jul 21, 2008 at 03:41:37PM -0500, Robert Gordon wrote: > > In effect you are asking for the ON build process to > fabricate the built/derived files outside of the > "source namespace" .. Much like the OSF build > process (and others) can do.. For example: > > the following has the source files: > usr/src/uts > > and the following has the built/derived files per > arch: > > build/i386/usr/src/uts > build/sparc/usr/src/uts > > it this correct ?
Sort of (that's a refinement of what I was suggesting). In my model the build spaces were clones of the development repository that are kept in sync with any changes in the dev. repository. Thus no changes are needed in the build environment. BTW, I realize now that using rsync --delete won't work to sync the build space with the development workspace since that will delete all build output in the build space. I guess I could use hg commit in the dev. repository and then pull the changes into the build space or if I don't want to commit, I could make a script that uses hg status output and just rsync those changes and not recurse down all the dirs. Of course it would be nice if all build output were in a path separate from the source, then rsync'ing would be easy (and perhaps unnecessary). -- Will Fiveash Sun Microsystems Inc. http://opensolaris.org/os/project/kerberos/
