Difference between revisions of "Porting/Wine"

From RCS Wiki
Jump to navigation Jump to search
(One intermediate revision by one other user not shown)
Line 3: Line 3:
  
 
== Status ==
 
== Status ==
Initial compilation hurdles fixedwine_call_on_stack() needs a proper port, applications currently crash after entering wine_call_on_stack()
+
[[File:Wine_demo_1.png|thumb|Command line]]
 +
[[File:Wine_demo_2.png|thumb|Wine configuration]]
 +
Initial port completewinecfg starts and runs on ppc64el systems (64k page size tested).
  
 
== To-Do==
 
== To-Do==
* Finish updating wine_call_on_stack() for ppc64 systems
+
* Add ppc64 (big endian) support
* Verify newly written stub assembly / thunking for ppc64 systems
 
* Update register save/restore in winedbg for ppc64
 
* ???
 
  
 
== 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
 +
 +
[[Category:Ports]]

Revision as of 21:18, 5 March 2019

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

Command line
Wine configuration

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):