Skip to content

feat: scaffold cc app entrypoint + manifest (refs #540) - #745

Draft
rwrife wants to merge 1 commit into
mainfrom
feature/cc-scaffold-540
Draft

feat: scaffold cc app entrypoint + manifest (refs #540)#745
rwrife wants to merge 1 commit into
mainfrom
feature/cc-scaffold-540

Conversation

@rwrife

@rwrife rwrife commented Aug 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • add user/apps/cc/main.c scaffold with stable --help/--version behavior
  • return deterministic non-zero diagnostic for compile attempts while TinyCC freestanding wiring is still pending
  • add staged app manifest user/apps/cc/manifest.json (shape pinned to manifests/apps_dev_cc.json)
  • add help cc resource entry (user/apps/os/help/resources/cc.txt) and list it in the help index

Why this slice

This is a starter slice for #540 that makes the cc app surface concrete and reviewable without claiming full compile/link execution yet.

Test Plan

  • ./build/scripts/test.sh apps_dev_cc_manifest
  • ./build/scripts/validate_manifests.sh user/apps/cc/manifest.json

Follow-ups

  • wire cc into disk-image staging at /apps/dev/cc
  • integrate/port manifest_resolution.c runtime path for freestanding app linking
  • add host/qemu command-behavior tests for cc --help / cc --version and compile-path diagnostics

Refs #540

- add user/apps/cc/main.c with stable --help/--version behavior
- return deterministic non-zero diagnostic for compile path while #408 is pending
- add user/apps/cc/manifest.json aligned to manifests/apps_dev_cc.json
- add help entry resources for the new cc command

Refs #540
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant