From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8603 invoked by alias); 27 Feb 2002 19:14:03 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 8507 invoked from network); 27 Feb 2002 19:13:56 -0000 Received: from unknown (HELO bothner.com) (216.102.199.253) by sources.redhat.com with SMTP; 27 Feb 2002 19:13:56 -0000 Received: from bothner.com (eureka.bothner.com [192.168.1.9]) by bothner.com (8.11.6/8.11.6) with ESMTP id g1RJIvp12253; Wed, 27 Feb 2002 11:18:57 -0800 Message-ID: <3C7D3014.2040502@bothner.com> Date: Wed, 27 Feb 2002 11:23:00 -0000 From: Per Bothner User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8+) Gecko/20020215 X-Accept-Language: en-us MIME-Version: 1.0 To: Mark Mitchell CC: gcc@gcc.gnu.org Subject: Re: Installation proposal References: <11560000.1014832588@warlock.codesourcery.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg01685.txt.bz2 Mark Mitchell wrote: > What's good about this? 5. The Makefiles for builting libraries can be simpler: Just use "install/bin/g++", not "g++ -B... -nostdinc++ -I..." (This is a variant of your point 1.) 6. Easier to "run in place" without installing. I.e. don't need to 'make install' - just add the $builddir/install to the $PATH. (Emacs already allows this.) 7. Possibly cleaner 'make bootstrap' - use a different install directory for each stage. > We can just have the top-level configure set the prefix for all of the > child configures to "install". Then, have the top-level "make" and > "make bootstrap" do what they do now, plus "make install" in all of > the children. Then, have the top-level "make install" do the copying > step. Sounds like one day's work to get it working, and another one > to debug the fallout. One disadvantage is that this would require more disk space while building, since you need teh addition space for the install directory. But this problem can be incrementally reduced as you gradually fix sub-directories to leave files directly in the install directory. I suggest chaninging the name from 'install' to 'build'. It isn't the real install directory. Ideally, for sub-directories that have been converted to this convention, you still have 'make install', but it just copies from the 'build' directory to $prefix. This is not critical, but it might be useful if one wanted to install files in a sub-directory only. -- --Per Bothner per@bothner.com http://www.bothner.com/per/