mPaaS directory structure
After you import the mPaaS framework into an iOS project, a specific directory structure is created in your project folder.
Importing the mPaaS framework into an iOS project adds the following directory structure to your project folder.
In versions 10.1.32 and later, only the APMobileFramework and mPaas directories are retained in the MPaaS > Targets > mPaaSDemo folder. If you upgrade from an earlier version, the directories and categories for other components are no longer generated.
The directory structure is as follows:
└── MPaaS
├── mpaas_sdk.config
├── Targets
| └── mPaaSDemo (Project Target Name)
| ├── mPaaSDemo-mPaaS-Headers.h
| ├── mPaaSDemo-Prefix.pch
| ├── APMobileFramework
| ├── mPaas
| ├── meta.config
| └── yw_1222.jpg
├── Resources
└── Frameworks
Where:
-
mpaas_sdk.config: Stores information about the modules added to the project, including version, addition time, and resource files. Automatically maintained by the mPaaS plugin. Do not modify it manually. -
mPaaSDemo-mPaaS-Headers.h: Contains the header files for the mPaaS modules that the project depends on. Automatically maintained by the mPaaS plugin. Do not modify it manually. -
mPaaSDemo-Prefix.pch: The project's PCH file, which automatically importsmPaaSDemo-mPaaS-Headers.h. -
APMobileFramework: The category file for mPaaS framework lifecycle management. -
mPaas: The category file for
MPaaSInterface. -
meta.config: The cloud metadata downloaded from the mPaaS console. -
yw_1222.jpg: The signature verification image for Wireless Security Guard, generated from the
base64codefield in the metadata. The mobile gateway uses this image for signature verification. You can delete it if you do not use the mobile gateway feature. -
Resources & Frameworks: Contain the resource files and binary files of the union of mPaaS modules used by all targets in the project. Automatically maintained by the mPaaS plugin. Do not modify them manually.
All targets share the Resources & Frameworks directories. Therefore, different targets cannot use different versions of the same module simultaneously. Do not modify these two directories. The frameworks added to each target's Build Phase depend on the modules selected for that target.