-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add github actions compile test #131
Conversation
If you wanted to be a bit more minimal about the Windows build, the Windows runner already has a bunch of stuff installed so you don't need to install the
|
The reason for installing CMake and MinGW from chocolatey is so we have known compilers, and a know installation process that we can suggest to users, rather than just using the versions built into GitHub actions runners
Thanks for these suggestions, I will switch the action to use curl and the pre-installed 7zip |
Looks like the pre-installed 7zip is causing the Windows tests to fail? 😕 |
I guess you need to call |
I agree it looks like the curl that's failing, but it looks like it is invoking |
Yes, you're right, it is invoking curl, I guess you just need a flag to allow redirects with |
Thanks, that's it - I'll use |
On that topic, unrelated to this particular PR, it might make sense to write a small PowerShell script that installs these dependencies the same way the VS Code extension does? Basically just use the manifest files that are used there, download and add to PATH for command line builds. I see the SDK, examples, and now this (picotool) have copies of this choco-based install, which are not exactly the same; and one of the major differences from the VS Code ext is the ARM GCC specified for choco is much older (even pico-setup-windows had a newer build.) |
Add compilation test across variations of OS, generator, and with/without Libusb, MbedTLS, and pre-compiled xip-ram-perms and flash-id executables