Re: ECL + EQL Standalone Binary

John, I think Pascal means that you will need to use (cffi:load-library "path/to/library") in your code, and if you happen to bundle your dylibs with your .app then you can at least find them there.  One problem that I haven't found a good answer to is if your libs have explicit path referenc

Re: ECL + EQL Standalone Binary

The behavior you're seeing r.e @executable_path et al is osx behavior.  I can't find a list of all of the supported "macros" but this gives an example of what is going on. Loosely, executables have the paths to the dylibs th

Re: ECL + EQL Standalone Binary

change it? Should I reinstall ECL in a different way? -John On Sep 26, 2017, at 10:45, Joshua Kordani <mailto:jkord...@lsa2.com>> wrote: The behavior you're seeing r.e @executable_path et al is osx behavior.  I can't find a list of all of the supported "macros"

Re: ECL + EQL Standalone Binary

(compatibility version 1.0.0, current version 400.9.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.0.0) -John On Sep 26, 2017, at 12:56, Joshua Kordani <mailto:jkord...@lsa2.com>> wrote: I cant speak to whether or not ecl is correctly built, but what is