[examples] automatically rebuild raylib #4854
Conversation
Hooked up raylib as a library in the examples build so that if a change is made in raylib then running `zig build` in the examples directory will automatically rebuild raylib. The main pieces to this are the build.zig.zon file which allows the examples build to see the parent raylib directory. Then we can add raylib as a typical dependency and grab the "raylib" artifact to link to. We also no longer need to add include paths since raylib's build.zig installs them for us.
| @@ -0,0 +1,10 @@ | |||
| .{ | |||
There was a problem hiding this comment.
I'd prefer to avoid keep ading build files, can this .zon file be omited somehow?
There was a problem hiding this comment.
The way I would describe it is build.zig.zon is the a way to glue/connect distinct packages together. Since we have two separate build.zig files we essentially have two separate packages so the .zon file is how we "connect them" in a way that we can share build objects between them (i.e. get access to the raylib artifact from the examples build).
The other way to solve this would be to remove the second build.zig file in the examples directory and treat the repo as a single "package". This is a better solution IMO and I'm happy to do that if you prefer.
There was a problem hiding this comment.
The other way to solve this would be to remove the second build.zig file in the examples directory and treat the repo as a single "package". This is a better solution IMO and I'm happy to do that if you prefer.
@marler8997 If using a single-package approach, could it include separate build targets (like a Makefile) or building+artifacts will always include the "full-package"? If that's possible, I prefer to keep a single-build package.
There was a problem hiding this comment.
Yes, I've created #4856 which incorporates the builds into one. Running zig build will still only build/install the raylib library, but now running zig build examples will build/install all the examples. Also the original examples "steps" to run each individual example still work.
|
Closing this one in favor of #4856 |
Hooked up raylib as a library in the examples build so that if a change is made in raylib then running
zig buildin the examples directory will automatically rebuild raylib.The main pieces to this are the build.zig.zon file which allows the examples build to see the parent raylib directory. Then we can add raylib as a typical dependency (like any other external raylib-based application would) and grab the "raylib" artifact to link to. We also no longer need to add include paths since raylib's build.zig installs whatever headers are needed.