Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!lll-winken!aunro!alberta!brazeau.ucs.ualberta.ca!unixg.ubc.ca!ubc-cs!uw-beaver!ssc-vax!bcsaic!sundry!wsc-sun!cek From: cek@wsc-sun.boeing.com (Conrad Kimball) Newsgroups: comp.windows.x Subject: Re: Multiple architecture's compiled out of a single source tree-- how Message-ID: <1833@wsc-sun.BOEING.COM> Date: 3 Jun 91 17:14:30 GMT References: <9105282237.AA11404@teccb1.TFS> Sender: news@wsc-sun.boeing.com Organization: Boeing Computer Services (ESP), Seattle, WA Lines: 32 Nntp-Posting-Host: zulu In article <9105282237.AA11404@teccb1.TFS>, jason@tfs.COM (Jason P. Venner) writes: |> |> Is anyone compiling multiple architectures out of a single source |> tree? |> |> if so, what are you doing? Depending on what you mean by a single source tree, yes I am doing what you describe. I keep a single tree of the source files (with file permissions set to 444 and directory permissions set to 555, to prevent inadvertent damage). When I wish to build for a particular architecture (currently I build for sun3, sun4, DEC Vaxstation and DECstation architectures) I create a parallel "shadow" tree of links (either symbolic or hard) into the "true" source tree. Then I apply any architecture-specific patches and what-not to the shadow tree and build within the shadow tree, from which I also install the built software as well. When I'm all done and want to clean up, its a simple "rm -fr" on the shadow tree. This works well for me since the source tree is available to all my architectures via NFS. Depending on disk space availability, I often build 2 or more architectures simultaneously. The R4 release materials contain a script to create shadow trees: mit/util/scripts/lndir.sh. I used this for a while, but then I generalized and extended it for general purpose personal use in my other work. -- Conrad Kimball Boeing Computer Services (206) 865-6410 Email: cek@wsc-sun.boeing.com or cek%wsc-sun@atc.boeing.com UUCP: uw-beaver!bcsaic!wsc-sun!cek