zig/mach
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

freetype: don't expose harfbuzz directly from freetype pkg

Browse source 
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.
This commit is contained in:
mlugg 2022-09-29 19:31:34 +01:00 • committed by Stephen Gutekanst
parent 217cc3989a
commit ec8ced475f
1 changed files with 0 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

1
libs/freetype/src/main.zig
View file

@ -7,7 +7,6 @@ pub usingnamespace @import("stroke.zig");
pub usingnamespace @import("types.zig"); pub usingnamespace @import("types.zig");
pub usingnamespace @import("computations.zig"); pub usingnamespace @import("computations.zig");
pub usingnamespace @import("error.zig"); pub usingnamespace @import("error.zig");
pub const harfbuzz = @import("harfbuzz/main.zig");
pub const c = @import("c.zig"); pub const c = @import("c.zig");
const std = @import("std"); const std = @import("std");