Compare commits

..

No commits in common. "8cd0defd4508a21e4e8b137586731bfa5bbe8af2" and "8727a4e03810f0ccbbd0b6b3020efe5eac337a0d" have entirely different histories.

2 changed files with 4 additions and 13 deletions

View File

@ -12,19 +12,10 @@ steps:
from_secret: docker_password from_secret: docker_password
REGISTRY: REGISTRY:
from_secret: docker_registry from_secret: docker_registry
ZIG_VERSION: 0.9.1
commands: commands:
# DRONE_STAGE_ARCH is fine, but we can't substitute directly because zig - wget https://ziglang.org/download/0.9.0/zig-linux-x86_64-0.9.0.tar.xz
# uses x86_64 instead of amd64. They also use aarch64 instead of arm64. - tar x -C /usr/local -f zig-linux-x86_64-0.9.0.tar.xz
# - ln -s /usr/local/zig-linux-x86_64-0.9.0/zig /usr/local/bin/zig
# However, arm64/linux isn't quite fully tier 1 yet, so this is more of a
# TODO: https://github.com/ziglang/zig/issues/2443
#
# DRONE_STAGE_ARCH=amd64
# DRONE_STAGE_ARCH=arm64
- wget https://ziglang.org/download/${ZIG_VERSION}/zig-linux-x86_64-${ZIG_VERSION}.tar.xz
- tar x -C /usr/local -f zig-linux-${ZIG_VERSION}.tar.xz
- ln -s /usr/local/zig-linux-${ZIG_VERSION}/zig /usr/local/bin/zig
- apk add git - apk add git
- (cd codegen && zig build test) - (cd codegen && zig build test)
- zig build -Dfetch # implicitly does a codegen - zig build -Dfetch # implicitly does a codegen

View File

@ -1,4 +1,4 @@
# AWS SDK for Zig # AWS SDK for Zig (zig native branch)
[![Build Status](https://drone.lerch.org/api/badges/lobo/aws-sdk-for-zig/status.svg?ref=refs/heads/master)](https://drone.lerch.org/api/badges/lobo/aws-sdk-for-zig/) [![Build Status](https://drone.lerch.org/api/badges/lobo/aws-sdk-for-zig/status.svg?ref=refs/heads/master)](https://drone.lerch.org/api/badges/lobo/aws-sdk-for-zig/)