C++ compile time macros to detect windows os

Question

Are there any C++ compile time macros which exists to detect which Windows OS the code is being compiled on. I basically want to support certain functions only on Win7. So I am interested in doing something like this

#if <os_macro> = WIN7
  // This function would do something valid only on Win7 builds.
  bool myfunction {
        // do something here
  }
#else
  // This function would typically return false, since its not supported on OS below win7
  bool myfunction {
       return false;
  }
#endif

Is there any other better way to do this?

How is which OS it's compiled on helpful? Doesn't it need to know which OS it's running on? — Mark B
– Mark B, Commented Apr 11, 2012 at 18:49
In Visual Studio you can use #ifdef WIN32 or #ifdef _WINDOWS for cross-platform. If you just want windows version you normally define WINVER yourself. For Windows 7 #define WINVER 0x0601 — AJG85
– AJG85, Commented Apr 11, 2012 at 18:56

Adam Rosenfield · Accepted Answer · 2012-04-11 18:54:31Z

11

The OS that it's getting compiled on is not all that important; what matters more is the OS that the code is running on, which you obviously cannot detect at compile time. But if you want your code to run on older versions of Windows, you can set WINVER and _WIN32_WINNT to certain values, which will cause newer functions not to be available etc. (just search the Windows header files for where those macros get tested to get an idea).

To test for functionality at runtime, use GetProcAddress (and possibly also LoadLibrary, if it's in a newer DLL) to test if the function is available. If it is, call it, if not, don't.

See also the predefined macros used by the Visual Studio compiler if you want to detect the compiler version etc.

answered Apr 11, 2012 at 18:54

Adam Rosenfield

402k102 gold badges524 silver badges600 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Rajiv Over a year ago

Basically I should be able to say, this is a Win7 build which has certain capability, and this is a WinXP build which does not. Here I would be defining what the capability should be.

Adam Rosenfield Over a year ago

Why do you want separate builds? Why not have one build that behaves differently depending on what OS it's running on?

Martin Beckett · Accepted Answer · 2012-04-11 18:52:38Z

1

There are a set of standard windows header macros to tell you the exact version of the OS

answered Apr 11, 2012 at 18:52

Martin Beckett

96.3k28 gold badges196 silver badges268 bronze badges

1 Comment

Rajiv Over a year ago

How do I those macros to do the comparisons? I tried with Winver like this #if WINVER >= _WIN32_WINNT_WIN7, but it didn't work very well.

blueseal · Accepted Answer · 2019-11-14 03:24:42Z

1

There are certain things that do require knowing which OS version at compile time.

For example import "winhttp.dll" will compile under Windows 7, but cause compile time error (C1083) under Windows 10.

But if you switch to import "winhttpcom.dll". It would compile under Windows 10 but fail under Windows 7.

So an OS macro is needed here to import appropriate dll.

edited Nov 14, 2019 at 3:24

blueseal

2,9287 gold badges29 silver badges46 bronze badges

answered Nov 13, 2019 at 20:57

Ninh Tran

111 bronze badge

1 Comment

BigChief Over a year ago

how to fix this?

Jerry Coffin · Accepted Answer · 2012-04-11 18:51:32Z

0

At least with MS VC++, WIN32, _WIN32, and _WIN32_WINNT, for starters. Unless you need to control it at compile time, you might consider using something like GetVersionEx to detect at run-time, so the same build runs on older versions, but takes advantage of new features when they're available.

answered Apr 11, 2012 at 18:51

Jerry Coffin

494k83 gold badges656 silver badges1.2k bronze badges

Comments

SeeTheC · Accepted Answer · 2023-01-09 08:46:02Z

0

My response is 10 yrs late but posting the answer for upcoming yrs.

For detecting the version c/c++ compiler version can be used. Suitable macro is mentioned below:

_MSC_VER 

_MSC_FULL_VER

Reference: MS macros

answered Jan 9, 2023 at 8:46

SeeTheC

1,64013 silver badges14 bronze badges

1 Comment

Sz. Sep 3 at 13:41

No, you can compile with just about anything else than MSVC on Windows, for Windows. (Note: the OP said "I basically want to support certain functions only on Win7".)

ingconti · Accepted Answer · 2017-08-31 09:56:30Z

-1

My two cents for people that want to compile / include differently between CONSOLE and WIN32 App under visual Studio (2017) in my case.

You you use wizard to create a Console App, You will have:

WIN32;_DEBUG;_CONSOLE;%(PreprocessorDefinitions)

under:

If You use wizard for win32 GUI App:

WIN32;_DEBUG;_WINDOWS;%(PreprocessorDefinitions) so NO _CONSOLE.

so You can write:

#ifdef _CONSOLE
// for Console
#else
// for GUI


#endif // _CONSOLE



int main()
{
#ifdef _CONSOLE
    // for Console
#else
    // for GUI


#endif // _CONSOLE


    return 0;
}

answered Aug 31, 2017 at 9:56

ingconti

11.8k3 gold badges68 silver badges52 bronze badges

Collectives™ on Stack Overflow

C++ compile time macros to detect windows os

6 Answers 6

2 Comments

1 Comment

1 Comment

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

2 Comments

1 Comment

1 Comment

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related