Write log to config dir/EmptyEpsilon.log when launched as a Mac app bundle#2734
Merged
daid merged 1 commit intodaid:masterfrom Feb 21, 2026
Merged
Write log to config dir/EmptyEpsilon.log when launched as a Mac app bundle#2734daid merged 1 commit intodaid:masterfrom
daid merged 1 commit intodaid:masterfrom
Conversation
When running a packaged build of EE on macOS through typical end-user/non-development means (double-clicking the icon, running open EmptyEpsilon.app), the log is written to STDOUT, which isn't accessible. Detect when EE is run as an app bundle on macOS, and if so, write EE's log to a file in the config directory (~/.emptyepsilon/EmptyEpsilon.log). This captures log output on macOS dev, server, and player runs for troubleshooting without resorting to running the binary on the command line from within the app bundle. This is also a more similar behavior to running EmptyEpsilon on Windows, which also writes the log to a file unless EE is built in DEBUG mode. Existing development and server/player workflows should be unaffected. Running the binary from within the app bundle (i.e. cd EmptyEpsilon.app/Contents && MacOS/EmptyEpsilon) should still log to STDOUT.
Contributor
Author
|
macOS CI failure doesn't seem related. Build succeeds without errors but it hits an |
Owner
|
The CI failure also happened on master, and I think it's just github action mac runnings changing something again breaking the builds. It's not the first time. |
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
2 participants
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.
When running a packaged build of EE on macOS through typical end-user/non-development means (double-clicking the icon, running
open EmptyEpsilon.app), the log is still written to STDOUT, which isn't accessible.Detect when EE is run as an app bundle on macOS, and if so, write EE's log to a file in the config directory (
~/.emptyepsilon/EmptyEpsilon.log). This captures log output on macOS dev, server, and player runs for troubleshooting without resorting to running the binary on the command line from within the app bundle. This is also a more similar behavior to running EmptyEpsilon on Windows, which also writes the log to a file unless EE is built in DEBUG mode.Existing development and server/player workflows should be unaffected. Running the binary from within the app bundle (i.e.
cd EmptyEpsilon.app/Contents && MacOS/EmptyEpsilon) should still log to STDOUT.