xcode环境变量设置(转载)
一般我们在xcode里面配置包含工程目录下头文件的时候,都要关联着相对路径和绝对路径,如果只是自己用这个项目,用绝对路径的问题不大,但是如果你把工程发给别人,别人就要在改这个绝对路径,这时候绝对路径的缺点立马出现。
所以在修改User Header Search Paths这个选项的时候使用"$(SRCROOT)/当前工程名字/需要包含头文件所在文件夹"将上面的双引号里面的字符串拷贝之后,你会发现这个“$(SRCROOT)”,会自动变成当前工程所以的目录。这样就可以了,发给别人,别人也不用在去修改路径了。xcode4的环境变量,Build Settings参数,workspace及联编设置一、xcode4中的环境变量$(BUILT_PRODUCTS_DIR)build成功后的,最终产品路径--可以在Build Settings参数的Per-configuration Build Products Path项里设置$(TARGET_NAME)目标工程名称$(SRCROOT)工程文件(比如Nuno.xcodeproj)的路径 $(CURRENT_PROJECT_VERSION)当前工程版本号 其他:当编译静态库,设备选模拟器(iPhone 5.0 Simulator),未设置任何Build Settings参数时,默认的基础路径:/Users/xxx/Library/Developer/Xcode/DerivedData/xxxWorkspace-caepeadwrerdcrftijaolkkagbjf下面用$()代替上面一长串东东$(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 二、xcode4中build Settings常见参数解析1.Installation Directory:安装路径静态库编译时,在Build Settings中Installation Directory设置“$(BUILT_PRODUCTS_DIR)”Skip Install设为YESInstallation Directory默认为/usr/local/lib因为Build Location默认时,.a文件会放在很长(比如:/Users/xxx/Library/Developer/Xcode/DerivedData/xxxProgramdalrvzehhtesxdfqhxixzafvddwe/Build/Products/Debug-iPhoneos)的路径下,或是我们target指定的路径Skip Install如果是NO,可能会被安装到默认路径/usr/local/lib2.Public Headers Folder Path:对外公开头文件路径设为“include”(具体的头文件路径为:$(BUILT_PRODUCTS_DIR)/include/xx.h)在最终文件.a同级目录下生成一个include目录默认:/usr/local/includePublic 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 或 armv7Valid Architectures:应用框架,可以设为 armv6、 armv7 或i386Product Name:工程文件名,默认为$(TARGET_NAME)Info.plist File:info文件路径Build Variants:默认为normalOther Linker Flags:其他链接标签设为“-ObjC”当导入的静态库使用了类别,需要设为-ObjCiOS 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 armv74.Valid Architectures设为:armv6 armv7 i3865.Build Products Path设为:$(SRCROOT)/../build6.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 plaincopymergeArmSymbols.sh # Version 2.0 (updated for Xcode 4, with some fixes) # Author: Adam Martin - 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 #################[ 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" fi #####################[ 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}" fi 下载右边的图片,然后把后缀改为.sh(其实就是上面的脚本,因为博客园只能上传图片)静态库编译后的目录结构如下: 二、 1.新建主工程,比如Nuno,添加对静态库的依赖点击工程,在Build Phases标签的Link Binary With Libraries项中点击加号添加UtilLib.a库选中上面的红色项,在右边栏的Location选Relative to Project,把值设为../libs/libUtilLib.a2.设置主工程依赖的外部头文件路径:User Header Search Paths项$(SRCROOT)/../include3.设置Header Search Paths为:$(SRCROOT)/../include4.设置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脚本来解决)reference: http://blog.sina.com.cn/s/blog_6de18992010190kk.htmlhttp://www.cnblogs.com/xiaodao/archive/2012/03/28/2422091.htmlxcode环境变量设置(转载)的更多相关文章
- 【转】linux环境变量设置
1. 显示环境变量HOME $ echo $HOME /home/terry 2. 设置一个新的环境变量WELCOME $ export WELCOME="Hello!" $ ec ...
- 转:Linux环境变量设置方法总结 PATH、LD_LIBRARY_PATH
转: https://www.linuxidc.com/Linux/2017-03/142338.htm 文章写比较全 转载记录 Linux环境变量设置方法总结 PATH.LD_LIBRARY_P ...
- linux 环境变量设置方法总结(PATH/LD_LIBRARY_PATH)
linux 环境变量设置方法总结(PATH/LD_LIBRARY_PATH) http://blog.csdn.net/wangeen/article/details/8159500 设置 Linux ...
- SQL*Plus环境变量设置浅析
SQL*Plus的使用环境是可以通过login.sql 或 glogin.sql脚本来设置的,可能很多初学者或不习惯使用SQL*Plus的老鸟都不知道.因为在如今UI工具(Toad.PL/SQL De ...
- [Java] Tomcat环境变量设置
@echo off title Tomcat环境变量设置 color 0a set /p inputTH=D:\Work\024_Tomcat if /i "%inputTH%"= ...
- java环境变量设置
java环境变量设置 1.打开我的电脑--属性--高级--环境变量 2.新建系统变量JAVA_HOME 和CLASSPATH 变量名:JAVA_HOME 变量值:C:\Program Files\Ja ...
- AIX系统的环境变量设置
AIX系统的环境变量设置 用户环境的定义是通过设置环境变量来实现的.AIX系统主要使用两大类profile文件来定义用户环境.一类是用来为所有用户定制环境,另一类是为个人定义自己的环境. 登录时,sh ...
- tomcat配置及使用 环境变量设置
Tomcat的配置及测试: 第一步:下载tomcat,然后解压到任意盘符 第二步:配置系统环境变量 我这里是tomcat5.5,解压到的D盘 (路径为: D:\Program Files\tomcat ...
- jdk-tomcat环境变量设置
1.export命令直接在shell下设置 export JAVA_HOME=/home/yn4a/jdk1.6.0_16export PATH=$JAVA_HOME/bin:$PATHexport ...
随机推荐
- Windows下php环境变量的配置
1.找到php的路径比如"E:\php_env\PHP". 2.需要保证该目录下php.ini的配置是正确的,如果是刚下载的php包,则可能需要修改相应的一些配置:将php目 ...
- 牛客网 Wannafly挑战赛9 A.找一找-数据处理
好几天没好好学习了(咸鱼晒干了) 把稍微没那么咸鱼的几天前的一场牛客网的比赛稍微看了一下,菜的要死,这一场大数的比较多,都死了. A.找一找 时间限制:C/C++ 1秒,其他语言2秒 空间限制:C/C ...
- 洛谷—— P1503 鬼子进村
https://www.luogu.org/problemnew/show/P1503 题目背景 小卡正在新家的客厅中看电视.电视里正在播放放了千八百次依旧重播的<亮剑>,剧中李云龙带领的 ...
- va_list 简介
原文:http://blog.sina.com.cn/s/blog_590be5290100qhxr.html va_list是一个宏,由va_start和va_end界定. typedef char ...
- 网络数据注入工具HexInject
网络数据注入工具HexInject 对于Kali Linux提供的工具HexInject来说,数据注入才是其最重要的功能.它可以直接向网络注入渗透人员构造的数据包,也可以篡改网络传输的数据.为了避 ...
- sed命令2
测试文件sedtest.txt,内容为: [root@localhost sed]# cat sedtest.txt my cat's name is betty it's a cat; this i ...
- C# Http方式下载文件到本地
下文代码是从网络(http://www.cnblogs.com/hayden/archive/2012/04/26/2472815.html)得来,亲测好用.我中修改了下格式和注释,版权属于原作者“舒 ...
- javascript 怎么操纵OGNL标签
吧ONGL标签放到html标签中,来操作html的标签就能够了 样例代码: html <div id="categoryid" style="display:non ...
- python(21)- python内置函数练习
题目一:用map来处理字符串列表啊,把列表中所有人都变成sb,比方alex_sbname=['alex','wupeiqi','yuanhao'] name=['alex','wupeiqi','yu ...
- 线程安全使用(四) [.NET] 简单接入微信公众号开发:实现自动回复 [C#]C#中字符串的操作 自行实现比dotcore/dotnet更方便更高性能的对象二进制序列化 自已动手做高性能消息队列 自行实现高性能MVC WebAPI 面试题随笔 字符串反转
线程安全使用(四) 这是时隔多年第四篇,主要是因为身在东软受内网限制,好多文章就只好发到东软内部网站,懒的发到外面,现在一点点把在东软写的文章给转移出来. 这里主要讲解下CancellationT ...