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

Release a macOS disk image (.dmg) for Apple silicon

Open
  • Is something wrong?
#198 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@SizzleUnrlsd is already working on this.

Since Oct 16, 2026.

  • #199 by @SizzleUnrlsd — open

Assessment

This issue has not been assessed yet.

Description

build enhancement

Releases ship Linux archives only. On macOS, the README sends users to a build from source, with Homebrew's LLVM 20. A ctrace built that way loads LLVM, Clang, Z3 and zstd from Homebrew by absolute path (otool -L build/ctrace), and OpenSSL and Brotli too, which cpp-httplib links whenever it finds them: it cannot be copied to another Mac.

To do

  • A "Build macOS binary (arm64)" job in release-binaries.yml, run on every pull request like the Linux ones, that produces coretrace-<version>-macos-arm64.dmg and its .sha256, with the Python analyzer.
  • The image holds one folder laid out as the Linux archive. The Homebrew libraries ctrace loads ship in lib/, and every Mach-O file loads them relative to itself: the macOS counterpart of the patchelf step.
  • Licenses as on Linux: an inventory of what the image ships, the license and version of each Homebrew formula collected from its keg, and a packaging that fails on an unlisted library.
  • Before the upload, the image is mounted, its folder copied out and run with Homebrew moved away: the Python analyzer, a C analysis and a concurrency analysis.
  • On a tag, the image is attached to the release with its provenance attestation.
  • The README says how to install it, and how to remove the Gatekeeper mark.

Out of scope

  • Signing with a Developer ID, and notarization. CoreTrace has no Apple Developer account. The image is signed ad hoc, which Apple silicon requires; macOS refuses to run a ctrace that a browser downloaded until the quarantine mark is removed. Once an account exists: import the certificate into a temporary keychain, sign each Mach-O file with codesign --options runtime --timestamp, then run xcrun notarytool submit --wait and xcrun stapler staple on the image.
  • Intel Macs. They need an x86_64 runner and Homebrew libraries built for it.
  • The runtime analyzer. It is released for Linux only.

Acceptance

  • The job passes on pull requests, and the image it builds runs from any folder, without Homebrew.
  • check-licenses.sh passes on the image with the macOS inventory.
  • A release attaches the .dmg, its .sha256 and its attestation.
Dominant language
C++
Stars
5
Forks
4
Avg merge
1h 9m
Merged PRs (30d)
81

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 CoreTrace/coretrace

All issues in CoreTrace/coretrace

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.