Hi folks, I’ve seen this notion pop-up repeatedly about wanting small binaries created within the Julia ecosystem. I personally have been quite confused about this desire due to probably not working in a space where having small binaries is desired. My mental oversimplification of this problem is t…

Hey folks! Thank you so much for the explanations! Just to summarize what I’ve learned here about the desire for small binaries is that small binaries: Support easier distribution of Julia programs or tools through package managers (per @lmiq ) Enable usage in contexts where storage space is an im…

Embedded systems were mentioned before, and that requires cross-compilation, right? My bigger question is what and where these assumptions about running the code on the same machine as the compiler are. My completely uninformed impression is that Julia is compiled to LLVM, which can be further comp…

Here’s one: when you encounter Sys.iswindows(), is that a compile time query or a runtime query? if Sys.iswindows() include(raw"C:\more\code\to\compile.jl") end is relevant for compilation time (it might be just filesystem navigation for the purpose of finding the source files), but function …

Yes, that’s a good example. It’s not impossible to solve, e.g. we could have an AbstractInterpreter that takes these things into account when “evaluating” them and either give a warning or insert appropriate runtime checks. The easier way is to not try to statically compile such code, which is ultim…

I don’t care about “small” shared libraries. I’ll be happy if it becomes truly convenient to produce hundred-megabyte sized shared libraries to be used from C/C++ I’ve run into strange bugs when calling Julia code as a shared library from C/C++. I may be wrong but eventually I concluded that it was…

Please do file an issue about such reproducible bugs, so that they can be fixed :slight_smile: Not to derail the thread, but julia uses libuv internally for printing & IO abstraction, so any issue with julia ought to occur with pure libuv as well.

Does the environment variable JULIA_CPU_TARGET affect package images as well? This would at least allow potential cross compilation between microarchtectures on the same platform I think.

[image] Sukera: julia uses libuv internally for printing & IO abstraction, so any issue with julia ought to occur with pure libuv as well. If my C/C++ application already uses stdio / iostream for IO, maybe it’s problematic to link with any other library (julia.h or otherwise) which loads lib…

This is extremely important to make Julia viable as a scripting language. Of course, one would say it is not the right tool for the job, but why not use your favourite language for everything? :slight_smile: For that end, I am probably more keen on having small memory footprints than small binaries…

[image] takbal: To give an example, I run a small Julia script to record my home automation states. It feels quite a big waste. Julia does not even start below 100-200 MB of RAM usage, and adding a few packages grows your sysimage to a multiple of that in no time. Do it larger scale, and even a …

Could Someone Explain To Me the Desire for Small Julia Binaries?

General Usage

greatpet March 25, 2023, 6:19pm 29

Thanks for the advice. My problem was described in this post. Let me know if there’s something obvious that I missed. Otherwise, I’ll go on to file a github issue.

Topic		Replies	Views
Roadmap for small binaries Internals & Design question	126	12310	November 10, 2024
Building stand-alone helloworld produces many dlls, being 200MB big New to Julia	37	6345	November 18, 2021
How do I create a binary from .jl files? New to Julia	34	7219	May 11, 2022
Statically compiled and statically linked General Usage	35	9902	September 8, 2020
Compiling to exe New to Julia question	34	13301	December 18, 2022

Could Someone Explain To Me the Desire for Small Julia Binaries?

Related topics