http://bugs.winehq.org/show_bug.cgi?id=657
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #59 from Jerome Leclanche adys.wh@gmail.com 2010-09-03 23:07:07 CDT --- (In reply to comment #58)
I'll take this to the list before filing a bug, to get opinions on it. Sure there are higher priorities, but I've seen some lower priority things sneak in lately. :-)
Brain food.
I agree this should be at least reopened. Just because it wont be fixed "just yet" doesn't mean it never will.
Now, what could be done in a more... human time scale is implement the most common functions from MFC42. Having a stub dll and maybe a couple doz^M^M^Mhundred functions should fix a handful of issues.
The MFC42 source is available with Visual Studio. What are the implications for Wine? Even though developers are not allowed to reuse that source in Wine, are they allowed to at least look at it in order to implement functions properly?
What's amazing with Wine is how hundreds of users will create patches for their own issues, for their own app. If an app crashes because MFC42.dll is missing, the current solution is "winetricks and that's it". Having a stub dll, even if it has to warn on every load "MFC42 is poorly supported. If you have issues, try native.", could get us patches to slowly support it more and more.
Ok, yeah, this is an insane project; but so is Wine, and it's doing well so far. This could even be done during GSoC, and before you know it, pops-your-knuckle we have a MFC42.dll good enough for most apps.
Once again, just brain food.
-
wine-bugs＠winehq.org