[Bug] SDK confused by symlinks in paths
asked 2014-06-21 17:07:39 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
As there seems to be no bug tracker, I'll post this here for reference.
Problem: The SDK gets confused if there are symlinks in the paths provided during installtion. In my case, I had a symlink from /home to /mnt/home, and I couldn't build the Hello World application. The less than helpful error message was "Project is outside of shared home (home path) and shared src (source path)".
I tried a re-installation with expanded paths, but it still didn't work, probably because $HOME and the expanded paths were still overlapping partly.
Background: The Mer SDK builds apps in a second virtualbox different from the emulator (would have been nice if that had been explained somewhere), probably to guarantee a consistent build environment. That means paths must be translated from the host to the virtual box. This seems to be done by "merssh". Apparently this translation runs into problems when symlinks are involved or the paths overlap in an unexpected way.
Solution: I re-installed with paths for apps and SailfishOS that were disjoint from $HOME and had the symlinks expanded.
