Difference between revisions of "Porting/Wine"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
== Status == | == Status == | ||
| − | Initial | + | [[File:Wine_demo_1.png|thumb|Command line]] |
| + | [[File:Wine_demo_2.png|thumb|Wine configuration]] | ||
| + | Initial port complete. winecfg starts and runs on ppc64el systems (64k page size tested). | ||
== To-Do== | == To-Do== | ||
| − | * | + | * Add ppc64 (big endian) support |
| − | |||
| − | |||
| − | |||
== Initial patches == | == Initial patches == | ||
Semi-monolithic (will be split further when closer to merge): | Semi-monolithic (will be split further when closer to merge): | ||
* https://github.com/madscientist159/wine | * https://github.com/madscientist159/wine | ||
Revision as of 23:38, 25 February 2019
Contents
Why?
One word: winelib! There are several large open source projects that, for one reason or another, targeted Windows at their genesis. Many of these projects are quite old, well established, and would take many man-centuries of work to rewrite for native Linux systems. Enabling wine on ppc64 gets us a cheap way to allow these projects to run (when built from source) on ppc64 systems via winelib.
Status
Initial port complete. winecfg starts and runs on ppc64el systems (64k page size tested).
To-Do
- Add ppc64 (big endian) support
Initial patches
Semi-monolithic (will be split further when closer to merge):
