> For the complete documentation index, see [llms.txt](https://docs.vezel.dev/zig-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vezel.dev/zig-sdk/configuration/items.md). # Items The following [MSBuild items](https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-items) are used by the Zig SDK: * `Compile`: Source code files passed to the Zig compiler. By default, the Zig SDK will populate this item type according to the project type. * `PreludeHeader`: C/C++ header files that will be automatically `#include`d in every C/C++ source file by way of Clang's `-include` flag. * `IncludeDirectory`: Header include directories passed to the compiler with the `-I` flag. Note that this applies to Zig as well, not just C/C++. * `LibraryIncludeDirectory`: Header include directories passed to the compiler with the `-isystem` flag. Note that this applies to Zig as well, not just C/C++. * `LinkerDirectory`: Library search directories passed to the linker with the `-L` flag. * `LinkerReference`: Names of native libraries that should be linked using the `-l` flag. These can be either static or dynamic. * `LibraryReference`: Direct paths to native library files that should be linked, ignoring library search directories. These can be either static or dynamic. * `CHeader`: Prepopulated by the Zig SDK with all files in the project directory ending in `.h`. * `CSource`: Prepopulated by the Zig SDK with all files in the project directory ending in `.c`. * `CxxHeader`: Prepopulated by the Zig SDK with all files in the project directory ending in `.hxx`. * `CxxHeader`: Prepopulated by the Zig SDK with all files in the project directory ending in `.cxx`. * `ZigSource`: Prepopulated by the Zig SDK with all files in the project directory ending in `.zig`. * `Watch`: Files that are monitored by `dotnet watch` for code changes. The Zig SDK will automatically populate this with all C, C++, and Zig source and header files in the project directory. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.vezel.dev/zig-sdk/configuration/items.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.