Not all samples are build into a runnable state in the pipeline
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- build-system, ci-cd
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.
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
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 190
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 12
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from pspdev/pspsdk
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pspdev/pspsdk#388 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pspdev/pspsdk#412 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gnif/LookingGlass#1352 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100