Difference between revisions of "Porting/Wine"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
== Status == | == Status == | ||
− | Initial compilation hurdles fixed. | + | Initial compilation hurdles fixed. wine_call_on_stack() needs a proper port, applications currently crash after entering wine_call_on_stack() |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== To-Do== | == To-Do== | ||
Line 33: | Line 12: | ||
== Initial patches == | == Initial patches == | ||
− | + | Semi-monolithic (will be split further when closer to merge): | |
− | * https:// | + | * https://github.com/madscientist159/wine |
Revision as of 03:24, 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 compilation hurdles fixed. wine_call_on_stack() needs a proper port, applications currently crash after entering wine_call_on_stack()
To-Do
- Finish updating wine_call_on_stack() for ppc64 systems
- Verify newly written stub assembly / thunking for ppc64 systems
- Update register save/restore in winedbg for ppc64
- ???
Initial patches
Semi-monolithic (will be split further when closer to merge):