Create build workflow
Moving the build workflow over here, something is going on with devkitPro package servers, because it's all returning 403 now on this workflows.
youre not using the docker container, use the docker container
Alright, I've switched to the docker container, but it's still 403ing when I do dkp-pacman -Syu
because you don't need to do the pacman -Syu, thats not up to the workflow to manage :) does it build without it? (i suspect the docker images need updating, but thats aside this PR)
It builds until it reaches the crypto examples (failes on SHA Engine Example), I do suspect the images would need to be updated too, since all examples build fine on all my other systems and the old workflow.
ye, they'll need updating. i suggest removing the pacman -Syu and ill see to get the dockers updated for it :)
Done that already.
@dakotath, is there a reason why you changed from actions/checkout@v4 to actions/[email protected]?
Honestly I forgot I even changed that
by the way, github actions runners all have 4 cores now, so you can use -j4
It's devkitPPC, not DevKitPPC.
can't this be fixed by editing the commit message when doing a squash merge?
It's devkitPPC, not DevKitPPC.
can't this be fixed by editing the commit message when doing a squash merge
The comment is for information in a vain attempt to get people to name things properly and stop the random capitalisation. This commit message wouldn't appear on squash and the contributor would remain unaware of the proper naming assuming this gets merged. Personally I don't really see the benefit of a workflow here and I really don't see the benefit of providing artifacts for an examples repository intended to illustrate use of the tools and also serve as a test for installed tools/libs.
@dakotath : any updates on the fixes to be pushed?
No updates, it gets the job done, I feel no need to push an update
Not much point keeping this open if the required fixes aren't being made ...