Steve Downey wrote:
> then, from in the bld-gcc-2.95.2, you run ../gcc-2.95.2/configure, and the
> build environment is created, while the source environment remains pristine.
> This is imperative if you're building for several environments out of the
> same source tree. In which case you might have
> gcc
> gcc-2.95.2
> bld-gcc-2.95.2-i686-linux
> bld-gcc-2.95.2-i386-linux
> bld-gcc-2.95.2-sparc-solaris6
> bld-gcc-2.95.2-sparc-solaris8
> bld-gcc-2.95.2-cygwin-cross-linux
Hmm ... that's true. I guess the reason that has never bothered me is because I
am explicitly telling configure where the source directory is and am executing
this from my chosen build environment location, as opposed to the compilation
command implicitly traveling up my hierarchy and creating the build there.
Then again, I agree with Costin and Remy about polluting the source tree. I
dunno ... I guess it's a matter of which personal taste as to which Ant
approach one finds more aesthetically unpleasing. I personally find the new
approach a little more pleasing, but I can certainly see Costin's point too and
am willing to go along with whatever is decided.
Regards,
Christopher
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
