177: gfx-rs update and multiple submissions r=msiglreith a=kvark
~~I wanted to get the Diligent Engine running, eventually got blocked by https://github.com/gfx-rs/gfx/issues/2676~~
Gets us full Diligent Engine compatibility 🎉
Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
175: Portability extensions fixes, README update r=grovesNL a=kvark
This version is confirmed to work with VkPI CTS 🎉
Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
173: Dependencies update, all-around unsafe qualifiers r=grovesNL a=kvark
The big update to hal-0.1 and beyond.
I'm not sure that trying to minimize the `unsafe` spots was the right decision... perhaps it's easier to just mark all of gfxXxx methods unsafe, but I'm too tired now to rewrite it again.
Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
163: Change deploy to overwrite existing release files r=kvark a=grovesNL
Small but important fix to resolve https://travis-ci.org/gfx-rs/portability/jobs/425115925#L1818
Earlier I bumped the `latest` tag with `git tag -a latest -f; and git push --tags -f` and it built and attempted to deploy successfully, but didn't upload the new files because of this.
Co-authored-by: Joshua Groves <josh@joshgroves.com>
155: Use git describe to create `commit-sha` r=kvark a=grovesNL
- `../.git/refs/heads/master` failed on CI, so just use git describe here as well
- .gitignore includes updated package names and temporary commit-sha
Co-authored-by: Joshua Groves <josh@joshgroves.com>
149: Use short commit SHA and single level of directories for binaries r=kvark a=grovesNL
Include OS name, use shorter commit SHA, and use a single level of directories for produced binaries.
The only potential downside about the commit SHA being included is that moving tags will cause the binaries to aggregate on the single release, see https://github.com/gfx-rs/portability/releases for example. Maybe this is a useful feature though, and we'll just need to clean releases up every once in a while.
Co-authored-by: Joshua Groves <josh@joshgroves.com>
148: Prevent empty cc arguments on Linux r=grovesNL a=grovesNL
I believe [the deployment error on Linux](https://travis-ci.org/gfx-rs/portability/jobs/421412694#L956) is caused by passing empty strings to cc on Linux. This PR attempts to address it by conditionally including the full Clink-arg string as a single variable instead.
Co-authored-by: Joshua Groves <josh@joshgroves.com>
146: Allow Linux binaries r=grovesNL a=grovesNL
- Include commit SHA in binary filename
- Only set current and compatibility versions on Darwin which should allow Linux targets to use `make package.zip`
Co-authored-by: Joshua Groves <josh@joshgroves.com>
143: Deployment configuration r=kvark a=grovesNL
Continue deployment configuration:
- just run everything in `script` instead of separating them
- only attempt to deploy for Rust stable builds
- `skip_cleanup` forces temporary build artifacts not to be cleared and seems to be recommended for this deployment
Co-authored-by: Joshua Groves <josh@joshgroves.com>
