Visual Studio 2015 compiled Versus MinGW cross-compiled code?
thaleslv at yahoo.com
Sat Nov 16 16:24:16 CST 2019
Okay, I decided to build my Visual Studio 2015 test application using mingw in Ubuntu as a separate project. When I did this, the test successfully showed the problem when run in Wine, whereas with Windows it worked fine. This means that with NT version 4 the problem also arises.
I don't know exactly what accounts for the difference between that and the test as I set it up in dlls/comctl32/tests/combo.c. That's what I'll look into now.
Regards,...John Alway On Friday, November 15, 2019, 11:30:53 PM CST, Thales <thaleslv at yahoo.com> wrote:
When I change the MajorOperatingSystemVersion field in the PE files (I mistakenly referred to MajorSubsystemVersion above) for both the wine cross compiled and the Windows Visual Studio 2015 version, the performance of neither changed.
Also, I realized that the version of mingw does default to 4. I read the wrong field.
I'm pursuing another approach now.
On Friday, November 15, 2019, 04:13:10 PM CST, Stefan Dösinger <stefandoesinger at gmail.com> wrote:
Am 15.11.19 um 03:03 schrieb Thales:
> Just for the record, in the "Optional Header," under the category
> "MajorSubsystemVersion," the mingw created PE binary has NT version 4
> (released 1996), whereas the Visual Studio 2015 PE binary has it set to
> NT version 6 (released 2008).
> So, it's exactly as you said!
Does this cause the behavior difference you see? If you edit the header
manually, does the mingw build get the msvc behavior and vice versa?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wine-devel