4 ms·

I'm pretty excited about Julia and integrating it into existing infrastructure[0]. The build process though -- even the "release" seems to insist on running git

by bch 12y ago

I'm pretty excited about Julia and integrating it into existing infrastructure[0]. The build process though -- even the "release" seems to insist on running git to pulldown code/data from the network -- if Julia devs/release-managers are reading -- what are odds of getting standalone distributions ? [0] https://news.ycombinator.com/item?id=7173137 https://news.ycombinator.com/item?id=7173137

one-more-minute 12y ago
We're actually working on static compilation right now, so that you'll be able to compile Julia code to a small binary and distribute it without the runtime. It should be completed over the summer.
- dnautics 12y ago
  Is there any word on Julia for the arm? To use my programs on rpi As it is I have to convert to octave (not hard) but the for loops are slooow.
  - StefanKarpinski 12y ago
    Isaiah Norton recently got Julia minus some of the external libraries working on ARM [1], but there's still a lot of work to be done. But it is certainly not impossible. [1] https://github.com/JuliaLang/julia/issues/3134#issuecomment-41510527 https://github.com/JuliaLang/julia/issues/3134#issuecomment-...
    - dnautics 12y ago
      awesome! I know that BLAS is now working on ARM. My RPi debian distro came with mathematica.
- bch 12y ago
  Unless I misread, I think you misinterpretted my question: what I'm wanting to do is compile a libjulia.so and link against it, and submit code to it and collect the results. Grabbing either the git master tip, or even .tgz "distribution" and trying to compile that results in git being fired up and pulling in _something_ new. Can that "something" be included in a distribution so I can effectively just: ./configure; make; make install without git, and without hauling down more code/data over the network ?
  - ihnorton 12y ago
    There are two different questions here. See my post above for the "link against libjulia" part (possible, not turnkey yet, probably still some warts to work out). For compilation without internet access: yes, that is possible. There is a special "make source-dist" target which will grab everything you need (see https://github.com/JuliaLang/julia/blob/master/DISTRIBUTING.md https://github.com/JuliaLang/julia/blob/master/DISTRIBUTING....). We are not distributing this bundle ourselves right now, but it's worth considering for the next release version.
    - bch 12y ago
      make source-dist sounds promising. I know we've been cross-posting threads, but I'll just thank you here. :)
ihnorton 12y ago
The release version is right now relatively minimal [1]: just the repl/compiler, some pure-Julia libraries, and a few important external libraries like OpenBLAS and FFTW. git is bundled to allow installation of additional functionality, and inclusion of git and the integrated "Pkg" system also help facilitate new contributions - which is important at this stage! There has been discussion of the idea of a larger "platform" distribution including snapshots of various important packages, so that more extensive functionality is available in a single installer. No timeframe promises, but it is on the radar, and this will be very important for the next phase of adoption. Regarding the "call Julia from C" question in the post you linked, this is technically possible, but not turnkey: https://groups.google.com/d/msg/julia-dev/qdnggTuIp9s/BoQSNGNXxV0J https://groups.google.com/d/msg/julia-dev/qdnggTuIp9s/BoQSNG... [1] As compared to default-install of some other technical environments. There is also a contingent pushing for a much more minimalist distribution for language-only/non-mathy applications!
- bch 12y ago
  re: call Julia from C -- understood -- that part I'm happy to hack w/ and see what happens. Regarding git for a build phase -- (because it's difficult to read emotional intent on the internet, let me say: I appreciate this work on Julia, and how difficult project management is. Much respect. But...) I think I disagree with you about what a "distribution" is - it should be a snapshot, and whether there are two versions (base, "batteries installed"), or additional packages to optionally install later is inconsequential - a "distribution" should be self-contained and fully baked. The devs/hackers can pull from tip of master and get the "live" build scripts, but that shouldn't be included a release -- release != repository. Again, much respect. Consider my comment food for thought.
  - ihnorton 12y ago
    (We're both mixing threads - see below!). No worries at all :) I understand what you mean now, and I've spent enough time in places with slow/no internet connectivity, so I'm very partial to the idea. I'll file an issue about it and see what other folks think.

by bch 12y ago

one-more-minute 12y ago

We're actually working on static compilation right now, so that you'll be able to compile Julia code to a small binary and distribute it without the runtime. It should be completed over the summer.

dnautics 12y ago
Is there any word on Julia for the arm? To use my programs on rpi As it is I have to convert to octave (not hard) but the for loops are slooow.
- StefanKarpinski 12y ago
  Isaiah Norton recently got Julia minus some of the external libraries working on ARM [1], but there's still a lot of work to be done. But it is certainly not impossible. [1] https://github.com/JuliaLang/julia/issues/3134#issuecomment-41510527 https://github.com/JuliaLang/julia/issues/3134#issuecomment-...
  - dnautics 12y ago
    awesome! I know that BLAS is now working on ARM. My RPi debian distro came with mathematica.
bch 12y ago
Unless I misread, I think you misinterpretted my question: what I'm wanting to do is compile a libjulia.so and link against it, and submit code to it and collect the results. Grabbing either the git master tip, or even .tgz "distribution" and trying to compile that results in git being fired up and pulling in _something_ new. Can that "something" be included in a distribution so I can effectively just: ./configure; make; make install without git, and without hauling down more code/data over the network ?
- ihnorton 12y ago
  There are two different questions here. See my post above for the "link against libjulia" part (possible, not turnkey yet, probably still some warts to work out). For compilation without internet access: yes, that is possible. There is a special "make source-dist" target which will grab everything you need (see https://github.com/JuliaLang/julia/blob/master/DISTRIBUTING.md https://github.com/JuliaLang/julia/blob/master/DISTRIBUTING....). We are not distributing this bundle ourselves right now, but it's worth considering for the next release version.
  - bch 12y ago
    make source-dist sounds promising. I know we've been cross-posting threads, but I'll just thank you here. :)

ihnorton 12y ago

The release version is right now relatively minimal [1]: just the repl/compiler, some pure-Julia libraries, and a few important external libraries like OpenBLAS and FFTW. git is bundled to allow installation of additional functionality, and inclusion of git and the integrated "Pkg" system also help facilitate new contributions - which is important at this stage! There has been discussion of the idea of a larger "platform" distribution including snapshots of various important packages, so that more extensive functionality is available in a single installer. No timeframe promises, but it is on the radar, and this will be very important for the next phase of adoption. Regarding the "call Julia from C" question in the post you linked, this is technically possible, but not turnkey: https://groups.google.com/d/msg/julia-dev/qdnggTuIp9s/BoQSNGNXxV0J https://groups.google.com/d/msg/julia-dev/qdnggTuIp9s/BoQSNG... [1] As compared to default-install of some other technical environments. There is also a contingent pushing for a much more minimalist distribution for language-only/non-mathy applications!

bch 12y ago
re: call Julia from C -- understood -- that part I'm happy to hack w/ and see what happens. Regarding git for a build phase -- (because it's difficult to read emotional intent on the internet, let me say: I appreciate this work on Julia, and how difficult project management is. Much respect. But...) I think I disagree with you about what a "distribution" is - it should be a snapshot, and whether there are two versions (base, "batteries installed"), or additional packages to optionally install later is inconsequential - a "distribution" should be self-contained and fully baked. The devs/hackers can pull from tip of master and get the "live" build scripts, but that shouldn't be included a release -- release != repository. Again, much respect. Consider my comment food for thought.
- ihnorton 12y ago
  (We're both mixing threads - see below!). No worries at all :) I understand what you mean now, and I've spent enough time in places with slow/no internet connectivity, so I'm very partial to the idea. I'll file an issue about it and see what other folks think.