On 06/14/16 21:22, Alex Henrie wrote:
Correct me if I'm wrong, but as I remember those exports are only used when you mix some of native dlls from vcrun2015 with some of builtins. Like when application imports from api-ms-* one, which is actually installed with vcrun2015 redist. What I mean is that such mixed environment exposes such glue exports that normally are not used directly, that could potentially qualify as implementation details. I'll be happy to be wrong about that.
I'm not sure if we should qualify them as implementation detail taking in account the functions are exported. I don't know if any real application uses them but as long as it's a simple forward to function without _base in name I don't see anything wrong in implementing them.
Anyway I don't think it's obvious that FUNCTION_base is identical as FUNCTION.
Can a reimplemented msvcp140.dll be included in Wine? If so, we can drop patches 2-4 of this series and work on this new DLL instead.
Sure, msvcp140.dll can (and should) be included in wine. It may be not that easy though. As far as I remember vcruntime140 is missing many functions that are needed to build msvcp*. I'm not sure if all of them are available in e.g. api-* dlls.
Thanks, Piotr