Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webos: add nightly build for webOS? #16322

Open
csdougliss opened this issue Mar 3, 2024 · 1 comment
Open

webos: add nightly build for webOS? #16322

csdougliss opened this issue Mar 3, 2024 · 1 comment

Comments

@csdougliss
Copy link
Contributor

Description

We now have a github workflow for webOS build:
https://github.com/libretro/RetroArch/blob/master/.github/workflows/webOS.yml
https://github.com/libretro/RetroArch/actions/workflows/webOS.yml

Would it be possible to add webOS to the nightly builds so these are also built for webOS users?

https://buildbot.libretro.com/nightly/

@LibretroAdmin not sure who to tag

@zoltanvb
Copy link
Contributor

zoltanvb commented Mar 3, 2024

Few comments, I do not have any authority for deciding / doing this, but have seen a few things while working with armv7 and a few other RA/core builds.
First, it would probably be useful to set up the compilation procedure to use a container, and have static stuff like SDK install done there, once. If you check other Github workflows, they pull an image for start. The build container sources are on gitlab.
Actual builds that are published on buildbot.libretro.com, are not built here on github, but on a gitlab server. Probably 2 CI templates will be needed, one for make, and another for cmake based cores. Maybe more, if there is need for different binaries (if there is e.g. also arm64 besides the armv7a).
Compilation is governed by the .gitlab-ci.yml file that is present in each repo's root that is currently being built. WebOS target needs to be added there for RA + for each core that is planned to be available, and of course tested that it can be built.
Depending on the build setup, it is possible that individual core makefiles need some change, although I see there are already 60+ cores compiled for this platform behind the default URL, so I presume you have found a way to use same make path as an existing platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants