Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Build the port inside evals

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c, cmake, cpp, github-actions

Research direction

Read ROADMAP.md, SKILL.md step 5, and the existing CI configuration that builds SDL 3.4.18 with CMake. First review the turn-limit issue referenced as #2 and the current eval cases to understand the tradeoffs. Done means the settled answers are recorded as a dated decision in ROADMAP.md and the issue has a milestone with its own checklist.

Written by the indexing model from the issue text.

Description

enhancement later

Install SDL3 on the eval runner, so the agent can build its port and run it headless, as the skill does on a real machine. Graders could then check that the port runs, not just what it says.

Building adds turns: Haiku 4.5 already reaches the 60-turn limit in 3 of 5 whole-program runs.

What has to be settled before this gets a milestone

  • What a build would prove. M3 kept builds out of evals because a trap compiles cleanly by definition, so a build changes no trap score, and graders can't see whether a build succeeded. SKILL.md step 5's syntax check against the bundled headers already catches compile errors. The gain is graders that check the port runs: a headless run whose output a grader reads, beside the regex graders on the files.
  • Turns. Either the build cases get their own, higher turn limit, or building stays out of the single-trap cases and only the whole-program case builds. Haiku's turn count (#2) should settle first.
  • Getting SDL3 onto the runner. CI already builds SDL 3.4.18 with CMake. The eval sandbox needs the same version prebuilt, so a run doesn't spend minutes and turns building SDL.

Done when

  • The settled answers are a dated decision in ROADMAP.md, and this issue gets a milestone with its own checklist.
Dominant language
C
Stars
1
Forks
1
Avg merge
3m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hazeliscoding/sdl3-porter

All issues in hazeliscoding/sdl3-porter

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.