MonoDevelop - 如何从编译中查看 stderr？
我正在使用 MonoDevelop 和 MonoTouch 来构建项目，但是每当 gcc 中出现编译错误时，它都会简单地说（在“构建输出”选项卡中）“进程已退出，代码为 1，命令：...”
问题是，我看不出 gcc 给出了什么错误。看起来 stderr 要么被忽略，要么被填充到日志文件中的某个地方。
我想如果我将该命令复制到终端窗口并运行它，我可能能够发现 gcc/stderr 输出，但它不会编译，因为命令行上的某些文件是 MonoTouch 设置的临时文件，并且它们在 MonoDevelop 尝试构建后被删除。
我尝试过：
- 将日志详细程度设置为诊断 在下面 MonoDevelop->Preferences->Build
- 在命令行上运行 mdtool 与 -v 并没有显示任何内容 gcc 输出或者
- 添加 --stderr=/Users/myname/somefile.txt 到mtouch命令行下 项目选项->iPhone Build->Extra 争论
..这些东西都不起作用。
那么..当 mtouch 运行它时，如何从 gcc 获取 stderr 输出？
I'm using MonoDevelop and MonoTouch to build a project, but whenever there is a compile error in gcc, it simply says (in the Build Output tab), "Process exited with code 1, command: ..."
The problem is, I can't see what error gcc gave. It looks like stderr is either ignored or stuffed into a logfile somewhere.
I thought I might be able to discover the gcc/stderr output if I copy that command to a terminal window and run it, but it won't compile because some of the files on the command line were temp files that MonoTouch setup, and they were removed after MonoDevelop tried to build.
I've tried:
- Setting Log Verbosity to Diagnostic
under
MonoDevelop->Preferences->Build - Running mdtool on the command line
with -v and that doesn't show me any
gcc output either - Adding
--stderr=/Users/myname/somefile.txt to the mtouch command line under
Project Options->iPhone Build->Extra
Arguments
.. none of those things work.
So.. how can I get the stderr output from gcc when mtouch runs it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
将“-v -v -v”添加到 iPhone 构建设置中构建配置的“额外参数”中。
Add "-v -v -v" to the "Extra Arguments" for your build configuration in the iPhone Build settings.
在构建结果窗口中，将鼠标悬停在导致错误的步骤的右端或单击导致错误的步骤。该行末尾将显示一个小图标。它看起来像一个椭圆形，有水平线穿过它。如果单击该按钮，您将看到在该构建步骤中运行的命令以及这些命令的输出。
In the build results window, mouse over the right end of or click on the step causing the error. A small icon will show up at the end of the line. It looks like an oval with horizontal lines going through it. If you click on that, you will see the commands that were run in that build step, as well as the output of those commands.