On 4/13/14, Alexpux <alex...@gmail.com> wrote: > > 13 апр. 2014 г., в 22:44, Alexpux <alex...@gmail.com> написал(а): > >> >> 13 апр. 2014 г., в 22:39, Ozkan Sezer <seze...@gmail.com> написал(а): >> >>> On 4/13/14, Ray Donnelly <mingw.andr...@gmail.com> wrote: >>>> Can someone with commit rights take care of this for us please? >>>> >>>> Best regards, >>>> >>>> Ray. >>>> >>>> On Sun, Apr 13, 2014 at 5:35 PM, Kai Tietz <ktiet...@googlemail.com> >>>> wrote: >>>>> 2014-04-13 17:52 GMT+02:00 Ozkan Sezer <seze...@gmail.com>: >>>>>> On 4/13/14, Ray Donnelly <mingw.andr...@gmail.com> wrote: >>>>>>> Seems 3 imports were listed as C++ functions when they are plain C >>>>>>> functions. >>>>>>> >>>>>>> The attached patch corrects this. >>>>>>> >>>>>>> Qt Creator 3.1.0-rc1 built with Qt-5.3.0-beta1 using Angleproject >>>>>>> could not resolve dll imports without this change. >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Ray. >>>>>>> >>>>>> >>>>>> According to wine (wine/dlls/d3d9/), Direct3DShaderValidatorCreate9 >>>>>> must be a stdcall like Direct3DShaderValidatorCreate9@0. According to >>>>>> wine again, several other exports in the def file are wrong too, e.g. >>>>>> stdcall funcs DebugSetMute@0, D3DPERF_EndEvent@0, >>>>>> D3DPERF_GetStatus@0, >>>>>> D3DPERF_QueryRepeatFrame@0, some of whose prototypes are actually >>>>>> available so easy to confirm. However PSGPError, PSGPSampleTexture, >>>>>> and DebugSetLevel are unknown. Many of these are undocumented, btw. >>>>>> >>>>>> -- >>>>>> O.S. >>>>> >>>>> Such .def file changes are preapproved. Please apply. >>>>> >>>>> Regards, >>>>> Kai >>>>> >>>> >>> >>> Pushed these revisions to svn: >>> >>> trunk: rev. 6566 >>> stable/v3.x: rev. 6567 (direct merge of r6566) >>> stable/v1.x and v2.x: rev. 6568 (merge of r5111 and 6566) >>> >> I see you comment PSGPError and another function in d3d9.def. Maybe you >> need do it on 64-bit .def too? > > I create def file from c:\windows\SysWOW64\d3d9.dll > http://pastebin.kde.org/p2apqxdii > > And commented functions present in library. Why you comment them?
For x86 they are most possibly __stdcall (WINAPI) and we don't know their exact signatures, therefore it is best that we comment them out. For x86_64, there is no __stdcall so they are fine as they are, that's why I didn't comment them out in the x86_64 defs. -- O.S. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
