You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@alex-nicholas I couldn't see any use of ~ hardcoded into the makefiles. When you get a chance could you please send me a screenshot or log of the error messages you're seeing. No rush.
The text was updated successfully, but these errors were encountered:
This is the bash output attempting to run make run-local in the project I'm working in. This may be specific to the makefile in this project more than make itself.
/usr/bin/sh: line 1: find-first-matching-file: command not found
/usr/bin/sh: line 1: find-first-matching-file: command not found
/usr/bin/sh: line 1: find-first-matching-file: command not found
/usr/bin/sh: line 1: find-first-matching-file: command not found
/usr/bin/sh: line 1: find-first-matching-file: command not found
/usr/bin/sh: line 1: find-first-matching-file: command not found
/usr/bin/sh: line 1: git-find: command not found
/usr/bin/sh: line 1: git-find: command not found
/usr/bin/sh: line 1: git-find: command not found
/usr/bin/sh: line 1: git-find: command not found
/usr/bin/sh: line 1: git-find: command not found
/usr/bin/sh: line 1: git-find: command not found
make: *** No rule to make target `next-dev', needed by `run-local'. Stop.```
After some quick experimentation on Alex's machine, it seems that sub shells under git-bash are not inheriting the environment variables of the parent shell.
@alex-nicholas I couldn't see any use of
~
hardcoded into the makefiles. When you get a chance could you please send me a screenshot or log of the error messages you're seeing. No rush.The text was updated successfully, but these errors were encountered: