Xcode中的环境变量

野性酷女 2024-04-17 05:31 63阅读 0赞

一般我们在xcode里面配置包含工程目录下头文件的时候，都要关联着相对路径和绝对路径，如果只是自己用这个项目，用绝对路径的问题不大，但是如果协作开发，这时候绝对路径的缺点立马出现。

所以在修改User Header Search Paths这个选项的时候使用  
"$(SRCROOT)/当前工程名字/需要包含头文件所在文件夹"  
将上面的双引号里面的字符串拷贝之后，你会发现这个“$(SRCROOT)”，会自动变成当前工程所以的目录。  
一、xcode中的环境变量  
$(BUILT\_PRODUCTS\_DIR)  
build成功后的，最终产品路径－－可以在Build Settings参数的Per-configuration Build Products Path项里设置  
$(TARGET\_NAME)  
目标工程名称  
$(SRCROOT)  
工程根目录（一般为.xcodeproj所在目录）  
$(PROJECT\_DIR)  
.xcodeproj所在目录  
$(CURRENT\_PROJECT\_VERSION)  
当前工程版本号  
其他：  
$() xcode数据目录该工程根目录  
$(SYMROOT) = $()/Build/Products  
$(BUILD\_DIR) = $()/Build/Products  
$(BUILD\_ROOT) = $()/Build/Products  
这三个变量中的$()不会随着Build Settings参数的设置而改变  
相反，以下可以通过设置而改变  
$(CONFIGURATION\_BUILD\_DIR) = $()/Build/Products/Debug-iphonesimulator  
$(BUILT\_PRODUCTS\_DIR) = $()/Build/Products/Debug-iphonesimulator  
$(CONFIGURATION\_TEMP\_DIR) = $()/Build/Intermediates/UtilLib.build/Debug-iphonesimulator  
$(TARGET\_BUILD\_DIR) = $()/Build/Products/Debug-iphonesimulator  
$(SDK\_NAME) = iphonesimulator5.0  
$(PLATFORM\_NAME) = iphonesimulator  
$(CONFIGURATION) = Debug  
$(TARGET\_NAME) = UtilLib  
$(EXECUTABLE\_NAME) = libUtilLib.a 可执行文件名  
$\{IPHONEOS\_DEPLOYMENT\_TARGET\} 5.0  
$(ACTION) = build  
$(CURRENTCONFIG\_SIMULATOR\_DIR) 当前模拟器路径  
$(CURRENTCONFIG\_DEVICE\_DIR) 当前设备路径  
$(BUILD\_DIR)/$(CONFIGURATION)$(EFFECTIVE\_PLATFORM\_NAME =  
$()/Build/Products/Debug-iphonesimulator  
$(PROJECT\_TEMP\_DIR)/$(CONFIGURATION)$(EFFECTIVE\_PLATFORM\_NAME) = $()/Build/Intermediates/UtilLib.build/Debug-iphonesimulator  
自定义变量

$\{CONFIGURATION\}-iphoneos 表示：Debug-iphoneos

$\{CONFIGURATION\}-iphonesimulator 表示：Debug-iphonesimulator

$(CURRENTCONFIG\_DEVICE\_DIR) = $\{SYMROOT\}/$\{CONFIGURATION\}-iphoneos

$(CURRENTCONFIG\_SIMULATOR\_DIR) = $\{SYMROOT\}/$\{CONFIGURATION\}-iphonesimulator

自定义一个设备无关的路径（用来存放各种架构arm6/arm7/i386输出的产品）

$(CREATING\_UNIVERSAL\_DIR) = $\{SYMROOT\}/$\{CONFIGURATION\}-universal

自定义变量代表的值

$(CURRENTCONFIG\_DEVICE\_DIR) ＝ $()/Build/Products/Debug-iphoneos

$(CURRENTCONFIG\_SIMULATOR\_DIR) = $()/Build/Products/Debug-iphonesimulator

$(CREATING\_UNIVERSAL\_DIR) = $()/Build/Products/Debug-universal

iphoneos5.0下的编译脚本：

xcodebuild -project "UtilLib.xcodeproj" -configuration "Debug" -target "UtilLib" -sdk "iphoneos5.0" -arch "armv6 armv7" build RUN\_CLANG\_STATIC\_ANALYZER=NO $(BUILD\_DIR)="$\{BUILD\_DIR\}" BUILD\_ROOT="$\{BUILD\_ROOT\}"

iphonesimulator5.0下的编译脚本：

xcodebuild -project "UtilLib.xcodeproj" -configuration "Debug" -target "UtilLib" -sdk "iphonesimulator5.0" -arch "i386" build RUN\_CLANG\_STATIC\_ANALYZER=NO $(BUILD\_DIR)="$\{BUILD\_DIR\}" BUILD\_ROOT="$\{BUILD\_ROOT\}"

加上下面一句表示输出到文件：

> "$\{BUILD\_ROOT\}.build\_output"

lipo脚本工具：合并iPhone模拟器和真机的静态类库，生成通用库

lipo -create -output "$\{CREATING\_UNIVERSAL\_DIR\}/$\{EXECUTABLE\_NAME\}" "$\{CURRENTCONFIG\_DEVICE\_DIR\}/$\{EXECUTABLE\_NAME\}" "$\{CURRENTCONFIG\_SIMULATOR\_DIR\}/$\{EXECUTABLE\_NAME\}"

意思是：把"$\{CURRENTCONFIG\_DEVICE\_DIR\}目录下的.a文件，和$\{CURRENTCONFIG\_SIMULATOR\_DIR\}目录下的.a文件合并，

在$\{CREATING\_UNIVERSAL\_DIR\}目录下，生成两个设备都通用的静态库,

例如：lipo -create -output xy.a x.a y.a

二、xcode中build Settings常见参数解析

1.Installation Directory：安装路径

静态库编译时，在Build Settings中Installation Directory设置“$(BUILT\_PRODUCTS\_DIR)”

Skip Install设为YES

Installation Directory默认为/usr/local/lib

因为Build Location默认时，.a文件会放在很长（比如：/Users/xxx/Library/Developer/Xcode/DerivedData/xxxProgram

dalrvzehhtesxdfqhxixzafvddwe/Build/Products/Debug-iPhoneos）的路径下，或是我们target指定的路径

Skip Install如果是NO,可能会被安装到默认路径/usr/local/lib

2.Public Headers Folder Path：对外公开头文件路径

设为“include”（具体的头文件路径为：$(BUILT\_PRODUCTS\_DIR)/include/xx.h）

在最终文件.a同级目录下生成一个include目录

默认：/usr/local/include

Public Headers Folder Path这个路径就是使用这lib的某工程需要依赖的外部头文件.导入这路径后，\#include/import "xx.h"才能看到

3.User Header Search Paths：依赖的外部头文件搜索路径

设置为“$(BUILT\_PRODUCTS\_DIR)/include”

和2中路径对应

4.Per-configuration Build Products Path：最终文件路径

比如设为“../app”，就会在工程文件.xcodeproj上一层目录下的app目录里，创建最终文件

默认为$(BUILD\_DIR)/$(CONFIGURATION)$(EFFECTIVE\_PLATFORM\_NAME)

等于$(BUILT\_PRODUCTS\_DIR)

5.Per-configuration Intermediate Build Files Path：临时中间文件路径

默认为：$(PROJECT\_TEMP\_DIR)/$(CONFIGURATION)$(EFFECTIVE\_PLATFORM\_NAME)

6.Code Signing Identity：真机调试的证书选择

选一个和Bundle identifier相对应的证书

Library Search Paths：库搜索路径

Architectures：架构，设为 armv6 或 armv7

Valid Architectures：应用框架，可以设为 armv6、 armv7 或i386

Product Name:工程文件名，默认为$(TARGET\_NAME)

Info.plist File：info文件路径

Build Variants：默认为normal

Other Linker Flags：其他链接标签

设为“-ObjC”

当导入的静态库使用了类别，需要设为-ObjC

iOS Deployment Target：ios部署对象

比如可以选择设为，ios3到ios5的一种版本

Prefix Header：预编头文件（比如：UtilLib/UtilLib-Prefix.pch）

Precompile Prefix Header：设为“Yes”，表示允许加入预编译头

三、workspace（工作区）

作用：管理多个工程（project），多工程联编

四、workspace多工程联编设置

一、

1.新建一个静态库工程，比如UtilLib，并生成UtilLib.h和UtilLib.m文件

2.选中需要公开的头文件，

把右侧栏的Target Membership中设置为public

或则，选中工程目录target的Build Phases标签的copy headers项，在public中添加要公开的头文件

3.Architectures设为：armv6 armv7

4.Valid Architectures设为：armv6 armv7 i386

5.Build Products Path设为：$(SRCROOT)/../build

6.Per-configuration Build Products Path设为：

$(SRCROOT)/../build/$(CONFIGURATION)$(EFFECTIVE\_PLATFORM\_NAME)

7.Per-configuration Intermediate Build Files Path设为：

$(SRCROOT)/../build/$(TARGET\_NAME).build/$(CONFIGURATION)$(EFFECTIVE\_PLATFORM\_NAME)

8.设置安装路径：Installation Directory项

9.设置对外公开的头文件路径：Public Headers Folder Path项

10.为静态库添加依赖的shell脚本

选中工程目录target的Build Phases标签，点击由下角的Add Build Phase按钮

在弹出的菜单里选择Add run script项，然后页面中会多出一个Run Script项

在黑框里填写"$SRCROOT/mergeArmSymbols.sh"

建立对此脚本的依赖（编译静态库的后会运行此脚本）

如果编译时设备选的是iphone simulator：

则此脚本会在对应iphone device的产品目录Debug-iphoneos中，生成对device有用的.a静态库，

相反，如果设备选的是iphone device：

则此脚本会在对应iphone simulator的产品目录Debug-iphoneos中，生成对simulator有用的.a静态库

最后，此脚本调用lipo工具，把本工程生成静态库与此脚本生成的静态库合并，生成simulator和device都通用的.a文件

11.具体bash shell脚本如下：

\[plain\] view plaincopy  
mergeArmSymbols.sh

# Version 2.0 (updated for Xcode 4, with some fixes) #

# Author: Adam Martin - [http://twitter.com/redglassesapps][http_twitter.com_redglassesapps] #

# Based on: original script from Eonil (main changes: Eonil's script WILL NOT WORK in Xcode GUI - it WILL CRASH YOUR COMPUTER) #

#  #

# More info: see this Stack Overflow question: [http://stackoverflow.com/questions/3520977/build-fat-static-library-device-simulator-using-xcode-and-sdk-4][http_stackoverflow.com_questions_3520977_build-fat-static-library-device-simulator-using-xcode-and-sdk-4] #

\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\[ Tests: helps workaround any future bugs in Xcode \]\#\#\#\#\#\#\#\#

#  #

DEBUG\_THIS\_SCRIPT="true"

if \[ $DEBUG\_THIS\_SCRIPT = "true" \]  
then  
echo "\#\#\#\#\#\#\#\#\#\#\# TESTS \#\#\#\#\#\#\#\#\#\#\#\#\#"  
echo "Use the following variables when debugging this script; note that they may change on recursions"  
echo "BUILD\_DIR = $BUILD\_DIR"  
echo "BUILD\_ROOT = $BUILD\_ROOT"  
echo "CONFIGURATION\_BUILD\_DIR = $CONFIGURATION\_BUILD\_DIR"  
echo "BUILT\_PRODUCTS\_DIR = $BUILT\_PRODUCTS\_DIR"  
echo "CONFIGURATION\_TEMP\_DIR = $CONFIGURATION\_TEMP\_DIR"  
echo "TARGET\_BUILD\_DIR = $TARGET\_BUILD\_DIR"  
echo "SDK\_NAME = $SDK\_NAME"  
echo "PLATFORM\_NAME = $PLATFORM\_NAME"  
echo "CONFIGURATION = $CONFIGURATION"  
echo "TARGET\_NAME = $TARGET\_NAME"  
echo "ARCH\_TO\_BUILD = $ARCH\_TO\_BUILD"  
echo "ARCH\_TO\_BUILD = $ARCH\_TO\_BUILD"  
echo "ACTION = $ACTION"  
echo "SYMROOT = $SYMROOT"  
echo "EXECUTABLE\_NAME = $EXECUTABLE\_NAME"  
echo "CURRENTCONFIG\_SIMULATOR\_DIR = $CURRENTCONFIG\_SIMULATOR\_DIR"  
echo "CURRENTCONFIG\_DEVICE\_DIR = $CURRENTCONFIG\_DEVICE\_DIR"

echo "\#\#\#\#\#\#\#\#\#\#\#\#\#Other\#\#\#\#\#\#\#\#\#\#\#"  
echo "BUILD\_DIR/CONFIGURATION/EFFECTIVE\_PLATFORM\_NAME = $BUILD\_DIR/$CONFIGURATION$EFFECTIVE\_PLATFORM\_NAME"

echo "PROJECT\_TEMP\_DIR/CONFIGURATION/EFFECTIVE\_PLATFORM\_NAME = $PROJECT\_TEMP\_DIR/$CONFIGURATION$EFFECTIVE\_PLATFORM\_NAME"

\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\[ part 1 \]\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#

# First, work out the BASESDK version number #

# (incidental: searching for substrings in sh is a nightmare! Sob) #

SDK\_VERSION=$(echo $\{SDK\_NAME\} | grep -o '.\{3\}$')

# Next, work out if we're in SIM or DEVICE #

if \[ $\{PLATFORM\_NAME\} = "iphonesimulator" \]  
then  
OTHER\_SDK\_TO\_BUILD=iphoneos$\{SDK\_VERSION\}  
ARCH\_TO\_BUILD="armv6 armv7"  
else  
OTHER\_SDK\_TO\_BUILD=iphonesimulator$\{SDK\_VERSION\}  
ARCH\_TO\_BUILD="i386"  
fi

echo "XCode has selected SDK: $\{PLATFORM\_NAME\} with version: $\{SDK\_VERSION\} (although back-targetting: $\{IPHONEOS\_DEPLOYMENT\_TARGET\})"  
echo "...therefore, OTHER\_SDK\_TO\_BUILD = $\{OTHER\_SDK\_TO\_BUILD\}"

#  #

\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\[ end of part 1 \]\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#

\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\[ part 2 \]\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#

#  #

# IF this is the original invocation, invoke whatever other builds are required #

#  #

# Xcode is already building ONE target... build ONLY the missing platforms/configurations. #

if \[ "true" == $\{ALREADYINVOKED:-false\} \]  
then  
echo "RECURSION: Not the root invocation, don't recurse"  
else

# Prevent recursion #

export ALREADYINVOKED="true"

echo "RECURSION: I am the root... recursing all missing build targets..."  
echo "RECURSION: ...about to invoke: xcodebuild -configuration "$\{CONFIGURATION\}" -target "$\{TARGET\_NAME\}" -sdk "$\{OTHER\_SDK\_TO\_BUILD\}" -arch "$\{ARCH\_TO\_BUILD\}" $\{ACTION\} RUN\_CLANG\_STATIC\_ANALYZER=NO"  
xcodebuild -project "$\{TARGET\_NAME\}.xcodeproj" -configuration "$\{CONFIGURATION\}" -target "$\{TARGET\_NAME\}" -sdk "$\{OTHER\_SDK\_TO\_BUILD\}" -arch "$\{ARCH\_TO\_BUILD\}" $\{ACTION\} RUN\_CLANG\_STATIC\_ANALYZER=NO BUILD\_DIR="$\{BUILD\_DIR\}" BUILD\_ROOT="$\{BUILD\_ROOT\}" > "$\{BUILD\_ROOT\}.build\_output"  
ACTION="build"

# Merge all platform binaries as a fat binary for each configurations. #

# Calculate where the (multiple) built files are coming from: #

CURRENTCONFIG\_DEVICE\_DIR=$\{SRCROOT\}/../build/$\{CONFIGURATION\}-iphoneos  
CURRENTCONFIG\_SIMULATOR\_DIR=$\{SRCROOT\}/../build/$\{CONFIGURATION\}-iphonesimulator

echo "Taking device build from: $\{CURRENTCONFIG\_DEVICE\_DIR\}"  
echo "Taking simulator build from: $\{CURRENTCONFIG\_SIMULATOR\_DIR\}"

CREATING\_UNIVERSAL\_DIR=$\{SRCROOT\}/../build/$\{CONFIGURATION\}-universal  
echo "...outputing a universal arm6/arm7/i386 build to: $\{CREATING\_UNIVERSAL\_DIR\}"

# ... remove the products of previous runs of this script #

# NB: this directory is only created by this script - it should be safe to delete #

rm -rf "$\{CREATING\_UNIVERSAL\_DIR\}"  
mkdir "$\{CREATING\_UNIVERSAL\_DIR\}"

#  #

echo "lipo: for current configuration ($\{CONFIGURATION\}) creating output file: $\{CREATING\_UNIVERSAL\_DIR\}/$\{EXECUTABLE\_NAME\}"  
lipo -create -output "$\{CREATING\_UNIVERSAL\_DIR\}/$\{EXECUTABLE\_NAME\}" "$\{CURRENTCONFIG\_DEVICE\_DIR\}/$\{EXECUTABLE\_NAME\}" "$\{CURRENTCONFIG\_SIMULATOR\_DIR\}/$\{EXECUTABLE\_NAME\}"

\#\#\#\#\#\#\#custom\#\#\#\#\#\#\#\#

# copy universal lib to ../libs #

libsDir=../libs  
includeDir=../include

rm -rf "$\{libsDir\}"  
mkdir -p "$\{libsDir\}"

echo "cp -R $\{CREATING\_UNIVERSAL\_DIR\}/$\{EXECUTABLE\_NAME\} $\{libsDir\}"

cp -R "$\{CREATING\_UNIVERSAL\_DIR\}/$\{EXECUTABLE\_NAME\}" "$\{libsDir\}"

echo "cp -R $\{CURRENTCONFIG\_DEVICE\_DIR\}/include $\{includeDir\}"

cp -R "$\{CURRENTCONFIG\_DEVICE\_DIR\}/include" "$\{includeDir\}"

下载右边的图片，然后把后缀改为.sh（其实就是上面的脚本，因为博客园只能上传图片)

静态库编译后的目录结构如下：

二、

1.新建主工程，比如Nuno，添加对静态库的依赖

点击工程，在Build Phases标签的Link Binary With Libraries项中点击加号添加UtilLib.a库

选中上面的红色项，在右边栏的Location选Relative to Project，把值设为../libs/libUtilLib.a

2.设置主工程依赖的外部头文件路径：User Header Search Paths项

$(SRCROOT)/../include

3.设置Header Search Paths为：$(SRCROOT)/../include

4.设置Library Search Paths为：$(SRCROOT)/../libs

编译运行即可实现联编

(备注：选择模拟器iphone 5.0 simulator，编译静态库的时，最终文件会在Debug-iphonesimulator，就算成功.a文件还是红色，  
这是可能是xcode的bug，不会自动切换路径  
因为$(BUILT\_PRODUCTS\_DIR)所指的位置，是build/Debug-iphonesos,不是包含最终.a文件的Debug-iphonesimulator；  
选择ios Device，编译成的最终文件才在build/Debug-iphonesos下，.a文件变成非红色  
所有得用mergeArmSymbols.sh脚本来解决）

[http_twitter.com_redglassesapps]: https://link.jianshu.com/?t=http://twitter.com/redglassesapps
[http_stackoverflow.com_questions_3520977_build-fat-static-library-device-simulator-using-xcode-and-sdk-4]: https://link.jianshu.com/?t=http://stackoverflow.com/questions/3520977/build-fat-static-library-device-simulator-using-xcode-and-sdk-4