mitchellh
commented
3 weeks ago I realized my repro has some Nix paths hardcoded. Here is a build.zig that also reproduces it, just put simdutf.cpp inside the vendor folder.
Command: zig build -Dtarget=x86_64-linux
const std = @import("std");
pub fn build(b: *std.Build) !void {
const target = b.standardTargetOptions(.{});
const optimize = b.standardOptimizeOption(.{});
const lib = b.addStaticLibrary(.{
.name = "simdutf",
.target = target,
.optimize = optimize,
});
lib.linkLibCpp();
lib.addIncludePath(.{ .path = "vendor" });
var flags = std.ArrayList([]const u8).init(b.allocator);
defer flags.deinit();
try flags.appendSlice(&.{});
lib.addCSourceFiles(.{
.flags = flags.items,
.files = &.{
"vendor/simdutf.cpp",
},
});
lib.installHeadersDirectory(
.{ .path = "vendor" },
"",
.{ .include_extensions = &.{".h"} },
);
b.installArtifact(lib);
}
jcollie
der-teufel-programming
Rexicon226
Zig Version
0.13.0
Steps to Reproduce and Observed Behavior
With
zig 0.13and the latest simdutf (5.7.8) at the time of writing amalgamation of simdutf8, targetingx86_64(macOS or Linux works).If it makes a difference, I am cross compiling from an aarch64 machine, but I don't believe that makes a difference since another tester I'm pretty sure reproduced this while building from an x86_64 machine.
Result:
Expected Behavior
Builds.
Additional info: https://github.com/llvm/llvm-project/issues/71325