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
Hey,
Nice to see neptune in the public now! Wanted to give it a go and encountered this:
When cloning the library by default git does not pull submodules but leaves an empty folder, this causes the build.sh to detect the folder, cd into it, do a git pull (now on the neptune library git remote since it does not detect this as a submodule) and the script fails.
It should probably be included in the readme that one needs to clone using git clone --recurse-submodules [email protected]:Space-Systems/neptune.git (using this, build.sh works flawlessly!) to get submodules or the bash-folder-exists test might be be exchanged with a git-remote check to see that its points to OPI.git? Or maybe a submodule pull git submodule update --init --recursive in the build.sh could be included?
The text was updated successfully, but these errors were encountered:
Hey,
Nice to see neptune in the public now! Wanted to give it a go and encountered this:
When cloning the library by default git does not pull submodules but leaves an empty folder, this causes the
build.sh
to detect the folder, cd into it, do a git pull (now on the neptune library git remote since it does not detect this as a submodule) and the script fails.It should probably be included in the readme that one needs to clone using
git clone --recurse-submodules [email protected]:Space-Systems/neptune.git
(using this,build.sh
works flawlessly!) to get submodules or the bash-folder-exists test might be be exchanged with a git-remote check to see that its points toOPI.git
? Or maybe a submodule pullgit submodule update --init --recursive
in the build.sh could be included?The text was updated successfully, but these errors were encountered: