http://bugs.winehq.org/show_bug.cgi?id=10126
James McKenzie jjmckenzie51@sprintpcs.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #6 from James McKenzie jjmckenzie51@sprintpcs.com 2007-10-27 22:57:09 --- 1. I used a proper compile of Wine. It was from THIS SITE and compiled using the instructions on the Building Wine for Mac OS X. Please explain, in great detail, why this is not a "proper build". If you consider that a 'proper build' ls Linux, you are massively wrong my friend as the Wine project is for Linux/UNIX/Mac OS X/OS/2 and other operating systems. I don't like beating folks over the head in a public forum, but you have left me little or no other choice. 2. Wine does work on the Mac, as demonstrated on MikesMassiveMess, where I am getting Darwine builds that also exhibit this behaviour. Mike spent alot of his personal time getting Darwine to work on the Intel Mac side, properly with corefonts, Fontforge and freetype. 3. Getting .NET to work should be a priority, not just 'Go get Mono' Mono DOES NOT WORK UNDER WINE AND NEVER WILL. User's need an 'install and go' application that will run their Windows Applications. .NET is becoming more and more embedded into Windows Applications. For instance there is a bug for Tomb Raider 6, which was build using Visual Studio 2003. As a VS product, .NET is embedded, if only for the installer. 4. I will continue to look for 'fixes' and apply them to see if they work/do not work in the Mac OS X environment that work with Linux. Remember, these are two different 'animals' and thus will behave differently when fixes are applied (or attempts to do so are. 5. One of the fixes for bug 5358 may or may not work in the Mac installation environment. I will try this for the program that is complaining about the lack of .NET 1.1.