Use relative symlink for AOTC

In VD cases, an app is temporarily installed in a temporal location
and then moved to its actual location during device booting.

When the app is installed at the temporary location, if AOTC runs,
it creates internal symlinks for ni.dll and pdb.
If these symlinks are created based on absolute paths,
they will point to incorrect locations when the app's position changes later.

To resolve this issue, modify the code so that symlinks are generated using relative paths.

diff --git a/NativeLauncher/tool/ni_common.cc b/NativeLauncher/tool/ni_common.cc
index b144185..f5a00da 100644 (file)
--- a/NativeLauncher/tool/ni_common.cc
+++ b/NativeLauncher/tool/ni_common.cc
@@ -427,7 +427,7 @@ static ni_error_e makePdbSymlinkForNI(std::string dllPath, std::string niPath)
                if (exist(pdbPath)) {
                        std::string targetPDBPath = changeExtension(niPath, ".ni.dll", ".pdb");
                        if (!exist(targetPDBPath)) {
-                               bf::create_symlink(pdbPath, targetPDBPath);
+                               bf::create_symlink(concatPath("..", getFileName(pdbPath)), targetPDBPath);
                                copySmackAndOwnership(pdbPath, targetPDBPath, true);
                        }
                }
@@ -691,7 +691,7 @@ static void renameAppNITmpPath(NIOption* opt)
                                        std::string niFile = ni.path().string();
                                        if (isNativeImage(niFile)) {
                                                std::string dllFile = changeExtension(niFile, ".ni.dll", ".dll");
-                                               bf::create_symlink(niFile, dllFile);
+                                               bf::create_symlink(getFileName(niFile), dllFile);
                                                copySmackAndOwnership(niFile, dllFile, true);
                                        }
                                }