For a human-readable string<\/strong>, use For machine-friendly numbers<\/strong>, use the Gestalt<\/a> function, with one of the selectors: Here’s a simpler example of using Gestalt: For scripts and command-line work<\/strong>, there is the sw_vers<\/a> command. Check the value of:<\/p>\n Finally, if you must, you can parse To enforce a minimum OS requirement for your application, you can set the LSMinimumSystemVersion<\/a> key in the Info.plist<\/a> file. Big Nerd Ranch has a more robust, user-friendly, but complicated solution<\/a> for older legacy systems.<\/p>\n","protected":false},"excerpt":{"rendered":" Cocoa For a human-readable string, use [[NSProcessInfo processInfo] operatingSystemVersionString]. It looks like “Version 10.5 (Build 9A581)”, but that format might change in the future. NSProcessInfo.h explicitly warns against using it for parsing. It will always be human-readable though. For machine-friendly numbers, use the Gestalt function, with one of the selectors: gestaltSystemVersionMajor (in 10.4.17 this would […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,5,4,13,9],"tags":[366,279,544],"class_list":["post-35","post","type-post","status-publish","format-standard","hentry","category-macosx","category-objective-c","category-programming","category-sample-code","category-unix","tag-java","tag-mac-os-x","tag-scripting"],"_links":{"self":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/35","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/comments?post=35"}],"version-history":[{"count":2,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/35\/revisions"}],"predecessor-version":[{"id":522,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/35\/revisions\/522"}],"wp:attachment":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/media?parent=35"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/categories?post=35"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/tags?post=35"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}[[NSProcessInfo processInfo] operatingSystemVersionString]<\/code>. It looks like “Version 10.5 (Build 9A581)”, but that format might change in the future. NSProcessInfo.h explicitly warns against using it for parsing. It will always be human<\/em>-readable though.<\/p>\n
\ngestaltSystemVersionMajor<\/code> (in 10.4.17 this would be the decimal value 10)
\ngestaltSystemVersionMinor<\/code> (in 10.4.17 this would be the decimal value 4)
\ngestaltSystemVersionBugFix<\/code> (in 10.4.17 this would be the decimal value 17)
\nDo not<\/em> use gestaltSystemVersion<\/code><\/a> unless your code needs to run on OS X 10.2 or earlier.<\/strong> It’s a legacy function that can’t report minor\/bugfix versions > 9; meaning it can’t distinguish between 10.4.9 and 10.4.11. The CocoaDev wiki has example code that works in 10.0<\/a> if you need to go that route.<\/p>\n
\n- (BOOL) usingLeopard {
\n long minorVersion, majorVersion;
\n Gestalt(gestaltSystemVersionMajor, &majorVersion);
\n Gestalt(gestaltSystemVersionMinor, &minorVersion);
\n return majorVersion == 10 && minorVersion == 5;
\n}<\/code><\/p>\nScripts<\/h3>\n
\n$ sw_vers
\nProductName:\tMac OS X
\nProductVersion:\t10.5
\nBuildVersion:\t9A581
\n$ sw_vers -productName
\nMac OS X
\n$ sw_vers -productVersion
\n10.5
\n$ sw_vers -buildVersion
\n9A581
\n<\/code><\/p>\nJava<\/h3>\n
System.getProperty(\"os.name\");\nSystem.getProperty(\"os.version\");\n<\/pre>\n
Fallback<\/h3>\n
\/System\/Library\/CoreServices\/SystemVersion.plist<\/code> — but I don’t like the idea of doing that. There’s a chance that the file could have been corrupted or maliciously altered. It seems safer, and less complicated, to directly ask the operating system it’s version.<\/p>\nMinimum OS Requirements<\/h3>\n