Re: [Mingw-w64-public] binary releases

> On 22-09-2020 13:39:19, sisyphus wrote: > > On Tue, Sep 22, 2020 at 9:28 PM wrote: > > > [snip] > > > > > > yes, I plan to continue releasing compiler builds but they will be > > hosted here: https://github.com/niXman/mingw-builds/releases > > > Great news !! > > Cheers, > Rob Yes, plea

Re: [Mingw-w64-public] Any plan to release new mingw-w64 version?

on will appear on: https://sourceforge.net/projects/mingw-w64/files/ That would be really great. If you guys could work towards that with an modern GCC version I would love to use that. Also I know people in the Boost community would like to see that happening. Best Regards, Maarten Verhage

[Mingw-w64-public] Issue with DDK inlines

Dear list members, I'm experimenting a bit with the native API of Windows. In "x86_64-8.1.0-release-win32-seh-rt_v6-rev0" you offer DDK include files from ReactOS. Are these also suitable to work with Windows? At this moment just including ntddk.h goes wrong. I've nothing modified in my x86_64

Re: [Mingw-w64-public] locale constructor valid strings?

>> Regarding C++ character classification functions like iscntrl, isprint I >> can >> include and use the std::locale class. As I have mingw-w64: >> "x86_64-8.1.0-release-win32-seh-rt_v6-rev0" and my OS is Windows 7, >> 64bit. >> Where can I find all the possible valid code page names for the >

[Mingw-w64-public] locale constructor valid strings?

unctions that also can do the character classification checks? Thank you very much for your attention and time! Best regards, Maarten Verhage ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] Forcing MinGW-w64's linker to find Windows specific libraries

Sorry attachment is here.FLAGS = -std=c++14 -pedantic -Wextra -Wformat -Wlogical-op INCPATHUTILITY = -I"$(CPP_MYDESIGN_PATH)\utility\include" LIBPATHUTILITY = -L"$(CPP_MYDESIGN_PATH)\utility\lib" INCPATHBOOST = -I"$(BOOST)" LIBPATHBOOST = -L"$(BOOST_LIB)" LIBSWIN = -l:libkernel32.a -l:libuser32.a -

Re: [Mingw-w64-public] Forcing MinGW-w64's linker to find Windows specific libraries

Hi Tom, I'm not an expert on this topic but maybe I can give you a few suggestions. As shown the mailing list discussion from the link below. I believe Mingw-w64 designed to work with gcc and you cannot use the libraries with Visual Studio. https://sourceforge.net/p/mingw-w64/mailman/message/3

[Mingw-w64-public] Mingw64 win32-seh build 32bit libraries

on to see which sources are compiled to which library. Thank you very much for your attention and time! Best regards, Maarten Verhage ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/

Re: [Mingw-w64-public] GCC issue with constexpr?

Hi, > Your code is not valid. Clang++ rejects your snippet, too. > > The array-to-pointer conversion from an array of `const char` is not > allowed in a constant expression unless such an array is declared with > `constexpr` [1]. Use `constexpr` in place of `const` will solve your > problem. >

[Mingw-w64-public] GCC issue with constexpr?

nction variant for the second template argument it should also work further down, I believe. Best regards, Maarten Verhage ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] Linking fails for GetSaveFileName when cross compiling with MinGW

b. Are you willing to try this? Kind regards, Maarten Verhage - Original Message - From: "Sailor Bob via Mingw-w64-public" To: Cc: "Sailor Bob" Sent: Tuesday, January 08, 2019 18:29 Subject: [Mingw-w64-public] Linking fails for GetSaveFileName when cross compiling

Re: [Mingw-w64-public] LLVM libc++ build with gcc

Hi Liu and others, > > If you insist on use of `-nodefaultlibs` or `-nostdlib` you may want to > see how the linker is invoked by g++ (with `-v` during linking) and copy > those options, then remove some until none can be removed any further. > Good progress now with this suggestion! The order o

Re: [Mingw-w64-public] LLVM libc++ build with gcc

u think the gcc supplied startfiles are interoperable with LLVM libc++? Can you think of a way to get my example to link correctly? Best regards, Maarten Verhage ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] win32 threads

Thanks Liu, Very clear. Much appreciated! - Original Message - From: "Liu Hao" To: "Maarten Verhage" ; Sent: Tuesday, December 18, 2018 03:23 Subject: Re: [Mingw-w64-public] win32 threads >在 2018/12/18 4:17, Maarten Verhage 写道: >> It's clear to me

Re: [Mingw-w64-public] win32 threads

Hi Liu, - Original Message - From: "Liu Hao" To: ; "Maarten Verhage" Sent: Monday, December 17, 2018 03:43 Subject: Re: [Mingw-w64-public] win32 threads >在 2018/12/17 2:58, Maarten Verhage 写道: >> Hi all or dear people, >> >> Regarding the

[Mingw-w64-public] win32 threads

hreads? You know in a way that the resulting executable actually calls the Windows API CreateThread function among others.. 3) If this is not possible why do the headers like thread and mutex exist in the mingw win32 thread builds? Best regards, Maarten Verhage #define _GLIBC

Re: [Mingw-w64-public] set default sysroot

Hi Rob, - Original Message - From: "sisyphus" To: Sent: Sunday, December 16, 2018 04:38 Subject: Re: [Mingw-w64-public] set default sysroot > Hi, > > I don't know if you can reset the default without recompiling gcc - I > suspect you can't, but others might know better. > > Closest I

[Mingw-w64-public] set default sysroot

s not the path I installed mingw and gcc into. How would I be able to set the *default* sysroot path on my system? I prefer not to msys(2) tools if possible. Thanks, best regards, Maarten Verhage ___ Mingw-w64-public mailing list Mingw-w64-p