Binary compatibility 编辑

If Mozilla decides to upgrade to a compiler that does not have the same ABI as the current version, any built component may fail. It is a possiblity that is introduced when upgrading to a new compiler without recompiling everything. Effectively, it is a different platform.

What does this mean to you? If you build a component and it works fine in version 1.0 of Mozilla. If and when Mozilla upgrades the compiler they use, your component will have to be rebuilt against the same compiler.

When you see a @status FROZEN, note that this means it should work as long as the component and xpcom are built with the same compiler ABI.

For more information on issues of componentization and binary compatibility, see http://mozilla.org/projects/xpcom/gl...ent_Reuse.html .

Comments and questions should be directed to the newsgroup, mozilla.dev.tech.xpcom, or the mailing list, mozilla-xpcom@mozilla.org.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:93 次

字数:1165

最后编辑:6年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文