This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Crossed-Native Builds, Toolchain Relocation and MinGW
Dave Murphy wrote:
> davem@NEUROMANCER /e
> $ gcc /usr/local/test/test.c -o /usr/local/test/test.exe
>
> davem@NEUROMANCER /e
> $ /usr/local/test/test.exe
> E:\msys\local\test\test.exe
> davem@NEUROMANCER /e
> $
>
> As you can see the paths are translated by the shell before being passed
> to windows executables.
No, you've actually just proved Ross' point correct. Gcc being a native
win32 app gets the actual win32 path, not any kind of posix path that
might be adjusted for MSYS mounts. If you took the above testcase and
mounted /usr/local/test as /foobar and then ran /foobar/test.exe you
would get identical output, E:\msys\local\test\test.exe, because that is
the actual path to the binary. In other words, native win32 binaries
are completely oblivious to any mounts created in MSYS, so using mounts
is not a viable workaround since only MSYS apps will see a distinction.
Brian