Skip to content

Latest commit

 

History

History
54 lines (35 loc) · 4.03 KB

File metadata and controls

54 lines (35 loc) · 4.03 KB

Primary Sources and Planning References

Access dates should be refreshed in the final repository. These links support planning; implementation must verify the exact versions encountered after kickoff.

Hackathon

  • Zero Dependency official website — tracks, zero-dependency definition, submission requirements, bonuses, scoring, rules, timeline, and FAQ.
  • Organizer email from Maksim Muravev to Ayan Khan — runtime invocation prohibited; generated metadata permitted with disclosure and graceful degradation; stdin allowed; build tools permitted; C++ includes libc/POSIX; Single File scope; same-machine reproducibility; Package Killer interpretation; no code before kickoff. Preserve the original email separately.

CMake File API

Important planning fact: CMake writes index-*.json beneath <build>/.cmake/api/v1/reply/, and clients should read the index before referenced reply files. Target ids are opaque and must not be interpreted.

CTest JSON

Important planning fact: --show-only lists test information without executing tests; json-v1 provides a structured format. diff2test consumes a file created earlier and does not invoke CTest.

Compiler dependency files

Important planning fact: GCC -MD can emit dependency files as a side effect of compilation, while -MMD excludes system headers. The chosen mode affects what completeness claim is defensible.

C++ standard library

cppreference is a practical secondary reference. Where standard conformance is disputed, consult the relevant ISO C++ working draft/toolchain documentation.

Build reproducibility

  • reproducible-builds.org documentation — sources of build nondeterminism and mitigation concepts.
  • GCC/Clang/linker documentation for the exact selected flags — record exact versions during the event.

Source-use policy

  • Prefer primary official documentation for format semantics.
  • Do not copy implementation code from parsers/libraries.
  • Record any dev-only test framework and disclose it if used.
  • Separate verified format facts from project policy decisions.
  • Update source links if the actual event toolchain uses older format versions than latest documentation.