黑莓 RIM 签名工具出现问题
我有一些使用 Visual Studio 的 Widget 工具包开发的 COD 文件。这些 COD 文件需要先进行签名，然后才能在设备上使用它们。
当我从 Eclipse (3.4.0) 中打开签名工具时，当前工作区中的每个 COD 文件都会显示在列表中。如果我点击“添加”按钮并选择我想要从另一个位置签名的 COD 文件，则该 COD 文件不会与所有其他文件一起列出。
我尝试从命令行运行签名工具，但发生了同样的事情。我点击“添加”，选择 COD 文件，然后什么也没发生。如果我在命令行上指定 COD 文件，则会收到一条错误消息，指出签名工具找不到任何 COD 文件。
唯一的例外是今天，就在我去吃午饭之前。当我单击“添加”并选择 COD 文件时，它出现在列表中，我可以按预期对其进行签名，但每次我尝试时它都不起作用。
关于正在发生的事情或我可以采取的任何其他方法有什么建议吗？
I have some COD files that I have developed using the Widget toolkit for Visual Studio. These COD files need to be signed before I can use them on a device.
When I open the Signature Tool from within Eclipse (3.4.0) every COD file from the current workspace is shown in the list. If I hit the 'Add' button and select the COD file I want to sign from another location the COD file isn't being listed with all of the other files.
I tried running the Signature Tool from the command line and the same thing happens. I hit Add, select the COD file and then nothing happens. If I specify the COD file on the command line then I get an error saying that the Signature Tool can't find any COD files.
The only exception to this was today, just before I went for lunch. When I clicked Add and selected the COD file it appeared in the list and I could sign it as expected but every other time I've tried it doesn't work.
Any suggestions as to what is happening or any other approaches I can take?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们使用 BlackBerry Ant Tools 从命令行进行签名，效果非常好。它所做的只是启动实际的 RIM 签名工具，但它负责传递正确的文件列表和（可选）您的签名密码 - 因此它或多或少可以自动化。除了 RIM 签名服务器偶尔宕机之外，我没有遇到过任何问题。
We use the BlackBerry Ant Tools for signing from the command line and it works great. All it does it launch the actual RIM signing tool but it takes care of passing in the correct list of files and (optionally) your signing password - so it can be more or less automated. I haven't encountered problems with it other than the odd time when RIM's signing servers are down.
问题是生成的 .csl 和 .cso 文件不存在于同一目录中，因此签名工具不知道需要签名哪个 API。
The issue was that the generated .csl and .cso file was not present in the same directory so the signature tool wasn't aware of which API's needed signed.