Ryujinx/moltenvk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify static linking as the recommended linking approach for iOS app store distribution.

Browse Source
This commit is contained in:
Bill Hollings 2019-09-25 19:04:33 -05:00
parent 5c7904c3a7
commit 9f7eeb46a0
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Docs/MoltenVK_Runtime_UserGuide.md
View File

@ -106,6 +106,11 @@ Depending on your build and deployment needs, you can install **MoltenVK** as a
*static library*, or *dynamic library*, by following the steps in this section. If you are unsure
about which linking and deployment option you need, follow the steps for installing a
*static framework*, as it is the simplest to install.
>**_Note:_** Distributing an app containing a dynamic library via the *iOS App Store* can require
specialized bundling. Unless you have specific needs for dynamic libraries, the recommended
approach on *iOS* is to link **MoltenVK** to your app as a static library.
1. Open your application in *Xcode* and select your application's target in the
*Project Navigator* panel.
@ -168,7 +173,6 @@ about which linking and deployment option you need, follow the steps for install
- `UIKit.framework` (*iOS*)
- `IOSurface.framework` (*macOS*, or *iOS* if `IPHONEOS_DEPLOYMENT_TARGET` is at least `iOS 11.0`)
6. If installing **MoltenVK** as a *dynamic library* in your application, arrange to install
the `libMoltenVK.dylib` file in your application environment:

3
Docs/Whats_New.md
View File

@ -19,7 +19,8 @@ MoltenVK 1.0.38
Released TBD
- Add request for feedback from people who reject MoltenVK to README.md document.
- Clarify static linking as the recommended linking approach for *iOS* app store distribution.
- Add request for feedback from people who reject **MoltenVK** to `README.md` document.