Currently the corto buildsystem creates a softlink to an executable in the root of the project directory, so that a user can easily invoke the executable. The actual location of the executable is in $CORTO_TARGET, which is done so it can be started from anywhere on the system using corto run.
On some systems however creating softlinks does not work. This is typically the case when a VM is used, a project is located in a folder that is shared with the host OS and the host OS does not support softlinks (Windows). Currently, the buildsystem fails on creating the symbolic link when this happens.
Instead of failing, the buildsystem should fallback to copying the binary.
Currently the corto buildsystem creates a softlink to an executable in the root of the project directory, so that a user can easily invoke the executable. The actual location of the executable is in
$CORTO_TARGET
, which is done so it can be started from anywhere on the system usingcorto run
.On some systems however creating softlinks does not work. This is typically the case when a VM is used, a project is located in a folder that is shared with the host OS and the host OS does not support softlinks (Windows). Currently, the buildsystem fails on creating the symbolic link when this happens.
Instead of failing, the buildsystem should fallback to copying the binary.