https://github.com/artemnovichkov/my-project
https://github.com/artemnovichkov/my-project
build framework xcode
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/artemnovichkov/my-project
- Owner: artemnovichkov
- Created: 2017-11-13T02:34:18.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-11-21T03:37:05.000Z (over 8 years ago)
- Last Synced: 2025-04-05T21:43:34.340Z (about 1 year ago)
- Topics: build, framework, xcode
- Language: C
- Size: 67.4 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## 📦 Frameworks
A test project for showing first-party framework integration. The main goal of this approach is to link a compiled static frameworks to prevent extra rebuilding.
## Features
- ⚡️ Fast project build - no need to wait frameworks
- 🛀 Isolated testing of frameworks
- 🤖 Debug compiled frameworks via workspace
## 🚀 Main flow
Current project structure:
- `MyWorkspace` - a workspace with all projects and playgrounds
- `MyProject` - a main app with linked static frameworks
- `MyFrameworkExample` - an example with a `MyFramework` target for isolated framework testing
- `MyFrameworkPlayground` - an playground with a `MyFramework` framework for isolated framework testing
Follow below steps for project changes:
1. Add new features to `MyFramework`.
2. Test it:
- via `MyFrameworkExample`. It lets you store different enviroments.
- via `MyFrameworkPlayground`. The same as above plus no need to run simulators.
3. Run `MyFramework-Universal` target. It creates an universal static framework and save it to `Frameworks` folder in the main project.
## 🤔 Current issues
- Manual configuration of new projects according this scheme
- Playgrounds don't work with static frameworks:
```bash
Playground execution failed:
error: Couldn't lookup symbols:
__T011MyFramework0A5ClassCMa
__T011MyFramework0A5ClassC3logyyFZ
```
So after `MyFramework-Universal` target running you should clean the Build folder.
- You must run `MyFramework-Universal` target manually after every change in the framework.
- Doesn't work with New Build System for universal framework building:
```bash
error: accessing build database ".../Build/Intermediates.noindex/XCBuildData/build.db": disk I/O error
```
- Framework linking graph is not obvious. You can miss something and increase app size with static framework duplication. It would be great if some tool prints dependency graph with linking type:
My Project
```
- MyFramework(static)
-- MyFramework2(dynamic)
- MyFramework2(dynamic)
```
or
```
- MyFramework(static)
-- MyFramework2(static)
- MyFramework2(static)
Warnings:
⁉️ MyFramework2 is static but used twice
```