Use Github Actions - Githubissues

ollydev commented 4 years ago

I've removed Travis and added Github Actions to run Lape's tests. Like it does with Travis all tests currently pass.

Tests are run tests natively on Win32, Win64, Linux (64 bit) and MacOS (64 bit). The Lazarus install step is mostly from Travis-Lazarus and Python was used in each step to have a consistent syntax for each platform.

Notes:

Lazarus only has one macOS x86_64 release published on sourceforge right now since Apple recently nuked x86 support. When more versions are added this will need a tiny update to be able to specify a Lazarus version on macOS builds.
You'll likely want to disable Github actions notifications as seen here

Bonus:

macOS static linking ffi is now tested!

ollydev commented 4 years ago

@nielsAD Changed the badge and decided to use subprocess.call over os.system. Tests fully pass: https://github.com/ollydev/lape/actions/runs/78348148

ollydev commented 4 years ago

Don't merge just yet. Lazarus 2.0.8 was released and has broken macos. https://forum.lazarus.freepascal.org/index.php/topic,49356.msg357637.html#msg357637

ollydev commented 4 years ago

Fixed, all tests pass. https://github.com/ollydev/lape/actions/runs/84215923

ollydev commented 4 years ago

@nielsAD I don't think we should use this anymore. I've made an action for Simba which builds FPC & Lazarus and caches it. https://github.com/ollydev/Simba/blob/simba1400/.github/workflows/build.yml

Would be extremely simple to modify for Lape.

Edit: I have not had one instance where lazbuild randomly access violated since using this method. Builds are super fast too, since all the lazarus/fpc units have already been built.

nielsAD / lape

Use Github Actions #138