# SPM dependencies in project used outside generated workspace

**URL:** https://community.tuist.dev/t/spm-dependencies-in-project-used-outside-generated-workspace/231
**Category:** Troubleshooting & how to
**Created:** [November 25, 2024, 1:24pm UTC](https://community.tuist.dev/t/spm-dependencies-in-project-used-outside-generated-workspace/231 "2024-11-25T13:24:23Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Tamar](https://community.tuist.dev/user_avatar/community.tuist.dev/tamar/32/67_2.png) [@Tamar](https://community.tuist.dev/u/Tamar)
#### Post date: [November 27, 2024, 3:55pm UTC](https://community.tuist.dev/t/spm-dependencies-in-project-used-outside-generated-workspace/231/4 "2024-11-27T15:55:40Z")

</div>

Thanks for the reply! It’s partly because the migration is not yet completed, but also - working with workspaces is not a must, many times having project with different targets and dependencies on other projects is sufficient.

So the setup is quite simple - a project which is simple enough to be a project and not a workspace, and it depends on another project, generated with Tuist. One can always change the structure of the projects that depends on the Tuist-generated one, but I would expect it to not be dependent on using workspaces.

For my case, using the workaround mentioned above was sufficient, but maybe it can help someone in the future.

---

_[View the full topic](https://community.tuist.dev/t/spm-dependencies-in-project-used-outside-generated-workspace/231)._