$(OutDir)/$(RemoteOutDir) problem about vslinux HOT 5 CLOSED

I have managed to workaround the problem by redefining $(OutDir) with the macro. Just curious why redefining RemoteRootDir does not work. BTW VS Add Macro window misbehaves. At least on two monitors (different sized) over RDP -- it opens behind the screen.

from vslinux.

And I get the error message from the VS --
MSBuild\Microsoft\VC\v160\Application Type\Linux\1.0\Linux.targets(192,5): error : Exception occured while copying sources to remote machine - Could not create directories, mkdir exit code: 1

it cannot copy cpp sources in Dir1 and Dir2 for the following structure:
Dir
-Dir1
-Dir2

I have three projects here: a kind of a front-end in Dir and two back-ends Dir1 and Dir2. VS manages to copy complex header file structures correctly but it fails on cpp files in Dir1 and Dir2 with the error as above.

from vslinux.

Heh, it looks like the directory you choose to copy source files of a project to heavily depends upon where the files of the project lie. So depending which directories the project references through the files it consists of the magic "Remote Build Project Directory" may be $(RemoteRootDir)/, $(RemoteRootDir)/$(ProjectName)/ or $(RemoteRootDir)/SomethingSpecial. And this weirdness is vitally essential for the VS to be able to copy files right and to call g++ right. The last necessity makes it impossible to use a thirdparty file sync tool -- I would be able to copy files right but compilation fails.

from vslinux.

I also found out that you should not use the ~ for dynamically home path. If the build and debug machine are different and have different users, visual studio looks under the ~ path of the debug machine on the build machine to deploy the file. Another thing is the new linker property page. There are two Output file entries.
The upper one is a path relative to the root folders (root project, root build and root deploy folders) where the output file shall be put to.
The second Output File entry goes for the absolute path where the output file lies on the build machine during deploy time.

from vslinux.

This issue is being closed because we are no longer tracking VS Linux issues on GitHub. If the issue still reproduces, bugs and new suggestions should be reported on the Developer Community forum. It is centralized, better equipped for group voting, and has more visibility.

from vslinux.