我的菠萝

https://code.visualstudio.com/Docs/runtimes/unity

shell脚本调用Xcode打包时会遇到这个错误,个人感觉应该是权限的问题,网上找到有人遇到类似问题,他的解决方案如下 原帖地址

1. 打开Keychain Access，中文叫钥匙串访问权限
2. 找到你的证书，右击 — 显示简介 — 访问控制 — 选中【允许所有应用程序访问此项目】 — 存储更攺 — 输入密码后保存更攺，解决问题。

允许所有应用程序访问此项目我在Xcode7版本没找到这个 允许所有应用程序访问此项目.自己摸索了下, 在信任里找到使用此证书时, 选择始终信任 ,问题解决了.

钥匙串访问（Keychain Access）是一个Mac OS X应用程序，它允许用户访问和配置钥匙串的内容（包括网站，FTP服务器，SSH帐户，网络共享，无线网络，群组软件，加密磁盘映像等内容的密码等），加锁或解锁钥匙串，显示系统存储的密码，管理根证书，密钥和加密笔记。

最近写了一个函数, table自动编码为protobuf格式

local parse
parse = function(args, msg)
    for k, v in pairs(args) do
        if type(v) == 'table' then --table类型判断是否是数组
            if #v > 0 then
                for index, ele in ipairs(v) do --遍历数组元素
                    if type(ele) == 'table' then --数组元素是table, 递归解析内容
                        local emsg = msg[k]:add()
                        parse(ele, emsg)
                    else --数组元素是基本数据类型,直接添加
                        msg[k]:append(ele)
                    end
                end
            else --非数组,递归解析内容
                parse(v, msg[k])
            end
        else
            msg[k] = args[k]
        end
    end
end

准备工作

• 下载protobuffer源码A (protobuf-master)
• 编译protoc.exe,也可下载编译好的protoc.exe(protoc-3.0.2-win32)
• 下载protoc-gen-lua源码B (protoc-gen-lua-master)
• 安装python-2.7.x(注意：python3.x不兼容)
• 设置protoc.exe,python环境变量

使用源码A,protobuf-master/python，运行以下命令:

    python setup.py build
    python setup.py test
    python setup.py install

注意：xxx.proto文件必须为UTF-8格式

生成proto_pb文件

cd %~dp0
set PROTO_FILE_FOLER=XXXX
set OUTPUT_FOLDER=XXX

cd %PROTO_FILE_FOLER%
for %%i in (*.proto) do (    
"%~dp0protoc.exe" --plugin=protoc-gen-lua="%~dp0run_plugin.bat" --lua_out=%OUTPUT_FOLDER% %%i 
echo %%i successfully converted
) 

run_plugin.bat

@python "%~dp0protoc-gen-lua-master\plugin\protoc-gen-lua" 

更改当前目录为批处理本身的目录

有些晕吧？不急，我举例 比如你有个批处理a.bat在D:\qq文件夹下
a.bat内容为 cd /d %~dp0 在这里 cd /d %~dp0的意思就是cd /d d:\qq %0代表批处理本身 d:\qq\a.bat ~dp是变量扩充 d既是扩充到分区号 d: p就是扩充到路径 \qq dp就是扩充到分区号路径 d:\qq

扩充变量语法详解：

:: 选项语法: 
:: ~I - 删除任何引号(")，扩充 %I 
:: %~fI - 将 %I 扩充到一个完全合格的路径名 
:: %~dI - 仅将 %I 扩充到一个驱动器号 
:: %~pI - 仅将 %I 扩充到一个路径 
:: %~nI - 仅将 %I 扩充到一个文件名 
:: %~xI - 仅将 %I 扩充到一个文件扩展名 
:: %~sI - 扩充的路径只含有短名 
:: %~aI - 将 %I 扩充到文件的文件属性 
:: %~tI - 将 %I 扩充到文件的日期/时间 
:: %~zI - 将 %I 扩充到文件的大小 
:: %~$PATH:I - 查找列在路径环境变量的目录，并将 %I 扩充 
:: 到找到的第一个完全合格的名称。如果环境变量名 
:: 未被定义，或者没有找到文件，此组合键会扩充到 
:: 空字符串 
:: 可以组合修饰符来得到多重结果: 
:: %~dpI - 仅将 %I 扩充到一个驱动器号和路径 
:: %~nxI - 仅将 %I 扩充到一个文件名和扩展名 
:: %~fsI - 仅将 %I 扩充到一个带有短名的完整路径名 
:: %~dp$PATH:i - 查找列在路径环境变量的目录，并将 %I 扩充 
:: 到找到的第一个驱动器号和路径。 
:: %~ftzaI - 将 %I 扩充到类似输出线路的 DIR

http://www.911cd.net/forums/lofiversion/index.php/t3730.html Look at this: Manipulating variables in CMD shell I'm not sure why this type of information isn't more prominent in the help files, but there you go. NT's command shell can manipulate variables but the operations you can perform are fairly limited. Still, better than nothing. :-) If you want to do some really clever stuff then you're going to have to look elsewhere. Vbscript can be useful as it's got lots of string handling capabilities. There's also Perl and AWK which are Windows (windoze?) ports of some very powerful Unix commands.

%1 is your command line option.

Namely: mycommand.cmd myoption1.

%0 determins where the batch file is running from. I've created a demo batch file in my winnt system32 folder called x.cmd. Running this gives the results shown below

%~f1 expands %1 to the drive, path and file name. If you pass %1 from the current directory then this expands that variable to it's full path

echo f0 = %~f0 produces f0 = c:\WINNT\system32\x.cmd %~d1 gets the drive letter from %1 echo d0 = %~d0 produces d0 = D %~p1 extracts the path from variable %1 echo p0 = %~p0 produces \WINNT\system32\ %~dp1 pulls the drive letter and path echo dp0 = %~dp0 produces C:\WINNT\system32\ %~sp1 creates a short path (but no drive letter)

echo sp0 = %~sp0 produces \WINNT\system32

If I set %1 to "c:\Program Files\Internet Explorer" then %~sp1 produces \PROGRA~1\INTER. Note you have to wrap the long path in quotes otherwise the truncation doesn't work. %~x1 leaves only the command extension echo x0 = %~x0 produces .cmd %~nx1 extracts the file name and extension echo nx0 = %~nx0 produces x.cmd %~sx1 extracts the short extension from %0 echo sx0 = %~sx0 produces .cmd but a longer extension (.document?) would be cut down to .doc

%~dp0 VS %cd% http://www.computerhope.com/forum/index.php?topic=54333.0 %cd% is available either to a batch file or at the command prompt and expands to the drive letter and path of the current directory (which can change e.g. by using the CD command)

%~dp0 is only available within a batch file and expands to the drive letter and path in which that batch file is located (which cannot change). It is obtained from %0 which is the batch file's name.

An experiment like the following shows the difference

Here is D:\dirshow.bat:

Code: @echo off echo this is %%cd%% %cd% echo this is %%~dp0 %~dp0

Run it from C:\ and this is what you see Code: C:>D:\dirshow.bat this is %cd% C:\ this is %~dp0 D:\