PyCForge 1.3.9 — Windows compiler checks

Use the compiler families installed on your laptop. Compiler installations
remain separate from PyCForge; no additional Python dependency is required.

Preparation

For MSVC, install the Visual Studio C++ build tools and a Windows SDK, then
launch PyCForge from an x64 Developer PowerShell. MSVC 2019 16.8 or later is
required. Clang-cl also needs the configured Visual Studio/SDK environment.
For MinGW-w64, use its 64-bit GCC driver and matching runtime libraries.
For PCFC11, retain its include directory beside the executable and select
its GCC-compatible assembler/linker when it is not already on PATH.

Checks

1. Open training_corpus/cases/inheritance-super/main.py from this project.
   Select Runtime conversion and transpile. Open Transpile > Compile C.

2. Select one installed compiler family and its executable. Use Compiler
   default unless deliberately selecting a specific target. For PCFC11,
   select Windows x64 and the matching MinGW-w64 assembler/linker.

3. Select Executable, main.main, O0, and an output path in a temporary folder.
   A folder containing spaces is useful. Click Compile. The window should
   remain responsive and report Build succeeded.

4. Run the resulting executable yourself from PowerShell. It should print:
   row 12 132
   27 17
   126 row
   The final process exit code should be zero.

5. Repeat at the other optimization levels offered by the selected family.
   The printed results and exit code should remain the same.

6. Select Object file. Compilation should succeed without selecting an entry
   function or linking an executable. MSVC/Clang-cl suggest .obj; GNU-style
   drivers suggest .o. An explicitly chosen output filename is preserved.

7. Switch between compiler families, then close and reopen the dialog. Each
   family's compiler path, target and optimization choice should be retained.
   An explicit output path should survive switching profiles.

8. Select a missing compiler path or an incompatible target and build again.
   The dialog should explain the failure and preserve an existing output.
   On a longer build, Cancel Build should stop it and preserve that output.

9. Repeat the executable check with each other installed family. Transpilation
   itself should still work when no compiler is installed.

Feedback

Use Copy Report after a successful build and after any failure. Include the
selected family, compiler version, target, optimization level, whether the
program ran, its output and its exit code. For Unicode file checks, use the
existing Runtime Help file-processing examples with a non-ASCII filename.

These are native Windows checks. The release's Linux GCC and command-contract
results do not replace them. Compilation in PyCForge never launches the program.
