-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to build latest v2.2.6 #193
Comments
The paths in this output are confusing. It looks like you’re copying the plugin repo out of the library repo’s submodule into a new folder, maybe? Unfortunately the tracking info for nested submodules is held in the .git folder of the topmost repo. (Which in your case is the library repo.) So the git paths in my makefile are wrong (first error, I can fix that) but the git describe command is failing (second error, I can’t fix that if the build area is disconnected from the submodule info.) If that’s the case, though, then the build should never have worked? |
From side conversations, it looks like the docker-based build toolchain has always had a nonfatal error with #194 fixes the fatal error introduced in 2.2.6 caused by the submodule paths being different when the monome-rack repo is itself a submodule of another repo. |
** Platform/Version **
Building with latest
rack-plugin-toolchain
.The text was updated successfully, but these errors were encountered: