Enable Windows releases without Windows CI/CD dependency #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Windows releases required
windows-latestrunners and 25-minute builds. This changes to a pre-built executable approach: build once on Windows, commit to repo, package from Linux.Changes
Workflow simplification
build-windowsjob now runs onubuntu-latestBeamCommander.exeinbin/, packages withzipFiles removed
.sln,.vcxproj,.vcxproj.filters)icon.rc,*.ico)Documentation added
.github/BUILD_WINDOWS_EXECUTABLE.md- Instructions for building on Windows with Visual Studio or MSYS2/MinGW.github/WINDOWS_BUILD.md- Describes one-time build workflowUsage
Build executable once on Windows, commit to
openframeworks-src-master/apps/myApps/BeamCommander/bin/:Create releases from any machine:
Workflow packages pre-built executable with documentation, creates release. No Windows runners required after initial build.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.