I’m so close (but no cigar) to having a Windows pipeline with all 6 variants of builds, but there’s one tiny (or HUGE) problem left.
It’s the GitLab runners that runs out of memory for the 10MB (800k+ lines) file
msbuild. The whole project works fine when I compile it on my 12G RAM laptop. The Shared Windows runners have only 7.5 G.
The error message is:
fatal error C1060: compiler is out of heap space.
I think it’s the difference in available memory that is the problem but an alternative explanation is that it is this problem that was reported fixed Aug 12, 2019. I have Visual Studio Build Tools version
14.26.28801 while the GitLab runner has
14.24.28314. I haven’t been able to find release notes for the build tools so I can’t say if the GitLab runners have this fix or not and I don’t know how to install the GitLab version on my computer.
I’ve made an experimental version of
lab_gamut.c, reducing it to just a few lines and GitLab had no problems with it, so I know it’s the size of the file (or rather the size of the data I guess) that is the problem.
Here’s the pipeline with all build jobs, but for some reason it doesn’t show the detailed error message, just
Done Building Project "C:\GitLab-Runner\builds\magjac\graphviz\lib\edgepaint\lab_gamut.vcxproj" (default targets) -- FAILED..
Here is a job that builds
lab_gamut only that shows the error message.
I’ve read Fatal Error C1060, but got no help from it.
Any help would be greatly appreciated: to pinpoint the problem better, to avoid it or ways to rewrite the file that would consume less memory. It looks like a generated file. Maybe it would be possible to generate it at runtime if we knew how. Perhaps @erg knows?