gpu-dawn: update README to clarify how to build as separate repo #203
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#203
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?
Moved here from https://github.com/hexops/mach-gpu-dawn/issues/1 (trying to keep all issues in this tracker)
@freakynit wrote:
Just tried building from source using following 3 commands:
Getting build error immediately:
zig version: 0.9.0
My system:
MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)
macos BigSur (Version: 11.5.1 (20G80))
Processor: 2 GHz Quad-Core Intel Core i5
Graphics: Intel Iris Plus Graphics 1536 MB
Thanks for filing this, sorry I didn't see it sooner.
You will need to replace a symlinks with a clone of a dependency, this is a bit of a hack until Zig gets a proper package manager, sorry about that.
Then you should be able to proceed with
zig build -Ddawn-from-source=truePlease make sure to use Zig v0.10 (nightly), not v0.9, which you can get a binary release of at the top of this page: https://ziglang.org/download/
I'll update the README soon to clarify this, sorry for the trouble! Let me know if that doesn't help.
It worked 👍 Thanks @slimsag