Re: [Mingw-users] Mingw32 installation problem

[Ross S. <ro...@ih...>]

Paul Garceau wrote:
> 
>         GCC_EXEC_PREFIX is a predefined Env Var with, afaik, "all" GCC based
> compilers.  It tells whichever shell you are using (cmd.exe or
> command.exe, bash, etc.) where c/c++ executables (c++.exe/gcc.exe) need
> to look (for cygwin that is a mount list which includes the necessary
> headers, for mingw that is a specific set of paths, including the
> headers) when they (gcc/g++) are attempting to build (Compile And Link)
> an application/program.
> 
>         If you are using Mingw and Cygwin as Separate Development Tool Sets.
> (Which contrary to what appears to be popular belief, is in fact,
> true)...if you do not inform your mingw and cygwin bat files where
> their gcc_exec_prefix (a pointer to the compiler specs file) should be,
> they will assume the installation default...the default in every case,
> unless you specifically state otherwise, will always point to the last
> valid specs file that gcc should be using.

I've been trying to get Cygwin and Mingw both working on the same
system. I thought all I needed was to put mingw/bin first in my $PATH
(via a script wrapper for make), but that didn't seem to work properly.
From what little I understood of the above, am I right in thinking I
need to set $GCC_EXEC_PREFIX as well? What should it be set to?

-- 
Ross Smith <ro...@ih...> The Internet Group, Auckland, New Zealand
========================================================================
        "Hungarian notation is the tactical nuclear weapon of
         source code obfuscation techniques." -- Roedy Green