Dear folks,
I'd like to proposal a short talk on the topic "Full Stack on Wine".
"Full Stack" means "full software stack", for example, the attached image is a software stack for Chromium. Chromium depends on several libraries like gtk, sqlite3, libwebp, these libraries depend on some common libraries like cairo, pango, then those common libraries depend on lower level libraries like libpng, glib, finally they depend on a few basic libraries like gcc-libs and zlib.
In the plan of Full Stack on Wine, we are thinking about improving the compatibility of thousands of open source win32 libraries on top of wine, from bottom to top, layer by layer. At the same time, we are planing to collaborate with thousands of open source win32 projects, make Wine a useful build & testing & deployment platform for them, establish a win-win for both sides. The idea is inspired by http://wiki.winehq.org/UnitTestSuites , but not exact the same, I'll explain the details in the talk.
Thanks for contribution from many people, currently we've successfully build 300+ win32 open source projects on top of Wine (using win32 version of toolchain, instead of cross-compile), with the help of MSYS2 [1]. At the same time, we also made Cygwin almost work out of box on Wine.
In the final, I'd like to not only make a call of help, but also proposal some adjustment on the Wine project, to coordinate with some of our partner win32 open source projects, that would bring us to an open discussion.
The talk is relative short, about 15 mins. I'd really like to talk 15 hours, but thanks to god my spoken English is so poor so I couldn't ;-)
Thank you!
Dear folks,
Thanks for listening to my talk, I appreciate everyone join the discussion and provide feedback, all the opinions are very valuable. For folks who are not present at WineConf, I've attached my slide to http://wiki.winehq.org/WineConf2015?action=AttachFile&do=get&target=... , I'll also create a wiki page on Wine for the Full Stack on Wine idea later.
For people who want to test Cygwin/MSYS2 on Wine earlier, here is the step: 1. fetch latest Wine Staging source code 2. apply a wine hack from https://bugs.wine-staging.com/show_bug.cgi?id=561#c3 3. apply another wine hack from https://bugs.wine-staging.com/show_bug.cgi?id=404#c7 4. compile Wine Staging
Then it will be enough to have Cygwin/MSYS2 works like the slide said (gcc compiles, 300+ MSYS2 packages compiles, Qt compiles, etc). Enjoy!
See also https://github.com/fracting/wine-fracting/wiki/MSYS2-on-Wine#build-status for some other information.
All these will be collect to Wine wiki, I need some more time to do that.
Thank you!
2. apply a wine hack from
https://bugs.wine-staging.com/show_bug.cgi?id=561#c3 3. apply another wine hack from https://bugs.wine-staging.com/show_bug.cgi?id=404#c7
Maybe it would be easier for some if you squash both hacks in one diff patch and attach it here?
Cheers, Aaryaman
Hi Aaryaman,
On Mon, Sep 21, 2015 at 5:32 PM, Aaryaman Vasishta jem456.vasishta@gmail.com wrote:
Maybe it would be easier for some if you squash both hacks in one diff patch and attach it here?
Good advice, thank you very much, I attached my hack here.
On Sep 21, 2015 8:53 AM, "Qian Hong" fracting@gmail.com wrote:
Dear folks,
Thanks for listening to my talk, I appreciate everyone join the discussion and provide feedback, all the opinions are very valuable. For folks who are not present at WineConf, I've attached my slide to
http://wiki.winehq.org/WineConf2015?action=AttachFile&do=get&target=...
, I'll also create a wiki page on Wine for the Full Stack on Wine idea later.
For people who want to test Cygwin/MSYS2 on Wine earlier, here is the
step:
- fetch latest Wine Staging source code
- apply a wine hack from
https://bugs.wine-staging.com/show_bug.cgi?id=561#c3
- apply another wine hack from
https://bugs.wine-staging.com/show_bug.cgi?id=404#c7 4. compile Wine Staging
Then it will be enough to have Cygwin/MSYS2 works like the slide said (gcc compiles, 300+ MSYS2 packages compiles, Qt compiles, etc). Enjoy!
See also
https://github.com/fracting/wine-fracting/wiki/MSYS2-on-Wine#build-status
for some other information.
All these will be collect to Wine wiki, I need some more time to do that.
Thank you!
wineconf mailing list wineconf@winehq.org https://www.winehq.org/mailman/listinfo/wineconf
Howdy Qian,
Thanks for the presentation and the great work on this project! I'd like to contribute by testing/building some of the untested 700 packages, where can I find your build/Travis CI scripts?
Hey Austin,
On Tue, Sep 22, 2015 at 2:12 AM, Austin English austinenglish@gmail.com wrote:
Thanks for the presentation and the great work on this project! I'd like to contribute by testing/building some of the untested 700 packages, where can I find your build/Travis CI scripts?
Thanks a lot for your great support!
Currently I'm in vacation so my reply is slow, sorry for that!
Here is the Travis CI scripts last time I use: https://github.com/fracting/msys2-scripts
However, it is outdated, many situation has been changed in the past few weeks, so I won't recommend you to have a try. Besides, we are still needing a real fix for those two hacks I mentioned in the previous mail before we can actual using MSYS2 in Travis CI, that would take some time. I will update my scripts soon after back from vacation, and I'll definitely call you for help when I'm ready ;-)
Before that, if you don't mind patch Wine-Staging locally with my hacks, then I think this wiki is good enough for you to build some MinGW packages locally: http://sourceforge.net/p/msys2/wiki/Contributing%20to%20MSYS2/
Cheers from Munich and looking forward to discuss with you for more details!
Thanks!