# Static framework using Foundation's #bundle macro

A project with a static framework that owns resources and reaches them through Foundation's
`#bundle` macro — both directly and as a caller-side default argument
([SE-0422](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0422-caller-side-default-argument-macro-expression.md)).

`#bundle` expands to `Bundle.module` only when the build system sets the
`SWIFT_MODULE_RESOURCE_BUNDLE_AVAILABLE` compilation condition for resource-bearing modules;
otherwise it falls back to a DSO-handle lookup that resolves to the main bundle for statically
linked code, where resources living in the companion `.bundle` are invisible.

```
Project:
  - ResourceLoader (static macOS framework, no resources, exposes an API with a #bundle default argument)
  - StaticFramework (static macOS framework with resources)
  - BundleMacro_StaticFramework (macOS bundle, synthesized)
  - StaticFrameworkTests (unit tests asserting the resource resolves at runtime)
  - App (macOS app linking StaticFramework)
  - AppTests (unit tests hosted in App exercising StaticFramework's expansions from a consumer,
    so cache acceptance tests can consume StaticFramework as a binary while these run from source)
```

The targets are macOS so acceptance tests run without booting a simulator and cache warms
produce single-slice binaries.

Dependencies:

- StaticFramework -> ResourceLoader
- StaticFramework -> BundleMacro_StaticFramework
- StaticFrameworkTests -> StaticFramework
- App -> StaticFramework
- AppTests -> App, StaticFramework


[Check out example](https://github.com/tuist/tuist/tree/main/examples/xcode/generated_static_framework_with_bundle_macro)

Static framework using Foundation's #bundle macro

A project with a static framework that owns resources and reaches them through Foundation's #bundle macro — both directly and as a caller-side default argument (SE-0422).

#bundle expands to Bundle.module only when the build system sets the SWIFT_MODULE_RESOURCE_BUNDLE_AVAILABLE compilation condition for resource-bearing modules; otherwise it falls back to a DSO-handle lookup that resolves to the main bundle for statically linked code, where resources living in the companion .bundle are invisible.

plaintext

Project:
  - ResourceLoader (static macOS framework, no resources, exposes an API with a #bundle default argument)
  - StaticFramework (static macOS framework with resources)
  - BundleMacro_StaticFramework (macOS bundle, synthesized)
  - StaticFrameworkTests (unit tests asserting the resource resolves at runtime)
  - App (macOS app linking StaticFramework)
  - AppTests (unit tests hosted in App exercising StaticFramework's expansions from a consumer,
    so cache acceptance tests can consume StaticFramework as a binary while these run from source)

The targets are macOS so acceptance tests run without booting a simulator and cache warms produce single-slice binaries.

Dependencies:

StaticFramework -> ResourceLoader
StaticFramework -> BundleMacro_StaticFramework
StaticFrameworkTests -> StaticFramework
App -> StaticFramework
AppTests -> App, StaticFramework

Check out example