This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: How to flatten the build directory structure
- To: "M. R. Brown" <marcusb at csd dot uwm dot edu>
- Subject: Re: How to flatten the build directory structure
- From: Mumit Khan <khan at nanotech dot wisc dot edu>
- Date: Fri, 29 Oct 1999 12:25:43 -0500
- cc: crossgcc at sourceware dot cygnus dot com, cygwin at sourceware dot cygnus dot com
"M. R. Brown" <marcusb@csd.uwm.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@sourceware.cygnus.com