On 8/30/2016 8:44 AM, Benjamin Smedberg wrote: > It is likely that this project will affect Thunderbird and/or SeaMonkey, > but I'm not sure in what ways. My understanding is that Thunderbird > currently builds with internal linkage. I plan to keep Thunderbird informed > of the work here, and accepting patches that help Thunderbird stay > building, but I do not intend to significantly delay or WONTFIX this > Firefox work for Thunderbird.
Thunderbird 45 (based on m-esr45) has allowed binary extensions, but we have agreed for some months now that Thunderbird 52 will no longer support binary extensions. The extensions are currently only used by addons closely closely connected to the core project. Even at TB 45 there were significant changes in m-c that made using a binary extension very challenging, and the assumption has been that ongoing changes, such as the ones you are suggesting here, would make that impossible. I am not aware of any existing parts of shipping Thunderbird that use external linkage, but if there are any that would be something that needs removing or fixing. That being said, there has been some pushback on this due to the performance costs of using JS instead of C++. If major breaking changes could be delayed until Gecko 53, or if it was possible to have some build options that would allow external linkage as an option, that would be good. But we could live without it. :rkent _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
