Fix #11631 - Latest release failed on Windows arm64 and on mac

[jmarrec]

Pull request overview

• Fix Latest release failed on Windows arm64 and on mac #11631

Description of the purpose of this PR

Pull Request Author

• Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
• Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish
• Pull requests that impact EnergyPlus code must also include unit tests to cover enhancement or defect repair
• Author should provide a "walkthrough" of relevant code changes using a GitHub code review comment process
• If any diffs are expected, author must demonstrate they are justified using plots and descriptions
• If changes fix a defect, the fix should be demonstrated in plots and descriptions
• If any defect files are updated to a more recent version, upload new versions here or on DevSupport
• If IDD requires transition, transition source, rules, ExpandObjects, and IDFs must be updated, and add IDDChange label
• If structural output changes, add to output rules file and add OutputChange label
• If adding/removing any LaTeX docs or figures, update that document's CMakeLists file dependencies
• If adding/removing any output files (e.g., eplustbl.*)
  • Update ..\scripts\Epl-run.bat
  • Update ..\scripts\RunEPlus.bat
  • Update ..\src\EPLaunch\ MainModule.bas, epl-ui.frm, and epl.vbp (VersionComments)
  • Update ...github\workflows\energyplus.py

Reviewer

• Perform a Code Review on GitHub
• If branch is behind develop, merge develop and build locally to check for side effects of the merge
• If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• If feature, test running new feature, try creative ways to break it
• CI status: all green or justified
• Check that performance is not impacted (CI Linux results include performance check)
• Run Unit Test(s) locally
• Check any new function arguments for performance impacts
• Verify IDF naming conventions and styles, memos and notes and defaults
• If new idf included, locally check the err file and other outputs

[jmarrec]

Windows arm64

cmake -G ‘Visual Studio 17 2022’ -A ARM64 -DLINK_WITH_PYTHON:BOOL=ON -DPYTHON_CLI:BOOL=ON -DPython_REQUIRED_VERSION:STRING=3.12.10 ‘-DPython_ROOT_DIR:PATH=C:\hostedtoolcache\windows/Python/3.12.10/arm64/’ -DBUILD_FORTRAN:BOOL=ON -DBUILD_PACKAGE:BOOL=ON -DENABLE_HARDENED_RUNTIME:BOOL=OFF -DDOCUMENTATION_BUILD:STRING=BuildWithAll -DTEX_INTERACTION:STRING=batchmode ../

I'm guessing the issue might be the backslashes in -DPython_ROOT_DIR:PATH=C:\hostedtoolcache\windows/Python/3.12.10/arm64/’

CMake Error at C:/Program Files/CMake/share/cmake-4.3/Modules/FindPackageHandleStandardArgs.cmake:290 (message):
  Could NOT find Python (missing: Python_EXECUTABLE Interpreter) (found
  suitable exact version "3.12.10")

      Reason given by package:
          Interpreter: Wrong version for the interpreter "C:/hostedtoolcache/windows/Python/3.13.13/arm64/python.exe"

Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-4.3/Modules/FindPackageHandleStandardArgs.cmake:654 (_FPHSA_FAILURE_MESSAGE)
  C:/Program Files/CMake/share/cmake-4.3/Modules/FindPython/Support.cmake:4334 (find_package_handle_standard_args)
  C:/Program Files/CMake/share/cmake-4.3/Modules/FindPython.cmake:700 (include)
  CMakeLists.txt:190 (find_package)

---

The step setup-python, with debug output enabled

##[debug]Added matchers: ‘python’. Problem matchers scan action output for known warning or error strings and report these inline.
##[debug]Node Action run completed with exit code 0
##[debug]pythonLocation=‘C:\hostedtoolcache\windows\Python\3.12.10\arm64’
##[debug]PKG_CONFIG_PATH=‘C:\hostedtoolcache\windows\Python\3.12.10\arm64/lib/pkgconfig’
##[debug]pythonLocation=‘C:\hostedtoolcache\windows\Python\3.12.10\arm64’
##[debug]Python_ROOT_DIR=‘C:\hostedtoolcache\windows\Python\3.12.10\arm64’
##[debug]Python2_ROOT_DIR=‘C:\hostedtoolcache\windows\Python\3.12.10\arm64’
##[debug]Python3_ROOT_DIR=‘C:\hostedtoolcache\windows\Python\3.12.10\arm64’
##[debug]PKG_CONFIG_PATH=‘C:\hostedtoolcache\windows\Python\3.12.10\arm64/lib/pkgconfig’
##[debug]Set output python-version = 3.12.10
##[debug]Set output python-path = C:\hostedtoolcache\windows\Python\3.12.10\arm64\python.exe
##[debug]Finishing: Set up Python 3.12.10

[jmarrec]

Update patched QtIFW to a newer version: https://github.com/jmarrec/QtIFW-fixup/releases/tag/v5.0.0-dev-with-fixup2

Fix a typo in flags passed to codesign: should be --options not --option

I also updated the target branch onto installer-framework 4.11.0: https://github.com/jmarrec/installer-framework/tree/QTIFW-3084-more-4_11_0

And Updated qt6 static to 6.11.0 (from 6.7.2) since I couldn't build with my macOS 26.5 with clang 21 (and even then, had to cherry pick one Qt commit thart's only on Qt's dev branch...)

[mitchute]

It looks like everything is building again. Thanks @jmarrec.

[jmarrec]

Explicitly pass Python_EXECUTABLE to avoid a broken FindPython (new in cmake 4.3.0) arm64 detection on windows

passing -DPython_EXECUTABLE:FILEPATH=<...>bypasses the entire discovery phase, handing CMake a pre-validated path so _PYTHON_VALIDATE_INTERPRETER never needs to search

I fixed the issue upstream in cmake but it won't be released soon enough: https://gitlab.kitware.com/cmake/cmake/-/merge_requests/12158

(I'm also doing forward slashes now, as I thought it could be the root cause and it's more correct for cmake)

[jmarrec]

I think the mac failure was actually a fluke to begin with.

But I did go into (a very lenghty) endeavor where I updated my patched qtifw to be based on qtifw 4.11.0, and qt 6.9.1. https://github.com/jmarrec/QtIFW-fixup/releases/tag/v4.11.0-Patched