AndrewShkrob/organicmaps
1
Fork 0
forked from organicmaps/organicmaps
Code Pull requests Activity

Elaborate on shallow submodule options

Browse source 
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 <zyphlar@users.noreply.github.com>
This commit is contained in:
zyphlar 2024-05-25 21:55:21 -07:00 • committed by Alexander Borsuk
parent 75b63cf886
commit e3047f3f01
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/INSTALL.md
View file

@ -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.