Add macOS build and run entrypoint#73
Open
AriaShishegaran wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
script/build_and_run.shas the project-local macOS build/run/debug entrypointEaselscheme in Debug configuration with deterministic project-local DerivedData under.build/xcoderun,--debug,--logs,--telemetry, and--verifymodes.codex/environments/environment.tomlso the Codex app Run action uses the same scriptCloses #71
Why
The macOS build/debug workflow previously required ad hoc command chains. A single checked-in entrypoint makes agent and contributor debugging repeatable and keeps launch verification consistent.
This PR is intentionally separate from Codex runtime discovery work so review stays focused on developer tooling only.
Validation
./script/build_and_run.sh --verifyEaselscheme.build/xcode/Build/Products/Debug/Easel.appEaselprocess exists withpgrep -x EaselNotes
Xcode prints a footer naming SwiftLint plugin invocations under “failed” even though the build exits 0 and reports
** BUILD SUCCEEDED **; the plugin lint output reports 0 violations.