You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that #97 has landed, the next step to prepare for official crate releases is to build and verify the crates on the CI server and release them to the skia-binariesrust-skia repository. The resulting .crate files are platform and feature independent, so we can create and verify them without an initial build in a separate Azure Pipelines job, but I would rather create them after a binaries package was created so that the verification already pulls in the previously built binary from the regular build and indirectly so tests the binary package downloader with each CI build.
For a first setup, I think we should limit the crate generation to "Linux stable" for now.
The text was updated successfully, but these errors were encountered:
pragmatrix
changed the title
Build, verify, and deploy cargo crates of skia-bindings and skia-safe to skia-binaries.
Build, verify, and deploy cargo crates of skia-bindings and skia-safe to rust-skia.
May 13, 2019
Now that #97 has landed, the next step to prepare for official crate releases is to build and verify the crates on the CI server and release them to the
skia-binariesrust-skia repository. The resulting.crate
files are platform and feature independent, so we can create and verify them without an initial build in a separate Azure Pipelines job, but I would rather create them after a binaries package was created so that the verification already pulls in the previously built binary from the regular build and indirectly so tests the binary package downloader with each CI build.For a first setup, I think we should limit the crate generation to "Linux stable" for now.
The text was updated successfully, but these errors were encountered: