I'm imagining something like this in a header file: pid_t __mingw_posix_getpid(); #ifdef __USE_MINGW_POSIX_PID #define getpid __mingw_posix_getpid #endif
So the mingw-w64 binary (the crt?) would always provide __mingw_posix_getpid, but the user program can either use it or not depending on how it is built. Wasn't __USE_MINGW_ANSI_STDIO implemented without making two ABIs? --David On Tue, Mar 1, 2016 at 11:31 AM, Adrien Nader <[email protected]> wrote: > On Tue, Mar 01, 2016, David Grayson wrote: >> Could we add a preprocessor configuration option like >> __USE_MINGW_POSIX_PID which makes getpid() actually return a pid_t >> (signed 64-bit integer)? (It can be wrapped in a function named >> __mingw_getpid or something.) So POSIXY projects could opt in to the >> new behavior in their build configuration, and Windowsy projects would >> keep working as is? It would be like __USE_MINGW_ANSI_STDIO. > > Wouldn't that mean two ABIs? Sounds difficult to balance. > > -- > Adrien Nader ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
