The feature you were referring to in the previous post is not what you thought. Here’s what you observed:
- Cloning a project on Linux creates a symlink, builds successfully.
- Cloning it on Windows creates a file with a path as its only content instead of the symlink.
- This doesn’t build on Windows.
Your hypothesis to explain these was that there was a feature that lets you create a regular file with a path in it and use that as your source, or in other words:
But this isn’t the case; there is no such feature. The true explanation for the behavior you observed was that checking out the build on Linux created the symlink, and therefore the build was successful, whereas your checkout on Windows did not create a symlink, and therefore the build didn’t work.
Therefore taking out the symlink will not fix the issue you’re having; it will just make it so you also have the issue on Linux. You must use more symlinks to fix the issue, not fewer. The other possibility is to point the source property directly to a real directory containing the sources, so that the symlink is not needed.