The biggest obstacle to having the interpreter available in distribution package is that it doesn’t work with a compiler statically linked against musl libc. Static musl doesn’t provide libdl which we use for loading dynamic libraries at runtime into the interpreted program. But we’re using exactly…

[image] straight-shoota: it doesn’t work with a compiler statically linked against musl libc Could we at least make it work for Mac? I don’t think we are using libmusl there. I also don’t understand why what’s the issue with the interpreter and static/dynamic libraries. @straight-shoota coul…

[image] zw963: Yes, this is my concern, if not enable it, new guys like me don’t know i can try play code in a REPL, that will help a lot when start to study one new programming language. But that’s just the thing: At this point, the interpreter is still in its infancy and has lots of rough e…

[image] asterite: Could we at least make it work for Mac? I don’t think we are using libmusl there. Yes, on MacOS distribution of the interpreter should not pose a problem. [image] asterite: I also don’t understand why what’s the issue with the interpreter and static/dynamic libraries. @…

[image] straight-shoota: That only works for shared libraries, but not for static libraries or plain object files. Are we using static libraries everywhere? (for the compiler distribution)

LLVM bindings use llvm_ext.o. Most of our distribution packages ship a custom build of libgc.a. We have a workaround in place for the latter: crystal/context.cr at 8948404a4debdd25204f81f3e86caee173a950a2 · crystal-lang/crystal · GitHub

I’m quite late to this thread, but I’m learning more about the interpreter and I’m blown away by how much of a value add it would be to use. Enabling interpreter support for our linux packages would require a major change to our distribution packaging system. We would need to recompile (or at leas…

Following is some simple describe based my own build script (static and dynamic) static: at first, you need setup a alpine build environment, check following dockerfile. ▶ dockerfile then use following command build it. ▶ build static binary dynamic: ▶ build dynamic binary You can check Makefil…

Thanks! I think I was overthinking it a bit. I went ahead and made a tool that aims to produce different kinds of platform packages. dynamically linked with runtime dependencies installed during installation statically linked (not implemented) dynamically linked with all dependencies provided (m…

[image] skinnyjames: Looking at All required libraries · crystal-lang/crystal Wiki · GitHub but I’m not sure it captures everything needed for shipping a Crystal interpreter. It should be pretty accurate. The interpreter also needs libffi which isn’t mentioned there. However, this is all a b…

Do we need libdl? Would it be possible to use something smaller like libltdl ?

Shipping the interpreter

Crystal Contrib

straight-shoota October 22, 2024, 9:50pm 30

There’s a trick that allows fully-portable yet dynamically linked builds. This could allow us shipping portable builds with the interpreter.

Topic		Replies	Views
Latest version is w/o interpreter Help & Support	7	925	February 28, 2023
Crystal 1.7.0 released Official release	10	1192	January 12, 2023
Portable, dynamically linked packages on Linux Crystal Contrib	3	530	September 24, 2024
Why people leaving crystal? Community	95	13408	July 21, 2023
What's up with the Debian packages? Help & Support	28	1722	August 14, 2023

Shipping the interpreter

Related topics