Additions to streamline the process of testing owl-control for anyone using a Linux workstation. #217
+1,258
−0
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.
Linux Development Setup for Windows VM
This PR adds tooling to make it easier for Linux developers to work on OWL Control using a Windows VM.
Since OWL Control needs Windows-specific APIs and OBS integration, I put together some scripts and documentation to streamline the VM setup process. I've tested everything on Debian 13 and it works.
What's included:
Scripts:
owl-dev-setup.sh- Main interactive menu to keep things simpleowl-install-prerequisites.sh- Sets up QEMU/KVM, virt-manager, and Sambaowl-cleanup.sh- Cleans everything up when you're done or want to start freshowl-windows-dev-setup.ps1- Handles the Windows side setup automaticallyDocumentation:
LINUX_DEV_SETUP.md- Step-by-step walkthrough with troubleshooting tips for the issues I ran intoCONTRIBUTING.mdto point Linux devs to the new guideThe setup uses Samba for file sharing, so you can edit code on Linux and build/test in the Windows VM. The guide walks through creating the VM manually in virt-manager (found this was more reliable than trying to fully automate it), and includes all the quirks I discovered during testing.
I'm happy to make adjustments if needed.
466f724a616e6574