-
-
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
Fix errors: conrtib/build_{executable,sysimg}.jl #14176
Conversation
Cc: @nalimilan |
println("running: rm -rf $(tmpdir) $(sys.buildfile).o $(sys.buildfile0).o $(sys.buildfile0).ji") | ||
map(f-> rm(f, recursive=true), [tmpdir, sys.buildfile*".o", sys.buildfile0*".o", sys.buildfile0*".ji"]) | ||
println("running: rm -rf $(tmpdir) $(sys.buildfile * ".o") $(sys.buildfile0 * ".o") $(sys.buildfile0 * ".ji")") | ||
run(`rm -rf $(tmpdir) $(sys.buildfile * ".o") $(sys.buildfile0 * ".o") $(sys.buildfile0 * ".ji")`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use the julia rm
function, not the coreutils rm
which is not going to be present on windows
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done, thanks.
@ViralBShah Did you mean to CC somebody else? I've no particular knowledge about this file. |
a3a1ef0
to
fc7621b
Compare
@dhoegh has been pretty actively maintaining a version of this at https://github.com/dhoegh/BuildExecutable.jl - it might be worth actually migrating so there aren't 2 separate copies of this going forward |
Yes I would deferentially appreciate the help at https://github.com/dhoegh/BuildExecutable.jl . I have already fixed some of the issues mentioned here. I support the idea of removing |
@dhoegh great work. |
My opinion is that |
That makes sense to me. sysimg is needed if you want to make a change to base source and actually have it take effect, which can be a bit counterintuitive for newcomers. |
fc7621b
to
bb4efd0
Compare
I think this PR is ready to merge, I've migrated the change to @dhoegh's https://github.com/dhoegh/BuildExecutable.jl at dhoegh/BuildExecutable.jl#6 . |
Note the travis errors, |
Done, thanks. @tkelman |
04d5dbc
to
1282a86
Compare
Travis failure was an unrelated repl test issue caused by fb48014. Thanks for the contribution! |
Fix errors: conrtib/build_{executable,sysimg}.jl
Could the changes to |
I guess? The debug flag is a bit feature-y. |
I see. If this got backported I would be able to get rid of the local copy of |
I thought the osx fix that did get backported was enough for that? What does having the debug flag fix? |
In dhoegh/BuildExecutable.jl#6 @KDr2 states that
|
In a source build you might only have release but not debug present, or maybe the other way around. I'm a bit skeptical of some of the changes over there with respect to JULIA_HOME, you should not be setting that environment variable or modifying it. |
|
Don't set |
Yes, don't set But sometimes the
Or we can simply and clearly write this down into the document. |
That environment variable is significant to the julia runtime, so it shouldn't be used for arbitrary other purposes. That significance should be documented, or possibly removed if the original reasons for it are no longer applicable. |
--debug
option--portable
to build a portable executable file which can be run with LD_LIBRARY_PATH and JULIA_SYSIMG environment var set.