Wow, thank you so much for figuring all of that out. I tried to make the
changes you suggested, and I'm still running into errors, but I'm not sure I
have the exact version of str that you do, so I imagine that is the reason. I
was able to make a build with a different package ("vector") and it
Le 10/02/2023 à 19:50, Brandon Hale a écrit :
Don't be confused by the various implementations of helloword in that
project. Look at the Makefile, only the lisp files are used when
compiling with ecl.
One thing I am confused about with this are all of the #-(and) in
generate.lisp. I know the
I think that you should not call quickload in the package file. ASDF should
solve depenencies based on a sole (ql:quickload 'cl-i3).
I've tried to reproduce your issue and I've succeeded. After quick
investigation it seems that the system cl-str expects that its
source code will be available to
Maybe I should get my project up in a repo, but it looks like I have the
dependency listed. Here is my package's .asd named cl-i3.asd:
(asdf:defsystem #:cl-i3
:name "cl-i3"
:description "A replacement for i3status written in Common Lisp."
:author "Brandon Hale"
:license "GPLv3"
:v
Don't be confused by the various implementations of helloword in that
project. Look at the Makefile, only the lisp files are used when
compiling with ecl.
One thing I am confused about with this are all of the #-(and) in
generate.lisp. I know the #+ecl means only run this in ecl, but what do
Le 10/02/2023 à 01:07, Brandon Hale a écrit :
ecl produces elf binaries. You will want to compile, and link all
your code into this executable file. So you don't need to load asdf or
anything else at run-time (in the prologue-code). Instead, you load
asdf, quicklisp, and your code, when you g
Hello Brandon,
--- Original Message ---
On Friday, February 10th, 2023 at 00:20, Brandon Hale
wrote:
> Hello all,
>
> I apologize if this is either the wrong place to get help with ecl, or if
> this is asked all of the time.
this is the right place, don't worry :)
> I've written
ecl produces elf binaries. You will want to compile, and link all
your code into this executable file. So you don't need to load asdf or
anything else at run-time (in the prologue-code). Instead, you load
asdf, quicklisp, and your code, when you generate the executable with
make-build.
Have
Le 10/02/2023 à 00:20, Brandon Hale a écrit :
Hello all,
I apologize if this is either the wrong place to get help with ecl, or
if this is asked all of the time. I've written a small replacement for
i3status with common lisp and want to use ecl to make a binary so when
i3wm loads, it just loa
Hello all,
I apologize if this is either the wrong place to get help with ecl, or
if this is asked all of the time. I've written a small replacement for
i3status with common lisp and want to use ecl to make a binary so when
i3wm loads, it just loads the cl-i3status binary. I've looked at the e
10 matches
Mail list logo
