build: compile examples and applications on demand #259

Merged

iddev5 merged 1 commit from ay-selective-build into main

2022-04-30 08:10:56 +00:00

iddev5 commented

2022-04-30 07:17:57 +00:00

(Migrated from github.com)

The old behavior is still preserved with a new step compile-all. In future this could be added to CI just to check if all the examples and applications at least build properly. This is not being done right now because zig std lib is undergoing lots of breaking changes right now and it will keep failing CI.

By selecting this checkbox, I agree to license my contributions to this project under the license(s) described in the LICENSE file, and I have the right to do so or have received permission to do so by an employer or client I am producing work for whom has this right.

Without this change, anytime a dependency is modified, all the examples and applications are rebuilt before tring to run any of them. The problem with this approach is that it leads to long compile times which will keep on increasing as more and more examples are added. The old behavior is still preserved with a new step ``compile-all``. In future this could be added to CI just to check if all the examples and applications at least build properly. This is not being done right now because zig std lib is undergoing lots of breaking changes right now and it will keep failing CI. --- - [X] By selecting this checkbox, I agree to license my contributions to this project under the license(s) described in the LICENSE file, and I have the right to do so or have received permission to do so by an employer or client I am producing work for whom has this right.

emidoots (Migrated from github.com) approved these changes

2022-04-30 07:58:32 +00:00

emidoots commented

2022-04-30 08:00:29 +00:00

(Migrated from github.com)

In future this could be added to CI just to check if all the examples and applications at least build properly. This is not being done right now because zig std lib is undergoing lots of breaking changes right now and it will keep failing CI.

We can go ahead and do this now. It's OK if CI fails, that's what it is there for! :) Also, if the CI in this repository fails it won't break the precompiled Dawn builds or anything because those are built in a separate repo's CI.

Plus, our CI uses a pinned version of Zig so it doesn't matter if zig stdlib changes until we try to update to newest version of Zig.

> In future this could be added to CI just to check if all the examples and applications at least build properly. This is not being done right now because zig std lib is undergoing lots of breaking changes right now and it will keep failing CI. We can go ahead and do this now. It's OK if CI fails, that's what it is there for! :) Also, if the CI in this repository fails it won't break the precompiled Dawn builds or anything because those are built in a separate repo's CI. Plus, our CI uses a pinned version of Zig so it doesn't matter if zig stdlib changes until we try to update to newest version of Zig.

👍 1