frostney / frostney/GocciaScript
Migrate the build onto lwpt build
Open
Nobody has claimed this yet.
internal
- Dominant language
- Pascal
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 45
Description
Summary
Migrate the project build system onto lwpt build (Path A toolchain adoption).
Why
GocciaScript is lwpt's named first consumer, committed to full toolchain migration. Moving the build onto lwpt build dedups bespoke build logic and aligns with the shared toolchain.
Current behavior
The project builds via its own build.pas targets.
Expected behavior
- Manifest-driven
lwpt buildproduces all current targets, gated behind proven equivalence with the existing build.
Scope notes
- Scheduled after the performance and conformance work. Part of the lwpt migration (parent #826).
Contributor 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.
Research direction
Start with the existing build.pas targets and the lwpt migration context in parent issue #826. Compare the current targets with what manifest-driven lwpt build must produce, and treat equivalent output for all current targets as the completion criterion.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100