Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Fri, 29 Oct 1999 09:25:58 -0500 (CDT)
From: "M. R. Brown" <marcusb AT csd DOT uwm DOT edu>
To: crossgcc AT sourceware DOT cygnus DOT com, cygwin AT sourceware DOT cygnus DOT com
Subject: How to flatten the build directory structure
Message-ID: <Pine.OSF.3.96.991029091302.12295A-100000@alpha3.csd.uwm.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Sorry for the crosspost, but this kinda relates to both lists...

I'm in the process of building Canadian crosses (gcc-2.95, binutils-2.9.1)
under cygwin, to be hosted under djgpp, mingw32, and linux (glibc5).  When
I'm ready to distribute these tools, I would like to "flatten" the
directory structure so that all includes and libraries are in a single
"root" directory: 

I would like to turn:
/psxlib-0.1
|
--bin
|
--target
  |
  --bin
  |
  --include
  |
  --lib
|
--lib
  |
  --gcc-lib

into:
/psxlib-0.1
|
--bin
|
--lib
|
--include

This appears to be something that has to be ironed out before the build
process, but I could be wrong.  The ideas is to eliminate "target/", but
doesn't gcc spawn executables there?  And the linker finds linker scripts
under "target/lib/ldscripts"...

Has anyone ever done this _without_ setting GCC_EXEC_PREFIX, C_INCLUDE,
etc.  Could it be done by modifying specs?

Marcus


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com