I've been working with MinGW for quite some time and I've sensed the
unholiness as well.
Thank you for showing me how to ship specific modules with ECL!
Best regards,
Binh Nguyen
On Thu, 23 Mar 2023 at 22:20, Daniel Kochmański
wrote:
> It seems that for mingw we do some unholy mashup between
It seems that for mingw we do some unholy mashup between posix and window
-specific options, that is we do a flat structure instead of a tree
(/usr/loca/bin etc). In that case you are expected to ship all your modules in
the same directory as the application (quite like with dll files when they
Hi Daniel,
＿|￣|○
Thank you for your reply!
Yep, I passed "--prefix=/usr/local/" to configure and then performed make
install afterwards, as per the notes on Autoconf based configurations.
(https://ecl.common-lisp.dev/static/manual/Building-ECL.html#Building-ECL)
I agree, I think there is someth
Hey Binh,
it is not that the function REQUIRE is not available, it is that it doesn't
know /where/ to look for sockets.fas. I see that you have unix pathnames, so
ecl should not expect the flat structure. Did you pass "--prefix=/usr/local/"
to configure (or something in this spirit)? If so, did
Dear ECL Community,
Could you let me know how to do the following, please?
- How to load file "quicklisp.lisp" in an embedded instance of ECL
- How to make the function REQUIRE available in an embedded instance of ECL
- How to load ASDF 3 or newer in an embedded instance of ECL
I am able to load
