-
-
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
Change absolute symlinks resulting from build to relative? #9502
Comments
If it works everywhere, sure, worth trying. It might be that NTFS junctions require absolute paths, I forget the exact reason. To point people in the right direction, these are created by Line 29 in 3758b81
Lines 801 to 820 in 837611a
|
moving a build root is not in general possible without a complete wipe of all of the dependencies also, since most build systems enforce that the install target be an absolute path. |
right, forgot about all the rpath and install_name_tool manipulations we have to do. so maybe this is a case of "don't do that"? |
yes. plus the absolute path gets hardcoded into the autotools and cmake build files in deps. i'm not really sure there a good way around that either (perhaps if everything is cmake?) |
|
good to know. closing this as "nobody with a moderately complex build system allows this because it's considered too insane and dangerous" |
But note that we went to great lengths with @staticfloat to ensure that you can change (Though all of this applies to the result of |
Consider the results of the following build (via
git clone
) where julia was cloned into/Users/seth/dev/julia/julia
(the "clone root"):These links use absolute paths, so that relocating the clone root is now impossible*.
Much better, if possible, would be to create the symlinks relative to the clone root, like so:
*impossible in that things break. See #9493 (comment) for an example.
The text was updated successfully, but these errors were encountered: