From ec8ced475f0afdb4e213f1fa2191365d0db48978 Mon Sep 17 00:00:00 2001 From: mlugg Date: Thu, 29 Sep 2022 19:31:34 +0100 Subject: [PATCH] freetype: don't expose harfbuzz directly from freetype pkg This declaration itself was nonsensical, as the file being imported was from the harfbuzz package (instead users should import harfbuzz directly). But as well as being nonsensical, this line was occasionally triggering a stage2 bug which we haven't quite tracked down yet which seems to be something to do with conflicting modules importing a file. This issue meant that projects with a specific dependency pattern on freetype and harfbuzz would sometimes randomly get a nonsensical compilation error. This change works around that issue for mach-freetype. --- libs/freetype/src/main.zig | 1 - 1 file changed, 1 deletion(-) diff --git a/libs/freetype/src/main.zig b/libs/freetype/src/main.zig index c3df86f1..4a900700 100644 --- a/libs/freetype/src/main.zig +++ b/libs/freetype/src/main.zig @@ -7,7 +7,6 @@ pub usingnamespace @import("stroke.zig"); pub usingnamespace @import("types.zig"); pub usingnamespace @import("computations.zig"); pub usingnamespace @import("error.zig"); -pub const harfbuzz = @import("harfbuzz/main.zig"); pub const c = @import("c.zig"); const std = @import("std");