freetype/harfbuss: upgrade C dependency version #772
Labels
No labels
CI
all
basisu
blog
bug
build
contributor-friendly
core
correctness
deferred
dev
direct3d-headers
docs
driver-os-issue
duplicate
dxcompiler
editor
examples
experiment
feature-idea
feedback
flac
freetype
gamemode
gkurve
glfw
gpu
gpu-dawn
harfbuzz
help welcome
in-progress
infrastructure
invalid
libmach
linux-audio-headers
long-term
mach
mach.gfx
mach.math
mach.physics
mach.testing
model3d
needs-triage
object
opengl-headers
opus
os/linux
os/macos
os/wasm
os/windows
package-manager
priority
proposal
proposal-accepted
question
roadmap
slipped
stability
sysaudio
sysgpu
sysjs
validating-fix
vulkan-zig-generated
wayland-headers
website
wontfix
wrench
www
x11-headers
xcode-frameworks
zig-update
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
hexops/mach#772
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This one is tricky and rather involved. The state of things today:
libs/freetypedo not build. Zig updated to Clang 15, and that version of harfbuzz does not build with clang 15 due to a new clang warning which is not possible to disable:github.com/hexops/mach@142c8b5b2elibs/freetypeout of the main repo and into its own standalone repo: https://github.com/hexops/mach-freetype - but we cannot yet rely on this as the new Zig package manager does not yet support a Zig package depending on a C package. https://github.com/hexops/mach/issues/721We could fix #1 above by updating https://github.com/hexops-graveyard/freetype to the latest upstream version, as they have a patch for clang 15 upstream which fixes the warning, however:
VER-2-12-1(what our Zig bindings were written against) to perform all relevant updates to our Zig bindings, so they do not become out of sync with the underlying C code.We should do this ASAP, it's unclear if we should wait for the Zig package manager fix so we can avoid doing extra work, but all in all it may require a bit of work either way.