Understanding Xcode Engineering

Document directory

• Connection rules and settings

Xcode project-defined information

No matter what product you create, Xcode manages three types of information for you:

• Source File ReferenceContains source code, images, localized string files, data models, and more information.
• Target, Define the product to be created. The target organizes the files and commands required by the production product into a sequence of executable concatenation actions.
• Execution EnvironmentYou can run and test software products in this environment. The execution environment defines the program used to run the product. In many cases, this program is the product itself, but not necessarily. In addition, the execution environment can also define command line parameters and the environment variables needed.

Deep understanding of source file references

When you add an Objective-C source code file (. M suffix) when added to the project and associated with a target, the file will be added to the targetCompile source code (Compile Sources)In the step, the GCC compiler will process it.

The target is how to process the connection rules and settings.

Xcode concatenates Based on the connection rules and settings associated with the target. Default rules and settings are specified: Any code files written in languages supported by GCC are compiled by GCC. However, if you want to use the previous GCC version to compile the C source code file, you can simply set it through the Info window of the target.

 

Execution Environment

The execution environment refers to how the product runs in Xcode. The execution environment defines what programs Xcode should run and how to run them. You can create multiple execution environments to test the product under different conditions.

Simply put, the execution environment defines the following:

• What execution file is used may be one of the products generated after the target is connected or another execution file in the system.
• Command line parameters to be passed to the execution file.
• Environment variables that need to be set in the execution environment before starting the execution file.
• The debugger to be used and how to run the execution file in the debugger.

You can see in the Info window how to define these items for the execution File