Source control problem with new Catalina-enforced symlinks

FMOD Studio
1

So, like many teams, after Catalina, we had to create a symlink to our ‘/projects’ folder called ‘/Users/Shared’ to get around the can’t-write-to-root problem.

But Perforce still knows it is dealing with ‘/projects’.

But Studio is asking Perforce to save a file in ‘Users/Shared’.

Any advice other than giving up on version control integration? :frowning:

2

Resolved this by making a new Perforce workspace with the REAL path instead of the symlink path.