Re: [Mingw-w64-public] New directx header from wine?

2017-10-11 Thread Jacek Caban
On 11.10.2017 14:18, Shinchiro Shinchiro wrote: > On Wed, Oct 11, 2017 at 6:38 PM, Jacek Caban  wrote: > > Oh, right, I didn't mean to commit that at all. The problem is > that mingw-w64 version of widl crashes on that IDL. It needs an > investigation (and probably identifying and backp

Re: [Mingw-w64-public] New directx header from wine?

2017-10-11 Thread Shinchiro Shinchiro
On Wed, Oct 11, 2017 at 6:38 PM, Jacek Caban wrote: > Oh, right, I didn't mean to commit that at all. The problem is that > mingw-w64 version of widl crashes on that IDL. It needs an investigation > (and probably identifying and backporting a fix from Wine). > Oh yeah, I get it too. I wonder why

Re: [Mingw-w64-public] Getting started and widl problems

2017-10-11 Thread Jacek Caban
On 11.10.2017 12:47, Leif AMO wrote: > On 2017-10-10 17:13, Jacek Caban wrote: >> Importing from Wine is scripted, but the script for that is not >> public for quite a while. We used to have it in experimental branch >> of SVN, but it didn't survive move to Git. I maintain a local copy of >> it, bu

Re: [Mingw-w64-public] Getting started and widl problems

2017-10-11 Thread Leif AMO
On 2017-10-10 17:13, Jacek Caban wrote: Importing from Wine is scripted, but the script for that is not public for quite a while. We used to have it in experimental branch of SVN, but it didn't survive move to Git. I maintain a local copy of it, but I failed to do the right thing and upstream a

Re: [Mingw-w64-public] New directx header from wine?

2017-10-11 Thread Jacek Caban
On 11.10.2017 12:25, Shinchiro Shinchiro wrote: > On Wed, Oct 11, 2017 at 5:23 PM, Jacek Caban wrote: > > They were not really excluded, but simply not added. The update > was huge already, I wanted to do that separately. I committed it > now, please give it a try. > > > btw, I just not

Re: [Mingw-w64-public] New directx header from wine?

2017-10-11 Thread Shinchiro Shinchiro
On Wed, Oct 11, 2017 at 5:23 PM, Jacek Caban wrote: > They were not really excluded, but simply not added. The update was huge > already, I wanted to do that separately. I committed it now, please give it > a try. > btw, I just noticed the 'dxgi1_6.h' is 0 byte file after cloning it -

Re: [Mingw-w64-public] New directx header from wine?

2017-10-11 Thread Shinchiro Shinchiro
On Wed, Oct 11, 2017 at 5:23 PM, Jacek Caban wrote: > They were not really excluded, but simply not added. The update was huge > already, I wanted to do that separately. I committed it now, please give it > a try. > Nice, thanks

Re: [Mingw-w64-public] New directx header from wine?

2017-10-11 Thread Jacek Caban
On 10/11/17 5:15 AM, Shinchiro Shinchiro wrote: Is there a reason why latest pull from wine doesn't include new directx file like d3d11_3 and such? They were not really excluded, but simply not added. The update was huge already, I wanted to do that separately. I committed it now, please giv

Re: [Mingw-w64-public] problem with multiple defined symbolsinuuidanda patch

2017-10-11 Thread ralph engels
Yeah i forgot so i guess that ones on me, still a few Things about git i have to remember. He did not take it to hard since he was more interrested in getting the fix in than in who made what 😊 Sendt fra Mail til Windows 10 Fra: JonY via Mingw-w64-public Sendt: 11. oktober 2017 01:37 Til: ming