\ndefines several symbols for you automatically<\/a>\n(assuming you’re not running\nthe compiler in “strict ANSI compliance mode”).\nIf you’re willing to tie yourself to the Microsoft Visual C++ compiler,\nyou can use those symbols.\n<\/p>\n\n#ifdef _M_IX86\n \/\/ the target architecture is x86\n#else\n \/\/ the target architecture is something else\n#endif\n<\/pre>\n\nIf you don’t want to tie yourself to a particular compiler,\nyou’ll have to pass that information yourself.\nFor example, you could have your x86 makefile<\/code> pass\n-DBUILDING_FOR_x86<\/code> in the compiler flags,\nwhile having the ia64 makefile<\/code> pass\n-DBUILDING_FOR_ia64<\/code>, and so on.\nThis is the approach used by the build<\/code> utility\nthat comes with the Windows DDK:\nThe DDK’s makefile system defines a variety\nof symbols that programs (and other makefiles) can use to alter their\nbehavior depending on the compilation environment:\n<\/p>\n\n\/\/ assumes you use makefile.def\n#if defined(_X86_)\n \/\/ the target architecture is x86\n#elif defined(_IA64_)\n \/\/ the target architecture is Intel ia64\n#elif defined(_AMD64_)\n \/\/ the target architecture is AMD x86-64\n#else\n \/\/ some other architecture\n#endif\n<\/pre>\n\nAs we saw in the earlier article,\nyou can also use the _WIN64<\/code> symbol to detect that\nthe target platform is 64-bit Windows.\n<\/p>\n\nBut the point is that this is all something you control yourself.\nYou’re the one who is compiling the program.\nYou know what your target architecture is.\nNo need to ask somebody to tell you something that is already\nentirely under your own control.<\/p>\n","protected":false},"excerpt":{"rendered":"
Sometimes the questions I see make me shake my head in wonderment. How do I determine programmatically what processor architecture my program was compiled for? I want the x86 version of my program to behave differently from the ia64 version. Is there some API I can call? Note that this person isn’t asking whether the […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-29843","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
Sometimes the questions I see make me shake my head in wonderment. How do I determine programmatically what processor architecture my program was compiled for? I want the x86 version of my program to behave differently from the ia64 version. Is there some API I can call? Note that this person isn’t asking whether the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/29843","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=29843"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/29843\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=29843"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=29843"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=29843"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}