Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
app_with_framework_and_tests
invalid_workspace_manifest_name
ios_app_with_custom_workspace
ios_app_with_framework_and_resources
ios_app_with_framework_linking_static_framework
ios_app_with_frameworks
ios_app_with_setup
ios_app_with_static_frameworks
ios_app_with_static_libraries
ios_app_with_tests
ios_app_with_transitive_framework
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_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)

Dependencies:

  • App -> Framework1
  • App -> Framework2
  • Framework1 -> Framework2

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)

Dependencies:

  • App -> Framework1

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_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

Same as ios_app_with_static_libraries except using static frameworks instead of libraries.

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)

Dependencies:

  • App -> A
  • A -> B

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

You can’t perform that action at this time.