Đang chuẩn bị liên kết để tải về tài liệu:
Lập trình Wrox Professional Xcode 3 cho Mac OS part 53

mà nhiều đội sử dụng một phần mềm chuyên nghiệp thường xây dựng vị trí để chia sẻ các sản phẩm xây dựng. Ít nhất, bảo trì dễ dàng hơn nếu các dự án của bạn không ghi đè lên vị trí xây dựng defi ned trong Preferences Xcode. Bất kỳ thay đổi cần phải được thực hiện có thể được thực hiện ở một nơi: | Build Settings 393 that many professional software teams use a common build location to share built products. At the very least maintenance is easier if your projects don t override the build location defined in the Xcode Preferences. Any change that needs to be made can be made in one place the Xcode Preferences. The second solution sets the custom build location only in those projects that need to share built products. Although this would appear to be the most concise solution you are going to have problems sharing those projects with other developers. Project-specific custom build locations are absolute paths stored in the project document. Give that project to another developer and the project won t build if the path to its build location doesn t exist on their system. More than likely it won t unless you ve colluded with the other developer beforehand to ensure that it does. Using the single build location defined in the Xcode Preferences the first strategy works because the only information stored in each project document is a flag to use the global build location defined by the current user a location that can be different for every developer. This is in a fashion similar to the philosophy of source trees described in Chapter 21 and requires only that all of the developers have a custom build location defined in their preferences. On the other hand defining a centralized build location for all projects prevents any project from using the project folder for its build location. After you set the Xcode Preferences to a custom build location you lose the convenience of using the local build folder for all of your projects. If you have just a few projects that need to share built products and you don t need to share those projects with other developers consider setting the build location for those projects individually. The rest of your projects can continue to use their local build folder. The third option is somewhat of a trick but works well for small .