Elliot Saba

I think there are a few separate concerns here: 1. Should `juliaup`'s installer automatically modify `PATH` on Windows and macOS? 2. What should `juliaup` put on the `PATH`? 3. Will...

Does that compilation command run once to create a binary executable that is then redistributed to users, or is that compilation command run on users' machines?

Well, that's tough. 😅 The way the dynamic linker works is that it has certain directories it searches by default (on Linux for instance, it searches `/lib`, `/usr/lib`, `/usr/local/lib`, etc...),...

> Would I need instead to write a plugin that is not linked to libjulia at compile time? Upon loading it, I would pass it the libjulia path, and it...

> I was assuming I'll need to that with all the jl_* entry points, like jl_eval_string(), jl_string_data(). Am I wrong about that? Yes, that's correct. I suggest doing something like:...

So the issue here is that macOS doesn't source your login scripts when it starts the GUI session, which means that us adding paths into `~/.bashrc` or `~/.zshrc` only help...

I no longer get the `ERROR: Maybe we should never reach this?`, but I still get the long backtrace from the CTRL-C, which I think is expected.

Hmmmm, we don't use cygwin; we use mingw32 toolchains. The install scripts for all the software we use in [our docker container](https://hub.docker.com/r/juliapackaging/package-windows-x86_64/tags) are held here: https://github.com/JuliaCI/sandboxed-buildkite-agent/tree/main/windows-kvm/base-image/setup_scripts.

Alright, we finally managed to do some more testing on this on some large core-count Windows machines, and this helps significantly, so I'm going to merge.

Actually, something seemed fishy to me about how much this helped the internal workload, and I just tried the following on Julia v1.8.2: ``` julia> using Distributed addprocs(1) @everywhere begin...