If you use relative paths that’s relative to the root or the git repo, not to the project file.
Probably the easiest way to get the right path is:
- Git Clone the repository into a new directory on your Mac/Linux and
cd into that directory. E.g.:
git clone URL /tmp/repotest && cd /tmp/repotest
- Then check the relative path from there. A quick and simple test from the Terminal/Command line:
ls -alh ./rel/path
If you get something like:
ls -alh ./configs/paths.go
-rw-rw-r-- 1 viktorbenei viktorbenei 5,6K jun 29 13:10 configs/paths.go
Then the relative path is right (
./configs/path.go in the above example). If you get something like:
ls -alh configs/paths2.go
ls: cannot access 'configs/paths2.go': No such file or directory
Then the relative path is incorrect.
I hope this helps, if you have any questions just let us know!