Closed mksoc closed 3 months ago
In the example of a project with a single dependency dep0, for some reason, on the first build, the sub-dependencies are nested (correctly I would say) like this:
dep0
deps/ ├─ _deps/ │ ├─ dep0-src/ │ │ ├─ deps/ │ │ │ ├─ _deps/ │ │ │ │ ├─ dep1-src/ │ │ │ │ ├─ dep2-src/ │ │ │ │ ├─ .../
But after running a make command a second time, something triggers an update of all the dependencies that end up copied flat under the root, like so:
make
deps/ ├─ _deps/ │ ├─ dep0-src/ │ ├─ dep1-src/ │ ├─ dep2-src/ │ ├─ .../
@benoitdenkinger do you have any idea why? It started only after the last merge request on TriglaV.
In the example of a project with a single dependency
dep0, for some reason, on the first build, the sub-dependencies are nested (correctly I would say) like this:But after running a
makecommand a second time, something triggers an update of all the dependencies that end up copied flat under the root, like so:@benoitdenkinger do you have any idea why? It started only after the last merge request on TriglaV.