i386 架构元数据格式错误 - LLVM 错误
在我的一个项目中，我从编译器中收到了一个极其令人沮丧的错误。在更改了一些编译器设置以进行优化之后，一切都运行良好，直到我尝试在模拟器上进行测试。我收到此错误：
ld: in /Users/eric/Library/Developer/Xcode/DerivedData/My_Awesome_App-
hcpskretrcpxnuctkkvwptohgmib/Build/Intermediates/My_Awesome_App.build/Debug-
iphonesimulator/My_Awesome_App.build/Objects-normal/i386/main.o, could not parse object
file /Users/eric/Library/Developer/Xcode/DerivedData/My_Awesome_App-
hcpskretrcpxnuctkkvwptohgmib/Build/Intermediates/My_Awesome_App.build/Debug-
iphonesimulator/My_Awesome_App.build/Objects-normal/i386/main.o: Malformed metadata record
for architecture i386
我尽我所能重置了编译器设置，但错误仍然存在。我尝试了 架构 i386 的格式错误的元数据记录中的建议，但仍然没有任何结果。我还能做些什么吗？喜欢将 Xcode/LLVM-GCC 重置为默认值吗？
I am getting an extremely frustrating error from the compiler in one of my projects. After changing a few compiler settings for optimization, things were working beautifully, until I tried to test on the simulator. I get this error:
ld: in /Users/eric/Library/Developer/Xcode/DerivedData/My_Awesome_App-
hcpskretrcpxnuctkkvwptohgmib/Build/Intermediates/My_Awesome_App.build/Debug-
iphonesimulator/My_Awesome_App.build/Objects-normal/i386/main.o, could not parse object
file /Users/eric/Library/Developer/Xcode/DerivedData/My_Awesome_App-
hcpskretrcpxnuctkkvwptohgmib/Build/Intermediates/My_Awesome_App.build/Debug-
iphonesimulator/My_Awesome_App.build/Objects-normal/i386/main.o: Malformed metadata record
for architecture i386
I reset the compiler settings as best as I could, but still the error persists. I tried the suggestions in Malformed metadata record for architecture i386 but still nothing. Any other things I can do? Like reset Xcode/LLVM-GCC to defaults?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
找到了 - 我将该项目的构建设置与两天前在外部硬盘上备份的同一项目的设置进行了比较，罪魁祸首是
Link-Time Optimization标志，它被设置为是。将其设置为NO解决了该问题。定期备份的另一个原因！Found it- I compared the project's build settings to the settings of the same project in a backup I had on an external HD from just two days ago, and the culprit was the
Link-Time Optimizationflag, which was set to yes. Setting it toNOfixed the problem. Another reason to keep regular backups!