diff options
| author | Viktor Pocedulić <[email protected]> | 2024-06-16 09:37:45 +0200 |
|---|---|---|
| committer | GitHub <[email protected]> | 2024-06-16 09:37:45 +0200 |
| commit | eff7b065eba17725ddc3c16aef16eb8eeca1d888 (patch) | |
| tree | ce39c23d81b47d49e5d72ba134d02a2c734e9874 /src | |
| parent | b4fbdc028302f9a697f196e8d02a7dca28912f59 (diff) | |
| download | raylib-eff7b065eba17725ddc3c16aef16eb8eeca1d888.tar.gz raylib-eff7b065eba17725ddc3c16aef16eb8eeca1d888.zip | |
[build.zig] Fix raygui build when using addRaygui externally (#4027)
When addRaygui is used from an external build, for example in a
bindings project, the build of a generated `raygui.c` fails with
"raylib.h not found" error from the compiler.
I've traced this down to a raylib step not adding its `src/` to the
shared list of include paths using `addIncludePath` but relying on
`addCSourceFiles` `.root` to provide the implicit include path for
raylib proper's own files.
If raygui is later added to the step the compiler won't know where
to look for `raylib.h` and friends and will fail to build.
This change simply adds raylib's `src/` to the include path list.
Diffstat (limited to 'src')
| -rw-r--r-- | src/build.zig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/build.zig b/src/build.zig index 35622a46..81d4a766 100644 --- a/src/build.zig +++ b/src/build.zig @@ -217,6 +217,7 @@ fn compileRaylib(b: *std.Build, target: std.Build.ResolvedTarget, optimize: std. }, } + raylib.addIncludePath(b.path("src")); raylib.root_module.addCSourceFiles(.{ .root = b.path("src"), .files = c_source_files.items, |