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
Message-Id: <199910291725.MAA18568@pluto.xraylith.wisc.edu>
To: "M. R. Brown" <marcusb AT csd DOT uwm DOT edu>
cc: crossgcc AT sourceware DOT cygnus DOT com, cygwin AT sourceware DOT cygnus DOT com
Subject: Re: How to flatten the build directory structure 
In-Reply-To: Your message of "Fri, 29 Oct 1999 09:25:58 CDT."
             <Pine DOT OSF DOT 3 DOT 96 DOT 991029091302 DOT 12295A-100000 AT alpha3 DOT csd DOT uwm DOT edu> 
Date: Fri, 29 Oct 1999 12:25:43 -0500
From: Mumit Khan <khan AT thor DOT xraylith DOT wisc DOT edu>

"M. R. Brown" <marcusb AT csd DOT uwm DOT edu> writes:
> 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?
> 

GCC deals with includes and libraries a bit differently if they're in the
``target'' directory, and you may run into trouble if you remove them. It
can be done, but I'm not sure I understand your motivation here.

Regards,
Mumit


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