On Sun, 8 Dec 2019, Zach Bacon wrote:
Aye, iirc wines effort for directx12 is related to vulkan in the same
relative manner as dxvk if I recall correctly, so they aren't really
keeping that stuff in tree. And nightstrike, I know, hence why I asked my
question about where to start.
I don't know
Aye, iirc wines effort for directx12 is related to vulkan in the same
relative manner as dxvk if I recall correctly, so they aren't really
keeping that stuff in tree. And nightstrike, I know, hence why I asked my
question about where to start.
On Sun., Dec. 8, 2019, 2:29 p.m. Biswapriyo Nath,
wro
> Those are already present in Wine, we may just import it. See wine-import.sh.
wine-import.sh does not have any d3d12 headers or idl files.
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/li
Hi Zach,
On 08/12/2019 16:17, Zach Bacon wrote:
At this moment I'm looking at possibly including new directx headers namely 12,
and I'm curious as to the process, would one begin with working on compatible
headers first or the idl files?
Those are already present in Wine, we may just impor
On Sun, Dec 8, 2019, 12:35 PM Biswapriyo Nath wrote:
> The files in Windows SDK are too big to add (but not impossible). I am also
> eager to do it but afraid of any copyright laws which may be applied for
> big chunk of copy-pasting code.
>
You can't copy and paste copyrighted code. You have to
The files in Windows SDK are too big to add (but not impossible). I am also
eager to do it but afraid of any copyright laws which may be applied for
big chunk of copy-pasting code.
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
At this moment I'm looking at possibly including new directx headers namely 12,
and I'm curious as to the process, would one begin with working on compatible
headers first or the idl files?
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.source
On Sun, 8 Dec 2019, Liu Hao wrote:
在 2019/12/8 上午6:39, Martin Storsjö 写道:
Signed-off-by: Martin Storsjö
---
mingw-w64-crt/math/arm/nearbyint.S | 17 +
mingw-w64-crt/math/arm/nearbyintf.S | 17 +
mingw-w64-crt/math/arm/nearbyintl.S | 17 +
3 fil
在 2019/12/3 8:17, Thomas Dineen 写道:
> Gentle People:
>
> Considering that I am attempting to build a cross compiler on a
> CentOS Machine targeting Windows:
If you cross-compile you must specify `--host` otherwise you invoke the
native (CentOS => CentOS) compiler (as in your log was `gcc` which i
在 2019/12/8 18:53, Amit Choudhary 写道:
> On Sunday, December 8, 2019, Zach Bacon wrote:
>
>> So... Msys2 CRT is a wrapper around POSIX API. Bash uses said POSIX API,
>> mingw-w64 is more geared towards windows API, so to compile it with
>> mingw-w64, you'd have to do some heavy patching to bash to
On Sunday, December 8, 2019, Zach Bacon wrote:
> So... Msys2 CRT is a wrapper around POSIX API. Bash uses said POSIX API,
> mingw-w64 is more geared towards windows API, so to compile it with
> mingw-w64, you'd have to do some heavy patching to bash to support the
> windows API.
>
Please bear wi
So... Msys2 CRT is a wrapper around POSIX API. Bash uses said POSIX API,
mingw-w64 is more geared towards windows API, so to compile it with mingw-w64,
you'd have to do some heavy patching to bash to support the windows API.
On Sun, 08 Dec 2019 02:24:01 -0800 amitchoudhary2...@gmail.com
>
> I presume it is not possible to build bash using mingw-w64, because
> Windows is not a recent enough POSIX system.
>
> Instead, you must use the MSYS2 GCC to compile bash and link it against
> the MSYS2 CRT, not the mingw-w64 CRT. The triplet should look like
> `x86_64-pc-msys`.
>
I was able t
check for inclusion of fcntl.h in that file, gcc has become very verbose
in later versions so allmost no matter what you will get warnings. These
are mostly descriptive and can be ignored unless a real error occurs.
Den 08-12-2019 kl. 09:49 skrev Amit Choudhary:
> I have some doubts: I am using mi
在 2019/12/8 上午6:39, Martin Storsjö 写道:
> Signed-off-by: Martin Storsjö
> ---
> mingw-w64-crt/math/arm/nearbyint.S | 17 +
> mingw-w64-crt/math/arm/nearbyintf.S | 17 +
> mingw-w64-crt/math/arm/nearbyintl.S | 17 +
> 3 files changed, 15 insertions(+
I have some doubts: I am using mingw-w64 compiler to compile bash in
msys2 environment. It may not be possible. But I wanted to know
something else. I got a warning:
./include/filecntl.h:33:33: warning: implicit declaration of
function 'fcntl'; did you mean 'fcvt'?
[-Wimplicit-function-declara
Would probably need to do a cross build using the msys2 mingw64
compilers in /opt else you would have gained nothing since every
dependency compiled with msys2 gcc would rely on the msys2.dll.
Den 08-12-2019 kl. 07:53 skrev Liu Hao:
> 在 2019/12/7 21:44, Amit Choudhary 写道:
>> Hi,
>>
>> I have downl
在 2019/12/7 下午10:56, Biswapriyo Nath 写道:
> ...
>
>
>
Thanks, I pushed this one.
--
Best regards,
LH_Mouse
signature.asc
Description: OpenPGP digital signature
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists
18 matches
Mail list logo
