Hello list.
In a 32-bit program if mine (while printing the version info)
I have stuff like:
extern const char *os_name (const char *vendor);
#if defined(__MINGW64_VERSION_MAJOR)
#define VENDOR os_name ("MinGW-w64") /* a new-school MinGW */
#elif defined(__MINGW32__)
#define VENDOR os_n
2016-03-17 16:23 GMT+01:00 LRN :
>
> Why would you do that? What are you hoping to achieve by telling the
> difference between TDM mingw-w64-based toolchain and non-TDM
> mingw-w64-based toolchain?
>
>
There are ABI differences, but those shouldn't matter inside the code. This
difference should on
I wrote:
> In a 32-bit program if mine (while printing the version info)
> I have stuff like:
>
> extern const char *os_name (const char *vendor);
>
> #if defined(__MINGW64_VERSION_MAJOR)
>#define VENDOR os_name ("MinGW-w64") /* a new-school MinGW */
> #elif defined(__MINGW32__)
>
Ruben Van Boxem wrote:
> There is, as far as I know, no special define you can check to differentiate
> TDM's GCC from vanilla GCC. If I remember
> correctly, there's no extra defines added into the compiler in the patches
> applied in a TDM build.
Thanks for clearing that up.
--
--gv
--
On 17.03.2016 17:49, Gisle Vanem wrote:
>
> So how can I differentiate on your MinGW-w64 and TDM-gcc from
> http://tdm-gcc.tdragon.net
>
Why would you do that? What are you hoping to achieve by telling the
difference between TDM mingw-w64-based toolchain and non-TDM
mingw-w64-based toolchain?
-
