Add tests that invoke a linker which uses generated linker scripts from slinky
Nobody has claimed this yet.
- Dominant language
- Linker Script
- Stars
- 12
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Have dummy projects (with dummy C and asm files) that get built and linked using linker scripts generated by slinky.
Would be nice a few multiple projects that aim to represent multiple kinds of projects/platforms/variants, so we don't miss anything. Including but not limited to:
- N64
- IDO
- KMC
- EGCS
- Out of normal RAM segments
- Multiple overlays
- Shared vram overlays
- PSX
- PSX-EXE
- Overlays (or whatever they are called)
- No use of
$gpregister (-G0) - Hardcode the
$gpregister in the yaml - Shiftable
$gpregister
- PS2
- idk
- GC / Wii
- idk
Make sure the produced binary and mapfile is still the same as expected
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
Start by locating the existing test and build setup for dummy C and asm projects, then identify how slinky-generated linker scripts are invoked. Done means representative N64, PSX, PS2, and GC/Wii variants build and link successfully, with binaries and mapfiles matching the expected outputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, compilers, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100