-------- Forwarded Message --------
Subject: No more binary components in extensions
Date: Mon, 4 May 2015 11:03:12 -0400
From: Benjamin Smedberg <benjamin@xxxxxxxxxxxx>
Reply-To: dev-extensions@xxxxxxxxxxxxxxxxx
To: dev-platform <dev-platform@xxxxxxxxxxxxxxxxx>, Firefox Dev
<firefox-dev@xxxxxxxxxxx>, dev-extensions@xxxxxxxxxxxxxxxxx
(Followup questions or comments to mozilla.dev.extensions only, please.)
With the landing of bug 1159737, I have removed support for binary XPCOM
components in extensions. This is planned to ride the Firefox 40 train.
This change is necessary because we no longer expose or intend to expose
a binary-stable API to XPCOM. Most addons have already moved away from
binary XPCOM components, but those that haven't are a source of
instability around Firefox releases.
Extension authors that need to use native binaries are encouraged to do
so using the addon SDK "system/child_process" pipe mechanism:
https://developer.mozilla.org/en-US/Add-ons/SDK/Low-Level_APIs/system_child_process
If this is not sufficient, JS-ctypes may be an alternative mechanism to
use shared libraries, but this API is much more fragile and it's easy to
write unsafe code.
I will be updating MDN documentation and removing or archiving old
documentation about binary XPCOM components in the next few weeks.
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@xxxxxxxxxxxxxxxxx
https://lists.mozilla.org/listinfo/dev-platform
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
