Hi Алексей,
On Jun 8 12:49, Алексей Павлов wrote:
> I recreate git repository on msys2.sf.net.
> Now master branch point to MSYS2 source and when you go to code page on
> sf.net you get page with MSYS2 source.
Thank you, that's much better. This allows an unaware user to access
the correct sou
---
mingw-w64-headers/include/dxva2api.h | 2 ++
mingw-w64-headers/include/dxva2api.idl | 2 ++
2 files changed, 4 insertions(+)
diff --git a/mingw-w64-headers/include/dxva2api.h
b/mingw-w64-headers/include/dxva2api.h
index 3ab4842..bb67f3c 100644
--- a/mingw-w64-headers/include/dxva2api.h
+++
On 06/10/13 11:48, Rafaël Carré wrote:
> diff --git a/mingw-w64-headers/include/dxva2api.idl
> b/mingw-w64-headers/include/dxva2api.idl
> index c0fd3b0..5d8646f 100644
> --- a/mingw-w64-headers/include/dxva2api.idl
> +++ b/mingw-w64-headers/include/dxva2api.idl
> @@ -12,6 +12,8 @@ typedef DWORD ID
On 6/10/2013 14:07, Jim Michaels wrote:
> is there a way to detect compilation with --ansi or --posix?
>
No, this should not be needed, the correct inttypes macro will be used
corresponding to the printf set. C99 printf with __mingw_printf etc...
I have not investigated this further.
signa
Corinna,
I upload 3rdparty sources that I use in MSYS2 to
https://sourceforge.net/projects/msys2/files/Sources/
Regards, Alexey.
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT
On 6/10/2013 18:06, JonY wrote:
> On 6/10/2013 14:07, Jim Michaels wrote:
>> is there a way to detect compilation with --ansi or --posix?
>>
>
> No, this should not be needed, the correct inttypes macro will be used
> corresponding to the printf set. C99 printf with __mingw_printf etc...
>
Ther
New snapshots released.
In this version I split MSYS2 into two parts: MSYS2 (for using with mingw
compilers) and DEVELOP (msys-gcc, msys-binutils, win32api, libraries,
headers).
Links:
32 bit:
x32-msys2-alpha-20130610.tar.xz<http://sourceforge.net/projects/msys2/files/Alpha-versi
Erik van Pienbroek schreef op za 25-05-2013 om 20:46 [+0200]:
> Here's a really minimal testcase which demonstrates the problem:
>
> $ touch foo.c
> $ i686-w64-mingw32-gcc -shared foo.c -o foo.dll -Wl,--export-all-symbols
> $ i686-w64-mingw32-objdump -p foo.dll
>
> [Ordinal/Name Pointer] Table
>
2013/6/10 Erik van Pienbroek :
> Erik van Pienbroek schreef op za 25-05-2013 om 20:46 [+0200]:
>> Here's a really minimal testcase which demonstrates the problem:
>>
>> $ touch foo.c
>> $ i686-w64-mingw32-gcc -shared foo.c -o foo.dll -Wl,--export-all-symbols
>> $ i686-w64-mingw32-objdump -p foo.dll
