# Resolving nested git submodule dependencies? **URL:** \ **Category:** Help\ **Tags:** c, build-system\ **Created:** [February 26, 2025, 11:43am UTC](https://ziggit.dev/t/resolving-nested-git-submodule-dependencies/8752 "2025-02-26T11:43:40Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![tensorush](https://ziggit.dev/letter_avatar_proxy/v4/letter/t/6a8cbe/32.png) [@tensorush](https://ziggit.dev/u/tensorush)\ **Post date:** [February 26, 2025, 3:53pm UTC](https://ziggit.dev/t/resolving-nested-git-submodule-dependencies/8752/6 "2025-02-26T15:53:32Z")
It’s hard to maintain larger examples in a Doc here, which was the initial reason for creating [Liza](https://ziggit.dev/t/liza-zig-codebase-initializer/3486). In fact, it already has a minimal [Zig build template for building C libraries by depending on upstream repos](https://codeberg.org/tensorush/liza/src/branch/main/src/templates/bld/build.zig). I’ve added a note on that at the end of [Build System Tricks](https://ziggit.dev/docs?topic=3531): > [@Build System Tricks](https://ziggit.dev/t/build-system-tricks/3531#p-12644-p-s-24): > > This community-driven doc is an attempt to expand on the [official Zig Build System documentation](https://ziglang.org/learn/build-system/) as well as the past community contributions by [xq](https://zig.news/xq/series/2), [Sobeston](https://zig.guide/build-system/build-modes/) and others. Here you’ll find a list of tricks on how to use every part of the build system while making sure to conveniently name and lay out your build steps. I. Basic Usage 1) Declare commonly used information upfront // Resolve a query for a custom target const my\_target = b.resolveTargetQuery(.{ .cpu\_arch = .wasm32, .os\_tag =… --- _[View the full topic](https://ziggit.dev/t/resolving-nested-git-submodule-dependencies/8752)._