There’s more executable code on your Mac than that in apps and bundles alone. The great majority of that which is outside bundles is in executable Mach-O files – things like command tools and dylibs (dynamic libraries). And those Mach-O files can be 32-bit, or 64-bit.
When macOS 10.14 ships, Apple has warned that it will not run 32-bit code without “compromise”, so now is the time to start updating and replacing old 32-bit code, including command tools, dylibs, plugins, extensions, and of course apps themselves.
My free tool 32-bitCheck 1.1 is unique in scanning thoroughly for and reporting apps and bundles which are still 32-bit, but doesn’t examine bare Mach-O files such as command tools and dylibs. So I have improved it further in version 1.2 to give you the option of checking all bare Mach-O files too.
Tick the checkbox to Check Mach-O and run a scan on a folder containing plenty of command tools, etc., like /usr/local, and it informs you which of them are still 32-bit.
It tests for these in the same way that the command tool
file does, by examining their ‘magic number’, the first four bytes of the file. If that is
0xfeedface (I kid you not!) in hexadecimal, then that Mach-O binary is 32-bit and not 64-bit. I have checked results returned by 32-bitCheck against those from
I have also improved the information provided in the text report, to make it clearer which types of code were included in the scan, and updated the Help book again.
I have looked again at the issue of memory usage: this is almost entirely the result of performing a deep traversal of the folder being scanned. Interestingly, if you repeat a scan on the same folder, perhaps with different option settings (for bundles and Mach-O files), second and subsequent scans seem to be rather quicker, suggesting that the deep traversal is being cached after a scan.
Version 1.2 of 32-bitCheck is available from here: 32bitCheck12a
and in Downloads above.
This completes the features – apart from folder drag and drop support – which I intended this tool to have. If you want any additional features or changes, please let me know here.