Supermodel Forum

Joaquim Gonçalves wrote:The first version of Git revision 46eff8c is released. I'm glad to see you made it.
https://github.com/trzy/Supermodel/comm ... 743f657eae

This is not a GitHub action and runs on a spare PC here at home, so it's a bit fragile. How about you try to figure out the GitHub Actions -- how to build and package a release?

Bart wrote:

Joaquim Gonçalves wrote:The first version of Git revision 46eff8c is released. I'm glad to see you made it.
https://github.com/trzy/Supermodel/comm ... 743f657eae

This is not a GitHub action and runs on a spare PC here at home, so it's a bit fragile. How about you try to figure out the GitHub Actions -- how to build and package a release?

I don´t know.
But mame devs knows that.
Github only fetch and merge automatic, the rest with knowledge knows how to put the codes to work it fine.

Bart wrote:

orimarc wrote:Another thing is that you now can have a centralized "TODO: fix this stuff" list with the Issues tab.

That's a good idea! We should leverage these features. Truth be told Azure DevOps is even better than GitHub but I don't think it's a great place for a public repo.

I agree, Azure Pipelines is easier for automated releases but haven't seen it popular as public repo. It is very popular in corporate though. Normally you'd write a YAML that defines the job and has triggers for build/release like merge to master and runs on a VM in the cloud. I usually create pipelines for test automation but my experience is C#.

I remember trying GitHub Actions couple years back on a Java codebase and it's pretty similar to how Azure Pipelines does it. There were some different keywords here and there but it all starts with defining the YAML.

k_rollo wrote:

Bart wrote:

orimarc wrote:Another thing is that you now can have a centralized "TODO: fix this stuff" list with the Issues tab.

That's a good idea! We should leverage these features. Truth be told Azure DevOps is even better than GitHub but I don't think it's a great place for a public repo.

I agree, Azure Pipelines is easier for automated releases but haven't seen it popular as public repo. It is very popular in corporate though. Normally you'd write a YAML that defines the job and has triggers for build/release like merge to master and runs on a VM in the cloud. I usually create pipelines for test automation but my experience is C#.

I remember trying GitHub Actions couple years back on a Java codebase and it's pretty similar to how Azure Pipelines does it. There were some different keywords here and there but it all starts with defining the YAML.

I looked at it briefly but it seems like a simple build example doesn't exist. Some sort of marketplace exists and there are build scripts there. Need to find a way to configure an MSYS2 installation and it should be relatively straightforward. If you'd like to try your hand at it, please feel free and we can add it to the repo if it works

Definitely caught my interest. Haven't been around C/C++ in a while so I'll try to build local first to get a handle on it. The premise of it is whatever you do on local, you define it in YAML so the same thing can run on the VM in the cloud. Azure/GitHub offers Win, Mac, Linux VMs for free so you can build for different platforms all at the same time.

Yes, there is no simple build example and every bloody tutorial in YouTube is NodeJS (ugh) haha. I'm leaving these as examples we can go back to:
https://github.com/PCSX2/pcsx2/blob/mas ... ew_tag.yml
https://github.com/PCSX2/pcsx2/blob/mas ... peline.yml

This is how they do it at PCSX2. Looking quickly at it, they have YAMLs for different platforms and the build YAML calls other YAMLs.

k_rollo wrote:Definitely caught my interest. Haven't been around C/C++ in a while so I'll try to build local first to get a handle on it. The premise of it is whatever you do on local, you define it in YAML so the same thing can run on the VM in the cloud. Azure/GitHub offers Win, Mac, Linux VMs for free so you can build for different platforms all at the same time.

Yes, there is no simple build example and every bloody tutorial in YouTube is NodeJS (ugh) haha. I'm leaving these as examples we can go back to:
https://github.com/PCSX2/pcsx2/blob/mas ... ew_tag.yml
https://github.com/PCSX2/pcsx2/blob/mas ... peline.yml

This is how they do it at PCSX2. Looking quickly at it, they have YAMLs for different platforms and the build YAML calls other YAMLs.

Thanks for helping Bart.

No worries, I'll let you guys know if I make any headway in it. Just caught up with some deliverables at work.

Took the latest devbuild and forgot every package has its own Supermodel.ini. Forgot to back up mine and overwrote it. Have to re-do my custom controller mappings.

EDIT: Is it possible not to include the Supermodel.ini in the next builds since it generates anyway on -config-inputs iirc? This makes it easier to overwrite everything else every update.

That's a tough call. Can you open an issue on GitHub? Not sure when I'll be able to get around to it, I'm in a real crunch this next two weeks.

We probably could just rely on compiled-in defaults and let it be generated on -config-inputs. OTOH, I think a lot of people might already be following instructions that have them manually edit that file and if there is no initial sample, that could be an issue.

What does everyone else think?

Sure Bart, will open a ticket in GitHub and put some ideas in it.

EDIT: Ticket raised here - https://github.com/trzy/Supermodel/issues/6