Hi all,
After about a year since the last release, I'm happy to announce that we have a new Wine Gecko packages ready for testing. I'm not attaching a patch this time, because it's quite big and will change over next few weeks (I will be submitting some of those changes, so the patch would be invalid soon). I set up a Wine fork at [1] instead. It contains snapshot of my development tree on top of Wine, so be prepared for forced updates. Let me know if you'd prefer it to be in a different form.
This update catches up on development made for 10 Firefox releases that happened meantime. There were many problems that needed to be solved for this to happen. There were tree wide changes breaking our build config as well as API changes, that needed to be fixed. We still have long term problem with API that we use for embedding Gecko (mostly DOM APIs) that is slowly removed from Gecko. We need a long term solution, which means working on auto generated C/C++ bindings based on the new, WebIDL files. I may write a separated mail about that if there is an interest.
I decided to make this beta from Gecko tip at the point where it's branched. I usually waited until Gecko enters beta, but I want to catch up on development as much as possible this time. How the final release will look like depends on how testing goes. It will not be sooner than after a bit of Firefox beta.
As usually, everything that uses MSHTML is an interesting testing target. Let me know if there are any problems.
Thanks, Jacek
Hi Jacek,
On Wed, Sep 24, 2014 at 9:42 PM, Jacek Caban jacek@codeweavers.com wrote:
We need a long term solution, which means working on auto generated C/C++ bindings based on the new, WebIDL files. I may write a separated mail about that if there is an interest.
Thanks for the hard work on wine gecko! For the WebIDL topic, I believe it is interesting and appreciated :)
BTW, as we discussed in MN, could we host a read-only public mailing list or similar things to monitor wine-gecko daily build failures?
Looking forward to the new wine gecko release.
On 09/24/14 16:51, Qian Hong wrote:
Hi Jacek,
On Wed, Sep 24, 2014 at 9:42 PM, Jacek Caban jacek@codeweavers.com wrote:
We need a long term solution, which means working on auto generated C/C++ bindings based on the new, WebIDL files. I may write a separated mail about that if there is an interest.
Thanks for the hard work on wine gecko! For the WebIDL topic, I believe it is interesting and appreciated :)
OK, I will write a separated mail about it soon.
BTW, as we discussed in MN, could we host a read-only public mailing list or similar things to monitor wine-gecko daily build failures?
We can't really monitor wine-gecko daily. wine-gecko is updated only when I do merges (in the past it was about once a week and I hope to go back to this strategy). I always make sure that it builds and that Wine can use it after such merge.
However, we may build on top of Gecko (mozilla-central) tree. That's where most build problems come from (the diff between those branches are our modifications for Wine). I thought about it a bit. I have a cron job that builds Gecko tip nightly on my box. The easy way would be for this cron job to send a mail to such mailing list. However, I'm not sure that's a good idea. The tip usually needs some patches on top of it to build, so it's not really usable for people without them. I could publicize those patches, but then we have a pretty complicated situation anyway.
We were also talking about more ambitious solution of setting up build bot. That's much more work, but it also has way more benefits. It would be great to have such thing working, but I can't spend too much time on it. If we had a volunteer to do that, I'm happy to talk about it.
Jacek
On 10/01/14 14:00, Jacek Caban wrote:
The tip usually needs some patches on top of it to build,
To be clear, those are always on their way to upstream. The problem is that for some of them, it take a while.
Jacek
-
Jacek Caban -
Qian Hong