https://bugs.winehq.org/show_bug.cgi?id=45212
--- Comment #17 from Fabian Maurer dark.shadow4@web.de ---
As a result of this the pointer to the handle is returned as a null. So, there is nothing for the calls to findconnectionpoint will fail because of the null pointer.
Actually, that's not how it works. In face, I doubt the two things are even related. I don't want to go into too much detail here, but the endpoint stuff is for registering a callback to IPicture, so it can notify when it's finished. But the program requests a callback in the form of 33AD4ED2-6699-11CF-B70C-00AA0060D393 (IPictureBoxEvents) which wine doesn't know. It's a VB6 specific interface, and while I have no idea why oleaut32 would accept that, I'm gonna write some tests to check that behavior tomorrow.
So, not understanding at all how all of this fits into wine, is it save to say these .c files are used at build time for wine?
Sure, sources are compiled into a binary.
If so, then overriding with oleaut32.dll wouldn't actually do anything would it?
Uh, no, I don't see how this would follow. It's replacing the wine binary with the windows binary, sources don't matter for that.
I don't understand at all how run time libraries work (dll for windows, so files for linux?). From my old C experience, which is more than just a LITTLE bit rusty ;) I would have thought the .c files had to be included at compilation time.
Well, the sources are turned into a binary. But when you replace the binary, it should work.