lobo/aws-sdk-for-zig
1
0
Fork 0
Code Issues Pull requests Projects 1 Releases Packages 1 Wiki Activity Actions

remove build.zig aws constant
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 8m5s
Details

Browse source 
This was always problematic, and bypasses the build system. It broke earlier
when moving to proper modules, and really, it is not worth using. The idea was
to allow usage of the SDK in a build context, but that does not work anyway,
because the build operates in a sandboxed environment that effectively bars
things like connecting to TLS endpoints. That is a feature of the build system,
not a bug, and issues like https://github.com/ziglang/zig/issues/14286
demonstrate that the zig team wants to sandbox even further. For downstream,
the right idea here is actually to create an executable that depends on aws
and run it as part of the build. This is where https://git.lerch.org/lobo/lambda-zig
is heading.
This commit is contained in:
Emil Lerch 2026-01-30 12:04:30 -08:00
parent f788eed35c
commit fdc2089969
Signed by: lobo
GPG key ID: A7B62D657EF764F8
1 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
build.zig
View file

@ -3,8 +3,6 @@ const Builder = @import("std").Build;
const models_subdir = "codegen/sdk-codegen/aws-models/"; // note will probably not work on windows const models_subdir = "codegen/sdk-codegen/aws-models/"; // note will probably not work on windows
pub const aws = @import("src/aws.zig");
const test_targets = [_]std.Target.Query{ const test_targets = [_]std.Target.Query{
.{}, // native .{}, // native
.{ .cpu_arch = .x86_64, .os_tag = .linux }, .{ .cpu_arch = .x86_64, .os_tag = .linux },