Open gm-bug-reporter[bot] opened 1 month ago
I tried helping this individual on the GM subreddit; the issue is related to the v142 MSVC build tools having a link error in newer versions of visual studio, as the thing unable to be linked is the _guard_check_icall_$fo$
symbol which is part of the Control Flow Guard feature for win32 PE files. The fix is for them to either install the MSVC v143 build tools (99.99% sure these work as some of the set environment variables show that the msbuild version is 14.38.33130, which are the v143 tools) as this typically seems to be related to trying to use a newer SDK than the version of msbuild being used supports. The other option is to install a version of the windows SDK which is compatible with the v142 tools so that they have the proper version of libucrt.lib
Installing V143 cause a lot of other problems so it is not the solution, i have installed VS 2022 with v143 and GMS is still looking for v142. I can correctly build for all platforms including consoles with v142 and the problem is happening from a month or 2 not in the past months where i was able to build with VS2019 and v142 without any issues. The problem is from the GMS side not from the developer i wrote to Microsoft and they said there is something broke in their wait to create the project and the variables. I don't know what they changed.
I only use VS2019 and not changed since a while. I have tried to install 2022 and i made a roll back to 2019 because nothing is changed and i'm still not able to build in YYC for Windows.
Please fix it from your side because is not our fault.
Description
Whenever I try running or exporting a project, even a blank one, while using the YYC compiler, I receive an LNK error for an unresolved external symbol. The full error is attached. If it's relevant, my computer is in Brazilian Portuguese.
Steps To Reproduce
Windows user in Brazilian Portuguese. Install VS Community 2022. Run game using YYC.
Which version of GameMaker are you reporting this issue for?
IDE v2024.6.2.162 Runtime v2024.6.1.208
Which operating system(s) are you seeing the problem on?
Windows 10.0.19045.0
Which platform(s) are you seeing the problem on?
Windows
496103d8-7a72-4a8a-af1b-6eae411d04a2