--- title: Tuist 0.12.0 supports defining multiple sources and... description: Tuist 0.12.0 adds support for defining multiple source and resource paths for a target, introduces a new static framework product type for faster app startup,... canonical: https://daily.dev/posts/tuist-0-12-0-supports-defining-multiple-sources-and-resources-mbvt0sak8 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Tuist 0.12.0 supports defining multiple sources and resources | daily.dev og:description: Tuist 0.12.0 adds support for defining multiple source and resource paths for a target, introduces a new static framework product type for faster app startup,... og:url: https://daily.dev/posts/tuist-0-12-0-supports-defining-multiple-sources-and-resources-mbvt0sak8 og:image: https://api.daily.dev/og/posts/mBVT0sAk8.png og:image:alt: Tuist 0.12.0 supports defining multiple sources and resources og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Tuist 0.12.0 supports defining multiple sources and resources **[ Tuist ](https://daily.dev/sources/tuist-blog)** · 5 min read · 0 upvotes · 0 comments ## Summary Tuist 0.12.0 adds support for defining multiple source and resource paths for a target, introduces a new static framework product type for faster app startup, and generates an extra scheme per project that bundles all targets and test actions. The release also drops support for YAML and JSON project manifests in favor of Swift-only manifests. Upcoming work includes custom build configurations, workspace configuration, Storyboard bootstrapping, and unified resource access across modules. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I define multiple source and resource paths for a single Tuist target? Tuist 0.12.0 lets you pass arrays to the sources and resources parameters of a Target definition instead of a single glob string. For example, sources can be ["Sources/**", "OtherSources/**"] and resources can be ["Images/*.{pdf,png}", "Fonts/*.ttf"]. This change is backwards compatible, so existing single-path configurations keep working unchanged. _Developers configuring Tuist targets can track tooling updates like this via daily.dev._ ### Does Tuist still support defining project manifests in YAML or JSON? No, starting with version 0.12.0, Tuist removed support for YAML and JSON project manifests, leaving Swift as the only supported manifest format. The change was made so developers get a consistent experience with syntax highlighting, code completion, API documentation, and formatting tools when writing project manifests. _Teams migrating build configs off deprecated formats can follow changes like this on daily.dev._ ### What is a static framework product type in Tuist and when should I use it? A static framework is a new product type added in Tuist 0.12.0, selected via the .staticFramework option, that behaves like a static library but also bundles header files inside the framework. Static linking avoids the app-launch slowdown caused by many dynamically linked libraries, per Apple's WWDC 2016 guidance, making it a good choice for large-scale apps with slow startup times. _iOS developers weighing static versus dynamic linking can find tooling news like this on daily.dev._ ## Similar posts on daily.dev - [Toss: Building less to ship faster](https://daily.dev/posts/toss-building-less-to-ship-faster-1arhtus0n) · Tuist · 4 upvotes · 0 comments --- Tags: [#ios](https://daily.dev/tags/ios), [#swift](https://daily.dev/tags/swift), [#xcode](https://daily.dev/tags/xcode) [View this post on daily.dev](https://daily.dev/posts/tuist-0-12-0-supports-defining-multiple-sources-and-resources-mbvt0sak8) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Tuist 0.12.0 supports defining multiple sources and resources","url":"https://daily.dev/posts/tuist-0-12-0-supports-defining-multiple-sources-and-resources-mbvt0sak8","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/tuist-0-12-0-supports-defining-multiple-sources-and-resources-mbvt0sak8"},"datePublished":"2026-08-23T12:22:15.297Z","dateModified":"2026-08-23T12:41:58.023Z","description":"Tuist 0.12.0 adds support for defining multiple source and resource paths for a target, introduces a new static framework product type for faster app startup,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/269d304ccaf2a3c0a1c1a51ff5faffd2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/269d304ccaf2a3c0a1c1a51ff5faffd2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"\n Tuist\n ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"\n Tuist\n ","logo":"https://media.daily.dev/image/upload/s--3AYDH23h--/f_auto,q_auto/v1787487506/logos/tuist-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/tuist-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/tuist-0-12-0-supports-defining-multiple-sources-and-resources-mbvt0sak8","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ios,swift,xcode","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"\n Tuist\n ","item":"https://daily.dev/sources/tuist-blog"},{"@type":"ListItem","position":3,"name":"Tuist 0.12.0 supports defining multiple sources and resources"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/tuist-0-12-0-supports-defining-multiple-sources-and-resources-mbvt0sak8#faq","mainEntity":[{"@type":"Question","name":"How do I define multiple source and resource paths for a single Tuist target?","acceptedAnswer":{"@type":"Answer","text":"Tuist 0.12.0 lets you pass arrays to the sources and resources parameters of a Target definition instead of a single glob string. For example, sources can be [\"Sources/**\", \"OtherSources/**\"] and resources can be [\"Images/*.{pdf,png}\", \"Fonts/*.ttf\"]. This change is backwards compatible, so existing single-path configurations keep working unchanged. Developers configuring Tuist targets can track tooling updates like this via daily.dev."}},{"@type":"Question","name":"Does Tuist still support defining project manifests in YAML or JSON?","acceptedAnswer":{"@type":"Answer","text":"No, starting with version 0.12.0, Tuist removed support for YAML and JSON project manifests, leaving Swift as the only supported manifest format. The change was made so developers get a consistent experience with syntax highlighting, code completion, API documentation, and formatting tools when writing project manifests. Teams migrating build configs off deprecated formats can follow changes like this on daily.dev."}},{"@type":"Question","name":"What is a static framework product type in Tuist and when should I use it?","acceptedAnswer":{"@type":"Answer","text":"A static framework is a new product type added in Tuist 0.12.0, selected via the .staticFramework option, that behaves like a static library but also bundles header files inside the framework. Static linking avoids the app-launch slowdown caused by many dynamically linked libraries, per Apple's WWDC 2016 guidance, making it a good choice for large-scale apps with slow startup times. iOS developers weighing static versus dynamic linking can find tooling news like this on daily.dev."}}]} ```