automating builds (i.e. by replacing .travis.yml) with GitHub Action(s)?

[mi-hol]

Would automating builds be a topic worth putting effort into?

[turboencabulator]

I like this idea for several reasons:

• I've had problems building the AppImage lately and I don't know if it's just me, or if some 3rd-party tool or dependency broke.
• I don't have access to a Mac machine or any recent Windows machine. It'd be good to make sure nothing inadvertently breaks.

[EspoTek]

Got an email about this recently:

Chris,

Good news. I was glad to have my suspicions confirmed that the firmware was not indeed the problem. Knowing that 2cc0678 was good, I performed a bisect to determine where the problem occurrs, and the result was identifying e9d4298 as the problematic commit. Curious to know if you can reproduce this issue. At any rate, I can continue using my Labrador on 2cc0678, so for me the problem is effectively solved.

[mi-hol]

Got an email about this recently:

@EspoTek I updated the project ReadMe yesterday and removed your email with the intent to lower your support burden.
From my view it would be best to encourage any email writer to post issues first as discussions here.
Hope you share this view :)

[mi-hol]

problematic commit

From other projects I learned, that the best approach to avoid such issues, would be to commit only to a development branch and sync to master/main branch only after a alpha/beta test phase completed successfully.
Should we move to such an approach too?

[EspoTek]

To be frank, I don't think we have the QA resources to do this at this stage. I don't love the "YOLO" approach but it's the only real way forward.

That said, I was working with some students last year to develop a version based on ImGui Librador:
https://github.com/davidjstark/LabradorENG4701

Seems to be much more performant and stable than the main branch, and significantly less code/dependencies/tech debt.

[mi-hol]

I don't think we have the QA resources to do this at this stage

Concluding from the fork's branch setup it already seems to follow the proposed "dev" approach or did I get this wrong?

[mi-hol]

develop a version based on ImGui Librador:
https://github.com/davidjstark/LabradorENG4701

I moved this topic to its own discussion #285 please continue there

[EspoTek]

Also, for what it's worth I have access to both a Mac and Windows machine. :)

[mmehari]

I would also agree to having the automating builds.

In my recent PR (#272), I was only able to test it on Linux platform (X86-64 and Arm64) but not on Windows or macOS. It will facilitate the development process.

[mi-hol]

It will facilitate the development process.

that was my hope, when I raised the suggestion

[EspoTek]

Downloading Qt 5.12 now:
https://download.qt.io/archive/qt/5.12/5.12.12/

Going to try and build locally, and if that works I'll see if we can just shove the existing appVeyor and travis .yml files into o1 or o3-mini-high and get something that runs on GitHub Actions.

[mi-hol]

Going to try and build locally,

@EspoTek is there perhaps any result (good or bad) to share?

[EspoTek]

Going to try and build locally,

@EspoTek is there perhaps any result (good or bad) to share?

Looks like b85a104a3c881ace0e33998d912fef57cdff8ab5 builds and runs fine without a hitch on MSVC2017/64-bit.

[EspoTek]

We now have some untested GPT slop here:
https://github.com/espotek-org/Labrador/tree/master/.github/workflows

I think you guys should be able to manually trigger them? If not, let us know.

[mmehari]

Sorry, I can't either. I don't have Mac PC.

[EspoTek]

I can check Mac on the weekend. It's in my Todo app!

[EspoTek]

Windows seems almost there but the real pain is just getting MSVC2017 onto the build machine. Seems to be no simple way to get it. Half considering moving to MinGW just for that reason.

[turboencabulator]

I'm also getting close on the Windows build. Currently trying MSVC 2019, it's pre-installed on windows-2019 runners so I don't have to wait 30 minutes for 2017 to install.

[EspoTek]

Oh wow, I can definitely test that too. If it needs to be updated to Qt 5.15, that shouldn't be an issue.

[turboencabulator]

Does anyone know how to build the Android app? I'd like to set up a job for it.

[EspoTek]

Does anyone know how to build the Android app? I'd like to set up a job for it.

In Qt Creator I'd just use an Android kit. I'm sure there are similar ways to get it going through the command line.