This project uses Git Submodules to manage sub-repositories, including the following submodules:
BreezeApp-engine: BreezeApp engine core componentsBreezeApp-client: BreezeApp client components
git clone --recursive https://github.com/mtkresearch/BreezeApp.gitgit submodule init
git submodule updategit submodule update --remotegit submodule update --remote BreezeApp-engine
git submodule update --remote BreezeApp-clientcd BreezeApp-engine
# Make changes and commit
git add .
git commit -m "Update BreezeApp-engine"
git push origin main
cd ..
# Update submodule reference in main project
git add BreezeApp-engine
git commit -m "Update BreezeApp-engine submodule"cd BreezeApp-engine
git checkout <branch-or-tag>
cd ..
git add BreezeApp-engine
git commit -m "Switch BreezeApp-engine to <branch-or-tag>"- Clone main project:
git clone https://github.com/mtkresearch/BreezeApp.git - Initialize submodules:
git submodule init && git submodule update
# Ensure submodule updates are committed
git submodule update --remote
git add .
git commit -m "Update submodules"
git push# Reset submodules to correct state
git submodule deinit -f BreezeApp-engine
git submodule deinit -f BreezeApp-client
git submodule update --init --recursive# Completely remove submodule (use with caution)
git submodule deinit -f BreezeApp-engine
git rm BreezeApp-engine
rm -rf .git/modules/BreezeApp-engine
git commit -m "Remove BreezeApp-engine submodule"- Regular Updates: Run
git submodule update --remoteregularly to keep submodules up to date - Explicit Commits: After making changes in submodules, remember to commit submodule updates in the main project
- Version Control: Use tags or specific commits to ensure submodule version consistency
- Documentation Sync: Update related documentation when submodule APIs change