zig 0.14 fixes

Author: rdunnington

build.zig

@@ -883,7 +883,7 @@ pub fn build(b: *Build) !void {
     } else {
         curl_lib.root_module.addCMacro("CURL_EXTERN_SYMBOL", "__attribute__ ((__visibility__ (\"default\"))");
 
-        if (target.result.isDarwin() == false) {
+        if (target.result.os.tag.isDarwin() == false) {
             curl_lib.root_module.addCMacro("ENABLE_IPV6", "1");
             curl_lib.root_module.addCMacro("HAVE_GETHOSTBYNAME_R", "1");
             curl_lib.root_module.addCMacro("HAVE_MSG_NOSIGNAL", "1");

build.zig.zon

@@ -1,14 +1,27 @@
 .{
-    .name = "orca",
+    .name = .orca,
 
     // This is a [Semantic Version](https://semver.org/).
     // In a future version of Zig it will be used for package deduplication.
     .version = "0.0.1",
 
-    // This field is optional.
-    // This is currently advisory only; Zig does not yet do anything
-    // with this value.
-    //.minimum_zig_version = "0.11.0",
+    // Together with name, this represents a globally unique package
+    // identifier. This field is generated by the Zig toolchain when the
+    // package is first created, and then *never changes*. This allows
+    // unambiguous detection of one package being an updated version of
+    // another.
+    //
+    // When forking a Zig project, this id should be regenerated (delete the
+    // field and run `zig build`) if the upstream project is still maintained.
+    // Otherwise, the fork is *hostile*, attempting to take control over the
+    // original project's identity. Thus it is recommended to leave the comment
+    // on the following line intact, so that it shows up in code reviews that
+    // modify the field.
+    .fingerprint = 0x6111edddc2c61a9f, // Changing this has security and trust implications.
+
+    // Tracks the earliest Zig version that the package considers to be a
+    // supported use case.
+    .minimum_zig_version = "0.14.0",
 
     // 
     .dependencies = .{