You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we can improve CI a bit, and make the prebuilt system work better overall
Just build pre-builts once for each platform (no multiple node versions needed)
run tests as separate action on more node versions (for example include 10 and 17, since it's current)
Get non-x86-64 builds working (pi, M1)
move artifacts to tagged release (or figure out a better way to find the "best" artifact to use for a pre-built)
"best" artifact
We should have fall-through logic for choosing the best version for a supported platform/arch.
graph TD
ENV{Is an env-var set to force build?}
FS{Is it already built locally in target dir?}
GIT{Is this a git repo?}
TAGGED{Is this tagged with something already in releases?}
PKG{Is this package.json version in releases?}
BUILD[Build using cmake]
RELEASE[Download github release artifact]
ENV --> |yes| BUILD
ENV --> |no| FS
FS --> |yes| FS_USE(use that)
FS --> |no| GIT
GIT --> |yes| TAGGED
GIT --> |no| PKG
TAGGED ==> |yes| RELEASE
TAGGED ==> |no| PKG
PKG --> |yes| RELEASE
PKG --> |no| BUILD
Loading
Diagram is a bit crazy, but I think this would cascade correctly. I think we could make tags & branches build in CI, too, so if you don't set the env-var to force build, you can use the pre-built for that branch (like use whatever is the current raylib4-0.8.1 build for your platform, rather than fall right through to building.
The text was updated successfully, but these errors were encountered:
I think we can improve CI a bit, and make the prebuilt system work better overall
"best" artifact
We should have fall-through logic for choosing the best version for a supported platform/arch.
Diagram is a bit crazy, but I think this would cascade correctly. I think we could make tags & branches build in CI, too, so if you don't set the env-var to force build, you can use the pre-built for that branch (like use whatever is the current
raylib4-0.8.1
build for your platform, rather than fall right through to building.The text was updated successfully, but these errors were encountered: