flex builder 3 编译器不会显示错误或编译特定页面
在 flexbuilder 3 中，对于某些 mxml 文件，我可以故意放入语法错误，编译器似乎会编译特定页面（但实际上不会编译它）或报告该页面的任何错误。您知道有什么方法可以让编译器向我报告错误，以便我可以让它编译页面。我已经尝试重建所有项目并清理项目。
In flexbuilder 3 for some mxml files I can purposely put in syntax errors and the compiler will seem to compile the specific page(but actually not compile it) or report any errors for that page. Is there any way that you know of to get the compiler to report the errors to me so I can get it to compile the page. I've tried rebuilding all and cleaning the project already.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
听起来您实际上并没有在应用程序中的任何地方使用该页面。默认情况下，mxmlc 仅编译主类（直接或间接）引用的类。
Sounds like you're not actually using that page in your application anywhere. mxmlc only compiles classes that are referenced by the main class (directly or indirectly) by default.
如果未使用该组件；编译器会忽略它。
如果您使用的是图书馆项目；确保该组件已添加到库中。您可以在项目设置中执行此操作。
如果您使用的是 Flex 项目；确保该组件在应用程序中的某个地方实际使用。否则，它会从最终的 swf 中“优化”出来，并且永远不会被编译器处理。
IF the component is not used; the compiler will ignore it.
If you're using a Library project; make sure that the component is added into the library. You can do this in project settings.
If you're using a Flex Project; make sure that the component is actually used in the application somewhere. Otherwise it is "optimized" out of the final swf and never given the compiler treatment.
我能够通过从命令行编译来解决这个问题。 此处是文档的链接任何感兴趣的人（查看“使用 Flex 编译器”）
从命令行编译时，我能够让编译器实际告诉我发生了什么错误，以便我可以修复它。
I was able to get around this by compiling from the command line. Here is a link to the documentation for anyone interested(Look under Using the Flex Compilers)
When compiling from the command line I was able to get the compiler to actually tell me what error was occurring so I could fix it.
我有同样的问题。就我而言，项目路径中有一个空格。我将该文件夹重命名为不带空格并重新打开 Flex 构建器。然后编译错误开始按预期出现。此外，您还应该自动打开 Project>Build。
I had the same issue. In my case, the project path had a space in it. I renamed the folder to be without a space and reopened flex builder. Then the compilation errors started showing up as expected. Also you should have Project>Build automatically turned on.