Skip to content
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

Explore use of VCPkg to manage dependencies #2

Open
4 tasks
michael-okeefe opened this issue Mar 27, 2024 · 1 comment
Open
4 tasks

Explore use of VCPkg to manage dependencies #2

michael-okeefe opened this issue Mar 27, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers low-priority "Nice to have" but not necessary; prioritize lower
Milestone

Comments

@michael-okeefe
Copy link
Member

  • Follow the instructions to set up vcpkg and add our current dependencies
  • Remove all submodules
  • Ensure project builds correctly under the vcpkg setup
  • Test on Windows, Mac, Linux (manually or via the CI)

VCPkg seems like a great way to manage dependencies. My understanding is that it works out of the box on Windows (Visual Studio) and can be enabled through cmake for all other platforms. This task would explore seeing what it would take to set up VCPkg for GTest and any other dependencies we have (as opposed to submodules).

@michael-okeefe michael-okeefe added enhancement New feature or request low-priority "Nice to have" but not necessary; prioritize lower good first issue Good for newcomers labels Mar 27, 2024
@michael-okeefe
Copy link
Member Author

Note: hold off for now until we can discuss as a company/team. There is concern that 1) it is yet another dependency, and 2) it is still relatively young. I don’t want that to stop us from exploring it though.

@michael-okeefe michael-okeefe added this to the 2025+ milestone Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers low-priority "Nice to have" but not necessary; prioritize lower
Projects
None yet
Development

No branches or pull requests

1 participant