[Suggestion] Why do you still use travis and not GitHub actions?

[gcarreno]

Hi there,

Full disclaimer, this is me tutting my own horn since I did develop the GitHub Action setup-lazarus.

Are you doing anything so special that can only be done by Travis?

If not, take a look at these(maybe it has enough to get you unstuck from travis.com):

• setup-lazarus - GitHub action to install Lazarus+FPC and some, still incomplete, support for OPM packages
• lazarus-with-github-actions - The simplest of examples on how to use the setup-lazarus GitHub action.

Cheers, Gus

[benibela]

I do not have time to update things that still work.

Yesterday I finally updated from Travis org to Travis com, because the CI on the videlibri repo had broken for almost a year.

Cross compiling is rather special. Wine to test the Windows build, an arm build and qemu-arm to test it

[gcarreno]

Hey there

I do not have time to update things that still work.

Fair enough. But still, the way actions work and the thing I did is way simpler than what you have now. Just take a look at the example project: lazarus-with-github-actions My solution: You edit 1 YAML file and that's it, no taking care if the travis-lazarus repo is up to date or not... But if you're really not interested, then just ignore me :)

Yesterday I finally updated from Travis org to Travis com, because the CI on the videlibri repo had broken for almost a year.

Yeah, because you did an update is why I noticed and wanted to give you options.

Cross compiling is rather special. Wine to test the Windows build, an arm build and qemu-arm to test it

Well, GitHub Actions runs on native Windows Servers, native Ubuntu servers AND native macOS servers. With GitHub actions you don't need any emulation for those 3. And you can choose particular versions of those platforms or just run on the latest version that GitHub supports. In the case of ARM, I'm not aware they have hardware for that, but I'm guessing that we come to a solution that makes it easy in one of those 3 architectures(Windows, Linux, macOS), right?

Cheers, Gus

[benibela]

But still, the way actions work and the thing I did is way simpler than what you have now.

It still takes forever to setup: https://github.com/benibela/xidel/commits/master/.github

In the case of ARM, I'm not aware they have hardware for that, but I'm guessing that we come to a solution that makes it easy in one of those 3 architectures(Windows, Linux, macOS), right?

I do not need the hardware. I need to compile it, not run it

It needs (cross) compilers for (win, linux, android, mac) * (x86,amd64,armel,armhf,aarch64)

[gcarreno]

Hey Benito (@benibela),

It still takes forever to setup:...

Humm, I see that you decided to do it yourself so you could shoehorn the cross compilation. One of the things I didn't mention is that you get Win64, Lin64 and Mac for free, with only my action, but if you want cross to 32 bits or ARM it's a bit more complicated.

What I've seen others do is use fpcup/fpcuplaz to do the cross install. These tools is what fpcupdeluxe uses in the background to do the FPC+Lazarus installs.

Not sure if it will improve on your setup, but it's a new tool for your tool belt.

I'm not sure this is even gonna help you, but It's just another suggestion.

Cheers, Gus