You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found no way to create relative symlink by Create File Link action because, by specs, "if the path is relative, it will be made relative to <%InstallDir%>" for link target.
In most cases this is just not acceptable because the application directory can be mounted (e.g. by NFS) with different names on different hosts, so absolute links became invalid but relative links work.
For example, if I have libicudata.so link to libicudata.so.42.1 in <%InstallDir%>/linux86/lib, then I need link target literally 'libicudata.so.42.1' rather than /home/tim/.../linux86/lib/libicudata.so.42.1
The most straightforward way to fix this is to change the specs (though, of course, this would result in backward compatibility issue).
The text was updated successfully, but these errors were encountered:
I found no way to create relative symlink by Create File Link action because, by specs, "if the path is relative, it will be made relative to <%InstallDir%>" for link target.
In most cases this is just not acceptable because the application directory can be mounted (e.g. by NFS) with different names on different hosts, so absolute links became invalid but relative links work.
For example, if I have libicudata.so link to libicudata.so.42.1 in <%InstallDir%>/linux86/lib, then I need link target literally 'libicudata.so.42.1' rather than /home/tim/.../linux86/lib/libicudata.so.42.1
The most straightforward way to fix this is to change the specs (though, of course, this would result in backward compatibility issue).
The text was updated successfully, but these errors were encountered: