Basic configuration of project and Project Creation and basic configuration of App development process

Basic configuration of project and Project Creation and basic configuration of App development process

My development environment is: Mac OS X EI Capitan (10.11.6), Xcode 7.3.1

First of all, I want to explain the original intention of this project. Instead of creating a complete shelving application, I want to create a basic project that can be run and has a general configuration and architecture and provides general components and auxiliary tools. To achieve this, you can quickly assemble new projects by cloning or downloading them, focusing on the actual application logic development. Therefore, I named this project "base" and the project will be synchronized on github. It can be used with blogs and git to submit logs for viewing.

Take Single View Application as an example to create a project. I am used to code-only programming. The initial structure of this template is appropriate, and there are fewer files ignored in the future.

The following prompt is displayed on the options page:
1. Select a common device type.
2. If there are solutions such as FMDB or LevelDB for Data storage, Core Data is not needed.
3. No additional unit test or UI test is required.

 

In the above selection, select the Project Storage path interface. The important option is code version management. By default, Xcode git management is selected. If you want to use software such as sourcetree to manage code versions, we do not recommend that you select this option. Because the. git hidden file generated under the project root directory will cause sourcetree management to fail, the solution is to delete the. git file later.

 

General project configuration

 

The above is the created interface, but the general configuration is slightly changed:
1. version. We recommend that you use the 1.0.0 format. The build number must be modified before each submission to iTunes connect.
2. team, which can be ignored or added to the developer account
3. Select deployment target as needed. It is recommended that the release versions of the base under the PROJECT be consistent.
4. the main interface is not intended to use main. storyboard.
5. This base project only uses the portrait screen.
6. If the full direction of the device is not supported, select requires full screen. Otherwise, the compilation will fail.
7. Do not use LaunchScreen. storyboard during startup. Clear

If you Use a single Launch chart for each device during startup, clear the Launch Screen File column, and click Use Asset Catalog. You can directly confirm that there is no need to add a new xcassets File to the File list on the left.

Generating new Brand Assets is not required at the moment.
1. Right-click the blank position and choose AppIcons & LaunchImages-> New iOS Launch Images to generate a New LaunchImage file, as shown in figure
2. Right-click Brand Assets and remove selected items
3. Return to the general configuration page and select LaunchImages for Launch Images Source.
4. Click the right arrow of AppIcons or LaunchImages, or select the Assets. xcassets file in the list on the left to go to the detailed configuration page.

 

Select the arrow icon on the right to configure the icon or start chart of different versions. The image column displays the required information. Drag and Drop png images from other places to the corresponding grid. After dragging, you can right-click the images in the grid and view the specific storage location in the Finder. Note that the icon and startup image must be in png format.

 

Build Settings configuration

The basic configuration has been completed. Pay attention to the following configurations:

1. the default Bitcode value is YES. After being submitted to iTunes connect, Apple splits the package resources to generate small size ipa files for different devices. If the project contains code that does not support bitcode, an error is reported during compilation, you need to manually set it to NO

2. Code Signing: configure the certificate used for debugging and publishing the real machine. If you have added the relevant certificate and configuration profile, configure Xcode as follows to automatically identify

3. Generally, Other Linker Flags does not need to be set. After some third-party libraries are added, you need to set

4. Info. plist File this File records important configurations of the application. The path is configured by default. You can modify the path to point to the location of the custom plist File.

5. Search Paths requires special attention to the Search Paths of Framework, Header, and Library. After a third-party Library is added, it is automatically added and can be manually managed. Note: first, after deleting a third-party library, if you are prompted that the library cannot be found, you need to manually delete the path. Second, you are advised to use the project relative location "$ (PROJECT_DIR) to edit the path)"

6. If the Prefix Header file is added, we recommend that you use the relative position "$ (SRCROOT)" to manage the path of the Prefix Header file )"

 

Above, the basic configuration of the created project and project is recorded, and the next record is the plist and prefix header files.