Now take this workflow from a single Mac and expand it! To recap, mdfind is told to locate any file that is an application that can launch as 32-bit and cannot launch as 64-bit. Last, the final statement kMDItemKind = 'Application' looks for any applications. Next is another & to look for the first, second, and final statements. Since some applications list both, you want to find applications that support 32-bit only. We look for both applications that support 32-bit and do not support 64-bit. This is looking for any app that DOES NOT use x86_64 (64-bit) as the executable architecture. The second statement is kMDItemExecutableArchitectures != 'x86_64'. This looks for any file that has an executable architecture that uses i386 (32-bit).įollowing that we have & which simply looks at the first and the second statement combined. Next is "kMDItemExecutableArchitectures = 'i386'. The command we’ll be using is this: /usr/bin/mdfind "kMDItemExecutableArchitectures = 'i386' & kMDItemExecutableArchitectures != 'x86_64' & kMDItemKind = 'Application'"īreaking this command in to parts you get /usr/bin/mdfind that calls the absolute path for the mdfind binary. Additionally, you can leverage mdfind to locate files matching a given query.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |