Switching between compilers
Posted: Sat Oct 10, 2020 9:43 am
I have GCC 8 and GCC 10 installed, my path environment variable containing both. Lately I did my compilations using GCC 10 but yesterday I switched (by promoting the path to GCC 8 in the path variable) to GCC 8 because that produces faster executables.
The surprise came when I wanted to run an engine (Halogen 7) prviously compiled using GCC 10, and I got the error message 'the access point to the process cannot be found in the DLL' (this is an approximate translation, I use Hungarian Windows). I tried another engine compiled using GCC 10 and the result was the same. I switched back to GCC 10 (again via the path variable) and the errors went away.
So it seems to me that the engines try to use a DLL which can be found in the GCC 10 installation but not in the GCC 8 one. Is that comprehensible?
The strange thing is that the opposite seems to be not true: if I compile Halogen 7 using GCC 8 then switch paths, I don't get an error message.
I'd be grateful if someone could comment on this issue.
The surprise came when I wanted to run an engine (Halogen 7) prviously compiled using GCC 10, and I got the error message 'the access point to the process cannot be found in the DLL' (this is an approximate translation, I use Hungarian Windows). I tried another engine compiled using GCC 10 and the result was the same. I switched back to GCC 10 (again via the path variable) and the errors went away.
So it seems to me that the engines try to use a DLL which can be found in the GCC 10 installation but not in the GCC 8 one. Is that comprehensible?
The strange thing is that the opposite seems to be not true: if I compile Halogen 7 using GCC 8 then switch paths, I don't get an error message.
I'd be grateful if someone could comment on this issue.