nixpkgs/pkgs/development/compilers/julia
2024-01-11 11:17:34 -05:00
..
patches julia_18{,-bin}: drop as it has reached end of life 2024-01-11 11:17:34 -05:00
1.6-bin.nix julia_16-bin: 1.6.6 -> 1.6.7 2023-12-26 17:05:44 -05:00
1.9-bin.nix julia: add thomasjm as maintainer 2023-12-21 16:17:59 -07:00
1.9.nix julia_18{,-bin}: drop as it has reached end of life 2024-01-11 11:17:34 -05:00
1.10-bin.nix julia_110-bin: init at 1.10.0 2024-01-10 20:01:21 -05:00
1.10.nix julia_110: init at 1.10.0 2024-01-10 21:18:40 -05:00
default.nix julia_18{,-bin}: drop as it has reached end of life 2024-01-11 11:17:34 -05:00
README.md julia: fix URL to building instruction in README 2023-10-25 13:05:58 +02:00

Julia

Julia, as a full-fledged programming language with an extensive standard library that covers numerical computing, can be somewhat challenging to package. This file aims to provide pointers which could not easily be included as comments in the expressions themselves.

For Nixpkgs, the manual is as always your primary reference, and for the Julia side of things you probably want to familiarise yourself with the README , build instructions, and release process. Remember that these can change between Julia releases, especially if the LTS and release branches have deviated greatly. A lot of the build process is underdocumented and thus there is no substitute for digging into the code that controls the build process. You are very likely to need to use the test suite to locate and address issues and in the end passing it, while only disabling a minimal set of broken or incompatible tests you think you have a good reason to disable, is your best bet at arriving at a solid derivation.