16:47:21sjlShinmera: Have you tested deploy on the newest OS X? I can't seem to get the OS X app building working.
16:47:50sjlShinmera: I can build a normal executable with :build-operation "deploy-op", and that runs as I expect
16:48:26sjlShinmera: when I use "osx-app-deploy-op" and run the resulting binary from the command line, e.g. `./build/foo.app/Contents/MacOS/foo` this also runs as I expect
16:48:53sjlShinmera: but when I actually try to open the .app, via double clicking or `open foo.app` from the command line, it silently hangs at 100% CPU until I force kill it
17:13:31d4ryusJosh_2: i think sjl was refering to https://en.wikipedia.org/wiki/Rubber_duck_debugging
17:13:39scymtymJosh_2: explaining a problem to somebody or to nobody at all (or to a rubber duck, hence the name) and gaining some insight just from stating the problem from the beginning
20:10:13sjlShinmera: the problem was I was running the wrong app. previously I was building with my own script, using a Roswell-installed version of SBCL
21:09:03drmeisterI've added a dependency of 'esrap+sbcl' to building clasp - now I have the headache of figuring out how to ensure that it is available.
21:09:50Shinmeradownload the quicklisp.lisp file, run quicklisp-quickstart:install with the directory set to something local to the build
21:10:23jackdanieldrmeister: if you depend on some particular libraries, just use (ql:bundle-systems '(esrap) :to "clasp/sbcl-build/libraries")