On 6/20/2015 8:25 PM, Edward Diener wrote: > Thanks ! I will look at your toolchains. I assume if all paths are > relative there is no need for any installation to go into or have a > symbolic link from c:\mingw.
Correct. > Any timeframe for a gcc 5.1 release ? I noticed the latest mingw-64 > install now has gcc-5.1, but it has the same hardcoded to c:\mingw > limitation which my OP is about. There may or may not be a TDM-GCC 5.1 release (5.1 being the first in the GCC 5 series); right now I try to track the second minor release in every major series, so expect TDM-GCC 5.2 at some point in the next month or two after the upstream 5.2 release. My experience in the past with other GCC toolchains was that they tended to have enough usable relative search paths that you could still move them around wherever you want, as long as you didn't put *anything* at the hardcoded locations (/mingw or the like). That said, I haven't tried this with a MinGW-w64-based toolchain other than my own in a while. -John E. / TDM ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
