On 8/19/2015 04:34, Greg Jung wrote:
> You shouldn't have t make any part of the toolchain, they are there to be
> installed from cygwin setup. The names go like "mingw64-x86_64-gcc-g++"
> etc. (no mingw32 mentioned).
>
> For usage instructions, there should be something on cygwin.org. It might
You shouldn't have t make any part of the toolchain, they are there to be
installed from cygwin setup. The names go like "mingw64-x86_64-gcc-g++"
etc. (no mingw32 mentioned).
For usage instructions, there should be something on cygwin.org. It might
be as simple
as inserting /usr/x86_64-w64-ming
---
mingw-w64-headers/include/dxva2api.idl | 320
++---
1 file changed, 139 insertions(+), 181 deletions(-)
diff --git a/mingw-w64-headers/include/dxva2api.idl b/mingw-w64-headers/include/dxva2api.idl
index 007a2e4..8aa0389 100644
--- a/mingw-w64-headers/include/dxva2
On 08/17/15 20:20, David Grayson wrote:
> On Tue, Aug 11, 2015 at 6:22 AM, Jacek Caban wrote:
>> The patch looks good to me.
> I think it's good too, but it looks like it (intsafe_2.2.1.patch)
> hasn't been committed to the git repository. Can someone commit it?
Sorry for the delay, I was hoping
Hi there,
I installed x86_64-w64-mingw32-gcc collections from Cygwin setup and want to
know what to do
next to make the "x86_64-w64-mingw32-*" tools (x86_64-w64-mingw32-gcc,
x86_64-w64-mingw32-g++,
x86_64-w64-mingw32-ar, ...) function as being called like "gcc, g++, ar...".
The link
(http://
