A few weeks ago when I thought how cool it would be to marry Wine and Bochs to run Windows progams on Mac OS X & Darwin, I checked around, including this list, and didn't find any activity.
This issue comes up a few times a year (isn't it in a FAQ somewhere?) Anyway, take a look at these threads:
http://kt.zork.net/wine/wn20020830_133.html#3
http://bugs.winehq.com/show_bug.cgi?id=44
http://www.winehq.com/hypermail/wine-devel/2000/11/0004.html
http://www.winehq.com/hypermail/wine-devel/2000/11/0077.html
The fact that you're using Bochs does make it unique, but you may still glean some useful info from those links.
-brian vincent
This issue comes up a few times a year (isn't it in a FAQ somewhere?) Anyway, take a look at these threads:
Yeah, this is one of the most persistant 'Wine dream' around :-)
I had once a long discussion with a fellow hacker on this subject (going into the likes of using Valgrind's virtualization engine to output non-X86 code to do dynamic translation and so on). We agreed that before starting with Wine, one could start with running, for example, Linux/x86 binaries on Linux/PPC. That would already validate the fact that you can draw the line at one point and from there run such an heterogenous environment.
It's a very nice subject... A pitty it has such a low importance (seeing how X86 dominates the desktop market).
Lionel
Lionel Ulmer wrote:
I had once a long discussion with a fellow hacker on this subject (going into the likes of using Valgrind's virtualization engine to output non-X86 code to do dynamic translation and so on). We agreed that before starting with Wine, one could start with running, for example, Linux/x86 binaries on Linux/PPC. That would already validate the fact that you can draw the line at one point and from there run such an heterogenous environment.
Hey, that's a good idea. Then you could install and run x86 linux packages, if you were really lucky. Might be useful for running proprietary packages where they don't bother to rebuild for linux/ppc. - Dan
Dan Kegel wrote:
Lionel Ulmer wrote:
We agreed that before starting with Wine, one could start with running, for example, Linux/x86 binaries on Linux/PPC. That would already validate the fact that you can draw the line at one point and from there run such an heterogenous environment.
Hey, that's a good idea. Then you could install and run x86 linux packages, if you were really lucky. Might be useful for running proprietary packages where they don't bother to rebuild for linux/ppc.
Yes, it would be terrific if someone were to do some porting for Linux/PPC. Wine and Bochs certainly work quite well with Linux.
For my part, I plan to start with a trial port to Darwin/x86.
If those two things happened in parallel, that would save a lot of time and definitely bring more expertise to bear on the many issues.
Jim
Brian Vincent wrote:
This issue comes up a few times a year (isn't it in a FAQ somewhere?) Anyway, take a look at these threads:
Yes it is a bit of a FAQ, and the answers have mostly been along the lines of "just use Winelib for non-Intel machines". Now it can be "... and checkout the Darwine BOF".
Thanks for the links!
Lionel Ulmer wrote:
It's a very nice subject... A pitty it has such a low importance (seeing how X86 dominates the desktop market).
Supposedly Mac OS X already has the largest installed base of any single *nix distribution and certainly is ahead of Linux on the desktop. So there are easily as many potential users of Wine for Mac OS X as Wine for X86-whatever. And Virtual PC has been popular & successful.
Dan Kegel wrote:
Sounds like a plan to me. Hopefully your Wine tree won't drift out of sync with the main one like so many Linux kernel port trees do.
Yep, keeping things in sync will be important. In checking out Winehq distrbution, I see that updates revolve arond the monthly tarballs. So that's where we'll start and try to keep up-to-date with that.
Thanks for the encouragment!
Jim
-
Brian Vincent -
Dan Kegel -
Jim White -
Lionel Ulmer