Re: [Mingw-w64-public] [Mingw-users] Thoughts on how to build a linux / visual studio project (QuickFIX) with mingw

Date: Thu, 3 Jan 2013 22:47:58 -0500 From: K. Frank kfrank2...@gmail.com I see three ways to proceed: 1) Start with the actual source (i.e., .cpp files, etc.) and put together my own mingw32-make-compatible makefile. I think this should be relatively straightforward, but tedious, and

Re: [Mingw-w64-public] Problems with using printf format specs with GCC 7

> From: > Date: Tue, 12 Sep 2017 10:05:12 +1000 > > Not sure what to make of the format warnings (I'll leave that to others), > but I think the post that you cited does reveal an instance of Emacs doing > something wrong wrt the redefining of _WIN32_WINNT. > This

Re: [Mingw-w64-public] Problems with using printf format specs with GCC 7

> Date: Mon, 11 Sep 2017 23:46:00 + > From: JonY via Mingw-w64-public > Cc: JonY > > > . GCC doesn't recognize the PRIdMAX format spec, defined in > > MinGW64 inntypes.h header as "lld"; > > . GCC doesn't

Re: [Mingw-w64-public] gcc parameter -mcrtdll= for choosing Windows C RunTime DLL library

> Date: Sun, 20 Nov 2022 13:53:48 +0100 > From: Pali Rohár via Gcc > > Hello! I would like to propose a new parameter for gcc: -mcrtdll= to > allow specifying against which Windows C Runtime library should be > binary linked. On Windows there are more crt libraries and currently gcc > links to

Re: [Mingw-w64-public] gcc parameter -mcrtdll= for choosing Windows C RunTime DLL library

> Date: Sun, 20 Nov 2022 16:04:11 +0100 > From: Pali Rohár > Cc: g...@gcc.gnu.org, mingw-w64-public@lists.sourceforge.net > > On Sunday 20 November 2022 16:45:55 Eli Zaretskii wrote: > > > Date: Sun, 20 Nov 2022 13:53:48 +0100 > > > From: Pali Rohár via Gcc >

Re: [Mingw-w64-public] gcc parameter -mcrtdll= for choosing Windows C RunTime DLL library

> Date: Sun, 20 Nov 2022 16:44:08 +0100 > From: Pali Rohár > Cc: g...@gcc.gnu.org, mingw-w64-public@lists.sourceforge.net > > > Installing a redistributable is a nuisance, and dependence on non-system > > libraries might make the program non-free. > > On new windows versions they may be