microsoft / vcpkg-ce-catalog

Metadata file repository for vcpkg-ce

Project

This repository contains the artifact metadata files for the vcpkg-ce utility.

---

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

vcpkg-ce-catalog's Issues

Update strategy

This is really more of a discussion than an issue. I was wondering what the strategy is for adding new releases of packages.

I think this can be easily automated for vcpkg-ce, since there is a fairly small set of packages -- I did something similar for the Rasperry Pi Pico setup for Windows installer: https://github.com/raspberrypi/pico-setup-windows/blob/master/update.ps1

Would be happy to contribute here!

Ninja release is x64 only

The Ninja package zip referenced for Windows is x64-only. It should be marked as such -- let me know and I can do a PR for that.

I tried to get them to do x86 builds as well, but they didn't want it.

Packages like the pico-sdk work fine with NMake instead of Ninja, but I'm not sure if it is assumed that vcpkg-ce users will have desktop development tools installed, and if we could get NMake stand-alone somehow for this subset of users.

OpenOCD for Pico

The microsoft/openocd repo has disabled issues, so just reporting it here:

The currently-recommended branch of OpenOCD that we are using for Pico development is rp2040-v0.12.0. It looks like the Microsoft-built OpenOCD is using some really old RP2040 patches -- those should be removed as Picoprobe is now CMSIS-DAP compatible. The Raspberry Pi downstream branch of OpenOCD is basically the 0.12.0 release + a few patches for SMP support. It would be great if those could be pulled in too.

Again, let me know, would be happy to work on the merge/build etc.

Adding new tools to the catalog

Hey!

Wondering if you're accepting PRs with new tools to be added to the catalog.
I was looking into using vcpkg for nanoFramework to lower the barrier of setting up the tools to allow folks to build the firmware. For most of the targets you already have all that's needed, but for ESP32 their customized gcc toolchain(s) are required. They are available on github, so I guess that won't be very difficult to accomplish...