Re: muse for windows
Posted: Mon Feb 18, 2019 12:56 am
Also today I thought about whether we should be hard-coding #ifdef _WIN32 and _WIN64,
or whether it would be better to let cmake tell you what OS it is and define a flag like say HAVE_WIN32 or HAVE_WIN64
and all the code will refer to THAT flag instead of directly embedding those other flags in the code.
I'm a bit weary of hard-coding. It's nice if we can let cmake have total control over all the code with a HAVE_WIN32/64 flag.
We could have three flags: HAVE_WIN (for a general catch-all), and HAVE_WIN32 and HAVE_WIN64.
Not sure. Just some thoughts...
Also today I realized I am confused by something:
Why is _WIN32/64 defined at all in a Ming program? Isn't it supposed to be 'Linux'?
And if _WIN32/64 is defined then how are we supposed juggle knowing how to tell whether we can call
'Linux-y' type stuff or whether to make Windows calls instead?
Seems we have both 'Linux-y' type stuff and 'Windows-y' type stuff in one program?
Thanks.
or whether it would be better to let cmake tell you what OS it is and define a flag like say HAVE_WIN32 or HAVE_WIN64
and all the code will refer to THAT flag instead of directly embedding those other flags in the code.
I'm a bit weary of hard-coding. It's nice if we can let cmake have total control over all the code with a HAVE_WIN32/64 flag.
We could have three flags: HAVE_WIN (for a general catch-all), and HAVE_WIN32 and HAVE_WIN64.
Not sure. Just some thoughts...
Also today I realized I am confused by something:
Why is _WIN32/64 defined at all in a Ming program? Isn't it supposed to be 'Linux'?
And if _WIN32/64 is defined then how are we supposed juggle knowing how to tell whether we can call
'Linux-y' type stuff or whether to make Windows calls instead?
Seems we have both 'Linux-y' type stuff and 'Windows-y' type stuff in one program?
Thanks.