3d369d1717
* Use @rpath for dynamic frameworks in tests. * Remove case-insensitive handler. * Add @rpath tests. * Run swiftformat. * Move isDynamicAndLinkable to PrecompiledNode. * Fix build issues. * Edit changelog. |
||
---|---|---|
.. | ||
app_with_framework_and_tests | ||
app_with_old_config_name | ||
app_with_organization_name_config | ||
app_with_organization_name_project | ||
framework_with_environment_variables | ||
invalid_manifest | ||
invalid_workspace_manifest_name | ||
ios_app_large | ||
ios_app_with_actions | ||
ios_app_with_carthage_frameworks | ||
ios_app_with_coredata | ||
ios_app_with_custom_scheme | ||
ios_app_with_custom_workspace | ||
ios_app_with_extensions | ||
ios_app_with_framework_and_resources | ||
ios_app_with_framework_linking_static_framework | ||
ios_app_with_frameworks | ||
ios_app_with_headers | ||
ios_app_with_helpers | ||
ios_app_with_incompatible_dependencies | ||
ios_app_with_incompatible_xcode | ||
ios_app_with_local_swift_package | ||
ios_app_with_multi_configs | ||
ios_app_with_pods | ||
ios_app_with_remote_swift_package | ||
ios_app_with_sdk | ||
ios_app_with_setup | ||
ios_app_with_signing | ||
ios_app_with_static_frameworks | ||
ios_app_with_static_libraries | ||
ios_app_with_static_library_and_package | ||
ios_app_with_templates | ||
ios_app_with_tests | ||
ios_app_with_transitive_framework | ||
ios_app_with_watchapp2 | ||
ios_app_with_xcframeworks | ||
ios_workspace_with_dependency_cycle | ||
.gitignore | ||
README.md |
README.md
Fixtures
This folder contains sample projects we use in the integration and acceptance tests. Please keep this keep in alphabetical order.
invalid_workspace_manifest_name
Contains a single file Workspac.swift
, incorrectly named workspace manifest file.
ios_app_with_custom_workspace
Contains a few projects and a Workspace.swift
manifest file.
The workspace manifest defines:
- glob patterns to list projects
- glob patterns to include documentation files
- folder reference to directory with html files
The App's project manifest leverages additionalFiles
tha defines:
- glob patterns to include documentation files
- Includes a swift
Danger.swift
file that shouldn't get included in any buid phase - folder references to a directory with json files
ios_app_with_extensions
Sample application with extension targets.
ios_app_with_tests
Simple app which includes a setup manifest.
The setup action simply installs a dummy tool (file) to /tmp
Can be tested by running tuist up
.
ios_app_with_frameworks
Slightly more complicated project consists of an iOS app and few frameworks.
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- Framework1:
- Framework1 (dynamic iOS framework)
- Framework1Tests (iOS unit tests)
- Framework2:
- Framework2 (dynamic iOS framework)
- Framework2Tests (iOS unit tests)
- Framework3:
- Framework3 (dynamic iOS framework)
- Framework4:
- Framework4 (dynamic iOS framework)
- Framework5:
- Framework5 (dynamic iOS framework)
Dependencies:
- App -> Framework1
- App -> Framework2
- Framework1 -> Framework2
- Framework2 -> Framework3
- Framework3 -> Framework4
- Framework4 -> Framework5
ios_app_with_framework_and_resources
A workspace with an application that includes resources.
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- Framework1:
- Framework1 (dynamic iOS framework)
- StaticFramework
- StaticFramework (static iOS framework)
- StaticFrameworkResources (iOS bundle)
Dependencies:
- App -> Framework1
- App -> StaticFramework
- App -> StaticFrameworkResources
ios_app_with_framework_linking_static_framework
An example project demonstrating an iOS application linking a dynamic framework which itself depends on a static framework with transitive static dependencies.
Only Framework1.framework should be linked and included into App, everything else should be statically linked into the Framework1 executable.
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- Framework1:
- Framework1 (dynamic iOS framework)
- Framework1Tests (iOS unit tests)
- Framework2:
- Framework2 (static iOS framework)
- Framework2Tests (iOS unit tests)
- Framework3:
- Framework3 (static iOS framework)
- Framework3Tests (iOS unit tests)
- Framework4:
- Framework4 (static iOS framework)
- Framework4Tests (iOS unit tests)
Dependencies:
- App -> Framework1
- Framework1 -> Framework2
- Framework1 -> Framework3
- Framework3 -> Framework4
ios_app_with_multi_configs
An workspace that contains an application and frameworks that leverage multiple configurations (Debug, Beta and Release) each of which also has an associated xcconfig file within ConfigurationFiles
.
ios_app_with_sdk
An application that contains an application target that depends on system libraries and frameworks (.framework
and .tbd
).
One of the dependencies is declared as .optional
i.e. will be linked weakly.
ios_app_with_static_libraries
This application provides a top level application with two static library dependencies. The first static library dependency has another static library dependency so that we are able to test how tuist handles the transitiveness of the static libraries in the linked frameworks of the main app.
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- A:
- A (static library iOS)
- ATests (iOS unit tests)
- B:
- B (static library iOS)
- BTests (iOS unit tests)
A standalone C project is used to generate a prebuilt static library:
- C:
- C (static library iOS)
- CTests (iOS unit tests)
Dependencies:
- App -> A
- A -> B
- A -> prebuild C (libC.a)
Note: to re-create libC.a
run fixtures/ios_app_with_static_libraries/Modules/C/build.sh
ios_app_with_static_frameworks
This fixture contains an application that depends on static frameworks, both directly and transitively.
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- Modules
- A:
- A (static framework iOS)
- ATests (iOS unit tests)
- B:
- B (static framework iOS)
- BTests (iOS unit tests)
- C:
- C (static framework iOS)
- CTests (iOS unit tests)
- D:
- D (dynamic framework iOS)
A standalone Prebuilt
project is used to generate a prebuilt static framework:
- Prebuilt
- PrebuiltStaticFramework (static framework iOS)
Dependencies:
- App -> A
- App -> C
- App -> PrebuiltStaticFramework
- A -> B
- A -> C
- C -> D
Note: to re-create PrebuiltStaticFramework.framework
run fixtures/ios_app_with_static_frameworks/Prebuilt//build.sh
ios_app_with_tests
Simple app with tests.
ios_app_with_transitive_framework
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- Framework1:
- Framework1 (dynamic iOS framework)
- Framework1Tests (iOS unit tests)
A standalone Framework2 project is used to generate a prebuilt dynamic framework :
- Framework2:
- Framework2 (dynamic iOS framework)
Dependencies:
- App -> Framework1
- Framework1 -> Framework2 (prebuilt)
Note: to re-create Framework2.framework
run fixtures/ios_app_with_transitive_framework/Framework2/build.sh
ios_app_with_pods
An iOS application with CocoaPods dependencies
ios_app_with_incompatible_xcode
An iOS app whose TuistConfig file requires an Xcode version that is not available in the system.
ios_app_with_actions
An iOS app with a target that has pre and post actions.
ios_app_with_remote_swift_package
An iOS application with remote Swift package
ios_app_with_local_swift_package
An iOS application with remote Swift package
ios_app_with_static_library_and_package
An iOS application that depends on static library that depends on Swift package where static library is defined first
Note: to re-create PrebuiltStaticFramework.framework
run fixtures/ios_app_with_static_library_and_package/Prebuilt/build.sh
ios_workspace_with_dependency_cycle
An example of a workspace that has a dependency cycle between targets in different projects.
ios_app_with_carthage_frameworks
An example of an iOS app that contains Carthage frameworks *(fat frameworks with device & simulators architectures)*. This fixture is useful to test the script that embeds them stripping the architectures that are not necessary.
ios_app_with_helpers
A basic iOS app that has some manifest bits extracted into helpers.
ios_app_with_xcframeworks
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- MyFramework:
- MyFramework (dynamic iOS framework)
- MyStaticFramework:
- MyStaticFramework (static iOS framework)
- MyStaticLibirary:
- MyStaticLibrary (static iOS libraries)
An example of an application which depends on prebuilt .xcframework
s.
The .xcframework
can be obtained by running the build.sh
script within the each of the framework directories.
e.g. ios_app_with_xcframeworks/Frameworks/MyFramework/build.sh
ios_app_with_coredate
A simple iOS app with a Core Data model and Mapping Model (.xcmappingmodel)
ios_app_with_incompatible_dependencies
An iOS app that has a dependency with a dependency with a framework for macOS.
app_with_old_config_name
An iOS app where the configuration is defined following the deprecated naming TuistConfig
.
app_with_organization_name_config
An iOS app where the organization name is defined at the Config
level.
app_with_organization_name_project
An iOS app where the organization name is defined at the Project
level.
invalid_manifest
A project with an invalid manifest
framework_with_environment_variables
A framework project that leverages environment variables to change the name of the framework.