for future reference, the frozen modules Windows build is in PCbuild/_freeze_module.vcxproj

@zooba I made an attempt in gh-113303
it successfully generated the frozen modules (headers and deepfreeze.c) in $(IntDir), but I wasn't able to get the rest of the build to find these. I think my problem is that the generated files are written to the $(IntDir) of the _freeze_module project, which is not the same thing as the $(IntDir) of the pythoncore project. before falling into a rabbit hole about how to get one vcxproj consuming the intermediate outputs of another vcxproj, I wanted to pause and see if this is even the right direction, and whether there are other examples in the Windows build that I can borrow from.

Make sure you've got the latest from main, and then look for GeneratedPyConfigDir in pyproject.props. You'll want to do something like that for FrozenModulesDir and then reference that variable instead (it can keep the extra subdirectories so that #include works the same, but use the new property throughout the projcet files).

There's also a script to update the project files with the properties you've edited, so make sure you find and update that first and then regenerate the files. It's probably in Tools somewhere, and might be referenced from PCbuild/regen.targets, which would mean you can PCbuild/build.bat --regen to run it.