Allow to include or exclude specific sections from a file
Nobody has claimed this yet.
- Dominant language
- Linker Script
- Stars
- 12
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
This would allow finer control over the positioning of the sections of each file.
It should work without issues with section reordering ( decompals/slinky#44 ).
Compatibility with decompals/slinky#27 will be weird.
Syntax would look like something like this
- name: code
files:
- { path: src/code/main.o }
- { path: src/code/z_message_PAL.o, only_sections: [.data], section_order: { .data: .rodata } }
- { path: src/code/z_game_over.o, only_sections: [.data], section_order: { .data: .rodata } }
- { path: src/code/z_message_PAL.o, exclude_sections: [.data] }
- { path: src/code/z_game_over.o, exclude_sections: [.data] }
Combining only_sections and exclude_sections in the same entry should be illegal.
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 comparing the YAML examples with the section-reordering work in decompals/slinky#44 and the compatibility concern in decompals/slinky#27. Done means supporting only_sections and exclude_sections, preserving section reordering, and rejecting entries that combine both options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100