From xemacs-m  Fri Feb 14 19:13:23 1997
Received: from mhost.mri.com (mri-gw.mri.com [149.147.4.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id TAA27658
	for <xemacs-beta@xemacs.org>; Fri, 14 Feb 1997 19:13:23 -0600 (CST)
Received: from mri.com (mailhost.mri.com [192.9.201.130]) by mhost.mri.com (8.8.4/8.7.3) with ESMTP id RAA12099 for <xemacs-beta@xemacs.org>; Fri, 14 Feb 1997 17:13:23 -0800 (PST)
Received: from lungo by mri.com (8.6.12/SMI-4.1-1.16)
        id RAA10967; Fri, 14 Feb 1997 17:13:23 -0800
Received: from lungo by lungo (SMI-8.6) id RAA15257; Fri, 14 Feb 1997 17:13:20 -0800
Message-Id: <199702150113.RAA15257@lungo>
To: xemacs-beta@xemacs.org
Subject: Re: Multiple Architectures 
In-reply-to: Message from Martin Buchholz <mrb@eng.sun.com> 
  of "Fri, 14 Feb 1997 00:46:03 PST." <199702140846.AAA09554@xemacs.eng.sun.com> 
Date: Fri, 14 Feb 1997 17:13:18 -0800
From: Vladimir Ivanovic <Vladimir.Ivanovic@mri.com>

As long as the "run-in-place" functionality is kept, I don't really care
about the particular implementation.

Martin's solution allows arbitrarily named build trees which is better
than run-in-place.

BTW, does Autoconf 2.x support run-in-place?

-- Vladimir

>>>>> Martin Buchholz writes:

>>>>> "Vinnie" == Vinnie Shelton <shelton@icd.teradyne.com> writes:
  Vinnie> I believe Martin removed --run-in-place for 20.0.

  MB> I did, and I still haven't seen a compelling reason to put it back.
  MB> For sure we want the functionality of being able to run with one
  MB> source tree and mulitple binaries using that tree, but using the
  MB> `--run-in-place' option together with `make install' seems highly
  MB> unintuitive - I had never imagined anyone would do that...

  MB> The way I use to have multiple `run-in-place' binaries sharing the
  MB> source tree is like this:

  MB> srcdir=`pwd`/xemacs-20.0
  MB> configure="$srcdir/configure --srcdir=$srcdir"

  MB> mkdir sparc-us   && cd sparc-us   && $configure ... && make
  MB> mkdir sparc-mule && cd sparc-mule && $configure --with-mule ... && make

  MB> Then I can just directly run the binary immediately after it's built.

  MB> Maybe we should document this as the standard solution for XEmacs
  MB> developers and beta testers.

  MB> Of course, I do this so often I have lots of other little timesavers
  MB> to manipulate my build trees.

  MB> Martin

  >>> There's an even easier solution.  From the XEmacs root directory:
  >>> 
  >>> ./configure --run-in-place
  >>> make install
  >>> bin/${CONFIG}/xemacs
  >>> 
  >>> Separate configuration directories are created in bin and lib-src for the
  >>> architecture-dependent executables.  All other files are shared, including
  >>> Emacs-Lisp, man and info files.
  >>> 
  >>> -- Vladimir
  >>> 

