Skip to content

Create build workflow #15

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.

Sign up for GitHub

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Create build workflow #15

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6b09ab4
Create build workflow
dakotath Jan 1, 2025
c7b5999
Use DevKitPPC docker container.
dakotath Jan 1, 2025
a8b5460
Don't update pacman
dakotath Jan 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
name: C/C++ CI

on: [push, pull_request]

jobs:
build:
name: ubuntu-latest
runs-on: ubuntu-latest
container: devkitpro/devkitppc:latest

steps:
- uses: actions/[email protected]

- name: Build
run: |
make -j2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-j2 should be replaced with $(nproc) as I did here switchbrew/libnx@d6e38f2

Runners currently have up to 4 cores but I've still seen 2 core runners recently and of course they may up the cores in the future.


- name: Upload Build Artifacts
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

uploading artifacts from an examples repository just seems like a waste of resources to me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not necessary your own storage that's getting used during the process, so it doesn't really seem like a big deal to me. And also, there are things in certain build environments that break, and I see useful to testing things in multiple build environments (including actions). For example: sometimes I'll update libogc on my Arch laptop and then everything breaks to the point of the exception handler not even working. (This type of result has never been solidly reproducible so don't ask me how to reproduce it). Besides that, I'll get to the rest of the file when I'm done the day.

uses: actions/[email protected]