Open antoineB opened 2 years ago
Hmm, not sure - haven't really used geiser yet, but happy to make accommodations if we figure out we need some.
Oh, if you men because it can't find the shared libs, then whehter or not that should work without any extra adjustment likely depends on how you built/installed lokke (plus or minus any bugs we might need to fix).
In general I believe ./lokke
should just work, as should lokke
when run from the bin/
directory after a make install
. Anything else will likely need some assistance from environment variables.
I used (setenv "LD_LIBRARY_PATH" "~/lokke/lib/.libs")
in emacs didn't seems to work but
export LD_LIBRARY_PATH=~/lokke/lib/.libs
emacs
seems to work.
By the way I didn't understand the difference between :
lok
lokke
bin/lok-0
bin/lokke-0
antoineB @.***> writes:
I used
(setenv "LD_LIBRARY_PATH" "~/lokke/lib/.libs")
in emacs didn't seems to work but
Hmm. Is that a make install
tree, or a source tree? Guessing a
source tree, but that shouldn't matter.
Assuming it's a source tree, what happens if you run (cd && ~/lokke/lokke)
? That works here without any LD_LIBRARY_PATH
set, and
so I'd think it should work from emacs too...
Oh, and what version of guile are you using?
By the way I didn't understand the difference between :
lok
lokke
bin/lok-0
bin/lokke-0
The manpage should explain in more detail, e.g. via man -l lokke.1
from the source tree, but generally:
lokke
: general command supporting subcommands like help
, run
, ...lok
: like clojure clj
, but more accurately a shortcut for lokke run
.lokke-0
and lok-0
: versioned flavors of lokke
and lok
.The versioned flavors should be used in any non-interactive invocations,
e.g. #!/usr/bin/lokke-0
, etc., so that they won't break if/when we
make backward incompatible changes (which we'd introduce via lokke-1
,
lokke-2
, etc.).
Just checking back to see if this is still relevant.
I am struggling to setup geiser properly, especially regarding to the .so files.