Re: [Mingw-cross-env-list] Tutorial buglet?

[William R]

Hello,

The general idea is to have prefixed tools in usr/bin, for example 
i686-w64-mingw32-gcc.
Thus, you can add this path permanently, as it is very unlikely that 
i686-w64-mingw32-gcc conflicts with an other program with the same name 
elsewhere. Furthermore, it is clear that i686-w64-mingw32-gcc is gcc for 
the i686-w64-mingw32 toolchain.

However, if you add usr/i686-w64-mingw32/bin to your path, you are most 
likely to make conflicts between the "normal" gcc and the one from the 
toolchain (as gcc is also in usr/i686-w64-mingw32/bin).

The "good" way of doing is to use or adapt Makefiles to :
- use explicitely usr/i686-w64-mingw32/bin/freetype-config
- or, temporarily in some make commands, export i686-w64-mingw32/bin path
- or pass some additional option to freetype-config so that it can take 
into account cross i686-w64-mingw32 options
- or, copy freetype-config in usr/bin/i686-w64-mingw32-freetype-config, 
and refer to it. Note that autotools and configure.ac scripts often use 
commands that will first try to use i686-w64-mingw32-freetype-config, if 
available, and then freetype-config otherwise, it you tell ./configure 
that you are cross building.

Hope this helps!
If you don't understand, maybe it would be interesting to give link to 
your project or to your makefile?

B. regards,
William



On 08/06/2013 09:37 PM, Werner LEMBERG wrote:
> In step 4 of
>
>    http://mxe.cc/#tutorial
>
> you write
>
>    Edit your .bashrc script in order to change $PATH:
>
>      export PATH=/where MXE is installed/usr/bin:$PATH
>
> I think this is insufficient.  Assuming that the target is
> `i686-pc-mingw32', it should rather be
>
>      export PATH=\
>      /where MXE is installed/usr/bin\
>      :/where MXE is installed/usr/i686-pc-mingw32/bin\
>      :$PATH
>
> Otherwise configure and make scripts which try to access other
> configuration scripts like `freetype-config' fail.
>
> Since this situation is quite frequent and easy to miss (because many
> platforms have `/usr/bin/freetype-config' and friends), I suggest to
> mention this explicitly.
>
>
>      Werner