Re: [Mingw-cross-env-list] build tools installed in $(PREFIX)/$(TARGET)

[John W. Eaton]

On 02/05/2014 03:45 PM, Timothy Gu wrote:
> On Feb 5, 2014 12:03 PM, "John W. Eaton" <address@hidden
> <mailto:address@hidden>> wrote:
>  >
>  > In a fresh clone of MXE, after executing
>  >
>  >   make gcc
>  >
>  > the directory usr/i686-pc-mingw32/bin (i.e., $(PREFIX)/$(TARGET)/bin)
>  > contains the following files:
>  >
>  >   ar  c++      g++  gfortran  ld.bfd  objcopy  ranlib
>  >   as  dlltool  gcc  ld      nm      objdump  strip
>  >
>  > and they are all "ELF 64-bit LSB executable, x86-64 ..." files.
>  >
>  > Is this intentional?  I was expecting the $(PREFIX)/$(TARGET)
>  > directory to contain only cross-compiled files that are intended to
>  > run on the $(TARGET) system.
>
> Yes. We copied these files to $(PREFIX)/bin to avoid clashing with
> native GCC, ld, and others. Users are NOT encouraged to add
> $(PREFIX)/$(TARGET)/bin to their PATH's.

I guess I'm a bit confused about why they should be installed in 
$(PREFIX)/$(TARGET)/bin if users are not expected to add that directory 
to their PATH and Makefiles should be using names like $(TARGET)-gcc for 
cross compiler tools.

What I'd like to be able to do is cross compile tools like gcc, bison, 
etc. and install those tools in $(PREFIX)/$(TARGET)/bin along with all 
the other packages that I'm cross compiling for Windows.  That seems to 
conflict with putting the cross compiler binaries themselves in 
$(PREFIX)/$(TARGET)/bin.

jwe