From e3047f3f01e84afa07972cfd1c7a8ec0c9080d16 Mon Sep 17 00:00:00 2001 From: zyphlar Date: Sat, 25 May 2024 21:55:21 -0700 Subject: [PATCH] Elaborate on shallow submodule options I often clone things first and read docs second rather than use Github's interface. This causes problems with submodules, especially shallow submodules. I finally found a workflow that's pretty ok and figured I'd share it here for other contributors. Signed-off-by: zyphlar --- docs/INSTALL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/INSTALL.md b/docs/INSTALL.md index e7b432d125..073e33478f 100644 --- a/docs/INSTALL.md +++ b/docs/INSTALL.md @@ -72,6 +72,8 @@ If you're only doing a one-off build or your internet bandwidth or disk space is - a `--shallow-submodules` option to _shallow clone_ the submodules (save ~1.3Gb) - this is suitable for a generic development if no work on submodules is planned. +If you mistakenly did a `git clone` without checking out submodules, you can run `git submodule update --init --recursive`. If you want to do so shallowly, you can add `--depth=1` to the update command. + To be able to publish the app in stores e.g. in Google Play its necessary to populate some configs with private keys, etc. Check `./configure.sh --help` to see how to copy the configs automatically from a private repository.