Steven Shmerler wrote:
What do I put in Terminal to elicit what you are asking?
Just copy and paste it in, then hit the "enter" key:
file "/Library/Contextual Menu Items/DocumentsToGoXCM.plugin/Contents/MacOS/DocumentsToGoXCM"
The quotation marks are necessary in this example because of the space in the file name.
The "
file" command is to determine file types. For example, if you look at iTunes:
file "/Applications/iTunes.app/Contents/MacOS/iTunes"
You'll get:
/Applications/iTunes.app/Contents/MacOS/iTunes: Mach-O universal binary with 2 architectures
/Applications/iTunes.app/Contents/MacOS/iTunes (for architecture ppc): Mach-O executable ppc
/Applications/iTunes.app/Contents/MacOS/iTunes (for architecture i386): Mach-O executable i386
But if it's not a universal binary, you'll get a result with just one architecture. (I included quotation marks in the command, but they're not really necessary in this case, since there are no spaces).
You can also search for the plugin and do a "Get Info" in the Finder to see what architecture is in the file. In this case, though, search for the "DocumentsToGoXCM.plugin" part of the file name, not the part from "Contents" on, since that's in the bundle.
Applications can't load plugins across architectures. In other words, if you have an application running as native Intel code, it can't load any plugins that have only PowerPC code.
However, if the application is a universal binary, with both PowerPC and Intel code, you can force it to run the PowerPC code, and it can then load PowerPC plugins.
charlie