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
I added the NodeMCU firmware repository as a submodule (inside a directory named firmware), and encountered the following issue when building using the Docker build image:
$ docker run --rm -ti -v `pwd`:/opt/nodemcu-firmware marcelstoer/nodemcu-build build
fatal: Not a git repository: ../.git/modules/firmware
The above issue goes away if I clone the firmware repository directly (not as a submodule).
From a cursory look it seems the scripts rely on the firmware being located inside a valid git repository, which would not be the case when mounting the submodule folder directly (as the .git folder would be in the top level directory of the parent git repository).
The build also fails if you attempt using source code from a release, e.g. 3.0.0-release_20240225, but with the below message:
fatal: Not a git repository (or any parent up to mount point /opt/nodemcu-firmware)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
The text was updated successfully, but these errors were encountered:
I added the NodeMCU firmware repository as a submodule (inside a directory named
firmware
), and encountered the following issue when building using the Docker build image:$ docker run --rm -ti -v `pwd`:/opt/nodemcu-firmware marcelstoer/nodemcu-build build fatal: Not a git repository: ../.git/modules/firmware
The above issue goes away if I clone the firmware repository directly (not as a submodule).
Commands to reproduce:
From a cursory look it seems the scripts rely on the firmware being located inside a valid git repository, which would not be the case when mounting the submodule folder directly (as the
.git
folder would be in the top level directory of the parent git repository).The build also fails if you attempt using source code from a release, e.g. 3.0.0-release_20240225, but with the below message:
The text was updated successfully, but these errors were encountered: