Thunderbird/Backend/libxul: Difference between revisions

no edit summary
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 52: Line 52:


* Developers would have to re-build mailnews and re-link libxul to be able to test changes (assuming shared configuration is also not supported).
* Developers would have to re-build mailnews and re-link libxul to be able to test changes (assuming shared configuration is also not supported).
=== Option 3 - Static libxul linked into Thunderbird executable ===
This is building core in the libxul style, but then linking it into the Thunderbird executable. Essentially this ends up the same build as what we've got now for static builds.


== The way forward ==
== The way forward ==
Line 65: Line 69:
# (depending on what is likely to happen for shared builds) Finish work on the frozen API and fix any outstanding issues.
# (depending on what is likely to happen for shared builds) Finish work on the frozen API and fix any outstanding issues.
# (depending on what is likely to happen for shared builds) Support option 1 for developers, potentially dropping fully-shared build support depending on mozilla-central.
# (depending on what is likely to happen for shared builds) Support option 1 for developers, potentially dropping fully-shared build support depending on mozilla-central.
== Tracking bugs ==
* {{bug|585947}} - Main tracking bug for libxul in Thunderbird work
=== Other related bugs ===
* {{bug|432162}} - Can't Build mailnews with libxul or XULRunner
* {{bug|306324}} - Build/run Thunderbird on top of XULRunner ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=306324&hide_resolved=1 dependency tree])
** This is not a requirement for libxul (and not a current aim for Thunderbird), however the dependences are mainly required for option 1.
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,627

edits