libvaxis/build.zig.zon

.{
    .name = "vaxis",
    .version = "0.1.0",
    .paths = .{""},
    .dependencies = .{
        .ziglyph = .{
            .url = "https://codeberg.org/dude_the_builder/ziglyph/archive/ac50ab06c9.tar.gz",
            .hash = "1220e097fbfb3a15a6f3484cf507f1f10ab571d1bcf519c3b5447ca727782b7a5264",
        },
        .zigimg = .{
            .url = "https://github.com/zigimg/zigimg/archive/2224f91.tar.gz",
            .hash = "12207067e4892c48369415268648380859baa89c324748ae5bfda414a12868c9fc8b",
        },
    },
}
initial commit Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-18 04:52:33 +01:00			`.{`
fix name Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-29 04:36:30 +01:00			`.name = "vaxis",`
add pathological example as a terminal perf test 2024-02-09 19:27:22 +01:00			`.version = "0.1.0",`
refactor: make code more idiomatic - Added standard .gitattributes file for Zig projects. - Reworked build.zig a little, hopefully it's a bit clearer. Also, now zig build will run all steps. - outer: while in examples was redundant since there's only one loop to break from. switch expressions don't allow breaking from them, so breaking is only for loops, i.e. while and for. - When returning a struct instance from a function, the compiler infers the return type from function signature, so instead of return MyType{...}; , it's more idiomatic to write return .{...};. - Logging adds a new line by default, so you don't usually need to write \n like here: log.debug("event: {}\r\n", .{event});. 2024-02-11 19:59:33 +01:00			`.paths = .{""},`
initial commit Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-18 04:52:33 +01:00			`.dependencies = .{`
			`.ziglyph = .{`
refactor: make code more idiomatic - Added standard .gitattributes file for Zig projects. - Reworked build.zig a little, hopefully it's a bit clearer. Also, now zig build will run all steps. - outer: while in examples was redundant since there's only one loop to break from. switch expressions don't allow breaking from them, so breaking is only for loops, i.e. while and for. - When returning a struct instance from a function, the compiler infers the return type from function signature, so instead of return MyType{...}; , it's more idiomatic to write return .{...};. - Logging adds a new line by default, so you don't usually need to write \n like here: log.debug("event: {}\r\n", .{event});. 2024-02-11 19:59:33 +01:00			`.url = "https://codeberg.org/dude_the_builder/ziglyph/archive/ac50ab06c9.tar.gz",`
			`.hash = "1220e097fbfb3a15a6f3484cf507f1f10ab571d1bcf519c3b5447ca727782b7a5264",`
			`},`
			`.zigimg = .{`
			`.url = "https://github.com/zigimg/zigimg/archive/2224f91.tar.gz",`
			`.hash = "12207067e4892c48369415268648380859baa89c324748ae5bfda414a12868c9fc8b",`
initial commit Signed-off-by: Tim Culverhouse <tim@timculverhouse.com> 2024-01-18 04:52:33 +01:00			`},`
			`},`
			`}`