Changed the way to manage some libraries in the repository
It's a little late, but we have changed our policy to manage some libraries in the git repository as submodules. This may cause some problems for people who cloned the repository before the change, when they pull changes from now on.
git clone --recursive https://github.com/TLabAltoh/TLabWebViewVR.git
command to create a new clone, including initialization of the submodules.
Note: When importing updates to the repository, remember to include updates to submodules.
git fetch origin master
git pull origin master
git submodule update --init // Match the submodule version specified by the repository
// Match the submodule version specified by the repository
// Match the submodule version specified by the repository What does this ^ mean?
The git repository has recorded the commit id of the submodule used in the latest commit.
git submodule update --init are fetch submodule with git repo registered commit id.
For example, I have checkout submodule (TLabWebView) to bellow commit and push to remote, the user clone or fetch this repository will fetch same commit id of the submodule when run above command.
commit 243cd11ddc3005372aec53ba3f9f19295fe7f790 (HEAD)
Author: TLabAltoh <[email protected]>
Date: Fri Mar 29 20:35:47 2024 +0900
update native plugin