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

Migrate Windows CI from vcpkg to conda-forge #373

Open
j-rivero opened this issue Jan 12, 2021 · 0 comments
Open

Migrate Windows CI from vcpkg to conda-forge #373

j-rivero opened this issue Jan 12, 2021 · 0 comments
Labels

Comments

@j-rivero
Copy link
Contributor

We are using vcpkg to implement our CI on Windows, particularly to get external dependencies and inject them using -DCMAKE_TOOLCHAIN_FILE into colcon to build all ignitions from source.

Our documentation is recommending to use conda-forge for having binaries installed on Windows and would be good to move our CI infrastructure to follow the tools we recommend for end-user experience. One option could be to replicate the vcpkg setup and install the dependencies and use colcon to build all libraries together from source. A second step could involve to have conda-forge packages for every ignition library and only build from source the library under testing (like we do in Ubuntu with apt).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant