# \#spm

**URL:** https://community.tuist.dev/tag/spm/19.md

[Latest](https://community.tuist.dev/latest.md) · [Categories](https://community.tuist.dev/categories.md) · [Tags](https://community.tuist.dev/tags.md)

---

## [Is it possible to share constants between your Tuist/SPM files and your Swift files?](https://community.tuist.dev/t/is-it-possible-to-share-constants-between-your-tuist-spm-files-and-your-swift-files/848)

<div class="topic-metadata">

**Author:** [@CTMacUser](https://community.tuist.dev/u/CTMacUser)\
**Replies:** 4\
**Last updated:** [December 21, 2025, 8:12pm UTC](https://community.tuist.dev/t/is-it-possible-to-share-constants-between-your-tuist-spm-files-and-your-swift-files/848 "2025-12-21T20:12:19Z")

</div>

Since we can use Tuist to generate Info.plist, we already have a degree of DRY (Don’t Repeat Yourself). Is it possible to take it further, to make sure that constants used to configure a project exactly match ones in the…

---

## [Differentiating between a local SPM package and a Tuist project](https://community.tuist.dev/t/differentiating-between-a-local-spm-package-and-a-tuist-project/749)

<div class="topic-metadata">

**Author:** [@fdiaz](https://community.tuist.dev/u/fdiaz)\
**Replies:** 2\
**Last updated:** [September 11, 2025, 5:11pm UTC](https://community.tuist.dev/t/differentiating-between-a-local-spm-package-and-a-tuist-project/749 "2025-09-11T17:11:17Z")

</div>

Each module in our setup is organized as a Workspace that contains two Tuist projects: ModuleName-Tuist: This project contains the main source code of the module along with its unit tests. It’s the “real” module codeba…

---

## [Documentation Generation Fails Due to Missing Header](https://community.tuist.dev/t/documentation-generation-fails-due-to-missing-header/442)

<div class="topic-metadata">

**Author:** [@hak-ioki](https://community.tuist.dev/u/hak-ioki)\
**Replies:** 2\
**Last updated:** [March 19, 2025, 8:43am UTC](https://community.tuist.dev/t/documentation-generation-fails-due-to-missing-header/442 "2025-03-19T08:43:49Z")

</div>

Question or problem After migrating Firebase from Carthage to Swift Package Manager (SPM) and updating its version, I encountered an issue where Build Documentation fails due to missing FirebaseCore headers: This app…

---

## [Using SPM for declaring a local graph](https://community.tuist.dev/t/using-spm-for-declaring-a-local-graph/232)

<div class="topic-metadata">

**Author:** [@pepicrft](https://community.tuist.dev/u/pepicrft)\
**Replies:** 0\
**Last updated:** [November 26, 2024, 10:49am UTC](https://community.tuist.dev/t/using-spm-for-declaring-a-local-graph/232 "2024-11-26T10:49:03Z")

</div>

I’ve noticed some confusion about using SPM to model graphs with local packages, so I wanted to shed some light on the topic. While SPM can describe a project graph, we believe it’s not the best tool for the job—at leas…