-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
binary installers #236
binary installers #236
Comments
Mac turned out to be easy. The package just installs a julia-mac directory in the home directory, which can be uninstalled by simply deleting it. For linux, I think we should just release a tar.gz that people can install wherever they want. I could have made a debian package, but I no longer a debian maintainer. That will automatically happen. RPMs are painful, and you have all these dependencies that can only be resolved with yum. We are better off with a self-contained tarball on linux, which is statically linked. -viral On Oct 20, 2011, at 11:09 AM, Stefan Karpinski wrote:
|
You're probably right for Linux. Since we include all our own libraries, it should be easy enough to just download a tarball of a precompiled Julia directory with the |
We can put quick instructions wherever the download link is. |
Need a target that builds a statically-linked julia-release-readline. |
We can build statically since commit 475b8ea. The install directory also creates a self-contained tarball that can work out of any directory. Eventually, once we get some traction, debian packages, RPMs, Mac dmgs etc. will get done. For now, a tarball is sufficient. |
When I move my julia directory and untar one of these tarballs, I still get this:
|
Ok, got it to work by setting LD_LIBRARY_PATH: |
Is there any way we could statically link in all of the libraries in lib/ since we always load them? Then we could just have a single fat binary, which would be kind of nice and simple. |
Wait a second, our own dlopen should automatically look in |
Yes, we could do that for default libs. Seems avoidable though. But, I did not encounter this problem in all my testing. I think the current solution should work just fine. Do you have some environment variables that are interfering, like Jeff suggested? On 30-Oct-2011, at 10:36 PM, Stefan [email protected] wrote:
|
I believe that this variable is not recognized by os x, unless it is a recent change in lion. Usually it is DYLD... On 30-Oct-2011, at 10:31 PM, Stefan [email protected] wrote:
|
This trouble was all from the fact that I do set JULIA_HOME. I now simply don't do that and everything is fine. Sorry for the ruckus. |
Ok - but this is good to know. -viral On Mon, Oct 31, 2011 at 11:17 AM, Stefan Karpinski
|
…1061ecc (#55615) Stdlib: Downloads URL: https://github.com/JuliaLang/Downloads.jl.git Stdlib branch: master Julia branch: backports-release-1.11 Old commit: a9d274f New commit: 1061ecc Julia version: 1.11.0-rc2 Downloads version: 1.6.0(It's okay that it doesn't match) Bump invoked by: @IanButterworth Powered by: [BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl) Diff: JuliaLang/Downloads.jl@a9d274f...1061ecc ``` $ git log --oneline a9d274f..1061ecc 1061ecc Fix setting atexit. Fixes trailing download tasks during precompilation (#257) b871386 Add debug information to `setopt` commands (#248) 51e5321 fix: use invokelatest for easy_hook, avoid race (#241) 05f9ec2 make precompile workload relocatable (#236) 2dd891a Hardcode doc edit backlink (#232) ``` Co-authored-by: Dilum Aluthge <[email protected]>
To release and expect more than a handful of hardcore users to try Julia, we need easy binary installers. Viral said he's done this on OS X before. Not sure what we can do on Linux — RPMs? Debian packages?
The text was updated successfully, but these errors were encountered: