Not all samples are build into a runnable state in the pipeline
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 183
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
I found this to be the case for the following:
- gu/mipmapping does not build at all
- ms/callback does not build an EBOOT.PBP, not sure if this is intended for this one
- usb/storage does not build an EBOOT.PBP
- utility/msgdialog does not build an EBOOT.PBP
- utility/netconf does not build an EBOOT.PBP
- utility/systemparam does not build an EBOOT.PBP
- wlan does not build an EBOOT.PBP
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the pipeline configuration and inspect the named sample directories: gu/mipmapping, ms/callback, usb/storage, utility/msgdialog, utility/netconf, utility/systemparam, and wlan. Reproduce the sample-build step and determine which entries fail versus omit EBOOT.PBP intentionally. Done means the listed samples produce runnable EBOOT.PBP files or their intentional exceptions are documented and handled by the pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100