console log for Setup wizard problems
gperciva opened this issue · comments
Trying to debug #165, I ran into the problem that
open ./Tarsnap.app
(as suggested by INSTALL) doesn't display log messages on the command line. Instead, to figure out what was breaking, I had to run the undocumented
./Tarsnap.app/Contents/MacOS/Tarsnap
It would be nice if we could see the log (when the app is launched normally) if something goes wrong. On OSX, this might mean a top-bar menu item, but of course that wouldn't work on most linux window managers.
At the moment I don't have a great idea for how to solve this in a cross-platform manner, but I'll come back to it later.
I wrote a bin/tarsnap-gui shell script which always appends output to ~/Library/Logs/tarsnap-gui.log on macOS and ~/tarsnap-gui.log on other platforms.
The bin/ directory is correctly copied to ./Tarsnap.app/Contents/MacOS/bin/, but I'm not sure yet how to coax qmake into generating a Tarsnap.app that runs ./Tarsnap.app/Contents/MacOS/bin/tarsnap-gui instead of ./Tarsnap.app/Contents/MacOS/Tarsnap whenever the user opens Tarsnap.app.
bin/tarsnap-gui is symlinked to /usr/local/bin/tarsnap-gui by the new homebrew cask formula, and the automatic job scheduler uses it, at least.
I'll figure out the correct solution tomorrow.