Post

Replies

Boosts

Views

Activity

Reply to Error: apple/apple/game-porting-toolkit 1.1 did not build
As of now, installation of Apple's game-porting-toolkit is again broken, regardless of CLT/Xcode versions used. The compilation fails with: /private/tmp/game-porting-toolkit-20240603-70423-h1cgr2/wine/dlls/msvcrt20/msvcrt20.c: In function 'MSVCRT20__getmainargs': /private/tmp/game-porting-toolkit-20240603-70423-h1cgr2/wine/dlls/msvcrt20/msvcrt20.c:35:5: error: implicit declaration of function '__getmainargs' [-Wimplicit-function-declaration] 35 | __getmainargs( argc, argv, envp, expand_wildcards, &new_mode ); | ^~~~~~~~~~~~~ /private/tmp/game-porting-toolkit-20240603-70423-h1cgr2/wine/dlls/msvcrt20/msvcrt20.c: In function 'MSVCRT20__wgetmainargs': /private/tmp/game-porting-toolkit-20240603-70423-h1cgr2/wine/dlls/msvcrt20/msvcrt20.c:46:5: error: implicit declaration of function '__wgetmainargs'; did you mean 'MSVCRT20__wgetmainargs'? [-Wimplicit-function-declaration] 46 | __wgetmainargs( argc, wargv, wenvp, expand_wildcards, &new_mode ); | ^~~~~~~~~~~~~~ | MSVCRT20__wgetmainargs make: *** [dlls/msvcrt20/msvcrt20.cross.o] Error 1 make: *** Waiting for unfinished jobs.... This requires fixing by Apple.
Jun ’24
Reply to Error: apple/apple/game-porting-toolkit 1.1 did not build
Installation of what is now called "Evaluation environment for Windows games 2.0 beta" (also included in Game Porting Toolkit 2 beta) is still broken, with exactly the same problems stated above. Somehow not surprising, since the homebrew formula to build the toolkit has not been updated. Workaround is to use pre-built binaries that have been built during the 'golden age', when the toolkit still did built: https://github.com/Gcenx/game-porting-toolkit/releases
Jun ’24
Reply to Error: apple/apple/game-porting-toolkit 1.1 did not build
Security @Apple, please flag the current Apple Homebrew formula used in the installation of the Game Porting Toolkit at https://github.com/apple/homebrew-apple/blob/main/Formula/game-porting-toolkit.rb as security risk, since it installs outdated network, encryption and security components on user's machines (e.g. openssl 1.1). It is obvious to even a cursory reviewer that this script is completely un-salvageable, and seems to be in that state for quite some time, probably for reasons beyond the scope of bug reports. However, now, This requires a complete rewrite with up-to-date dependencies and should not be part of a 2.0 release in it's current state, even at a beta stage.
Jun ’24