blocks|key|1512233|text|file可能会告诉你。otool当然应该能够做到。但我会先试试file，例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1512234|logan:/Users/logan%25+file+d2
d2:+Mach-O+executable+ppc|code-block|syntax|javascript|1512235|存档示例：|1512236|logan:/Users/logan%25+file+/usr/lib/libMallocDebug.a
/usr/lib/libMallocDebug.a:+Mach-O+universal+binary+with+2+architectures
/usr/lib/libMallocDebug.a+(for+architecture+i386):++++++current+ar+archive+random+library
/usr/lib/libMallocDebug.a+(for+architecture+ppc):+++++++current+ar+archive|1512237|entityMap^0|0|4|B|5|V|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

<code>file</code> will probably tell you. <code>otool</code> certainly should be able to. But I'd try <code>file</code> first,
e.g.

<pre><code>logan:/Users/logan% file d2
d2: Mach-O executable ppc
</code></pre>

Example with archive:

<pre><code>logan:/Users/logan% file /usr/lib/libMallocDebug.a
/usr/lib/libMallocDebug.a: Mach-O universal binary with 2 architectures
/usr/lib/libMallocDebug.a (for architecture i386): current ar archive random library
/usr/lib/libMallocDebug.a (for architecture ppc): current ar archive
</code></pre>

blocks|key|1512311|text|另一种选择是lipo；它的输出比otool的输出简短且更具可读性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1512312|举个例子：|1512313|%25+lipo+-info+/usr/lib/libiodbc.a+
Architectures+in+the+fat+file:+/usr/lib/libiodbc.a+are:+x86_64+i386+ppc
%25+lipo+-info+libnonfatarchive.a
input+file+libnonfatarchive.a+is+not+a+fat+file
Non-fat+file:+libnonfatarchive.a+is+architecture:+i386
%25|code-block|syntax|javascript|1512314|entityMap^0|6|4|G|5|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Another option is <code>lipo</code>; its output is brief and more readable than <code>otool</code>'s.

An example:

<pre><code>% lipo -info /usr/lib/libiodbc.a 
Architectures in the fat file: /usr/lib/libiodbc.a are: x86_64 i386 ppc
% lipo -info libnonfatarchive.a
input file libnonfatarchive.a is not a fat file
Non-fat file: libnonfatarchive.a is architecture: i386
%
</code></pre>

blocks|key|1297661|text|此bash脚本将帮助您以编程方式将架构列表放入一个变量中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297662|list_archs.sh：|1297663|#!+/bin/bash
lipo+-info+$1+%7C+sed+-En+-e+'s/%5E(Non-%7CArchitectures+in+the+)fat+file:+.%2B(+is+architecture%7C+are):+(.*)$/\3/p'|code-block|syntax|javascript|1297664|使用示例：|1297665|./list_archs.sh+/usr/lib/libc.dylib
x86_64+i386|1297666|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This bash script will help you programmatically get a list of architectures into a variable.

list_archs.sh:

<pre><code>#! /bin/bash
lipo -info $1 | sed -En -e 's/^(Non-|Architectures in the )fat file: .+( is architecture| are): (.*)$/\3/p'
</code></pre>

Usage example:

<pre><code>./list_archs.sh /usr/lib/libc.dylib
x86_64 i386
</code></pre>

blocks|key|1512405|text|如果有人来这里寻找如何辨别一个库(或其中的目标文件)是否是为Mac+Catalyst设计的答案，可以使用otool+-l转储load命令。找到任何对象的LC_BUILD_VERSION部分。Mac+Catalyst是由platform+6而不是platform+1标识的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1512406|entityMap^0|1G|8|31|A|3E|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

If anyone comes here looking for answers about how to tell whether a library (or the object files in it) are intended for Mac Catalyst, use <code>otool -l</code> to dump the load commands. Find the LC_BUILD_VERSION section for any object. Mac Catalyst is identified by <code>platform 6</code> rather than <code>platform 1</code>.

I'm interested in verifying if a given iPhone static library has been built for ARM or Intel. 

It's more curiosity than anything. Is there some kind of Mac OS X or BSD specific tool to do this? This <a href="https://stackoverflow.com/questions/267941/determine-target-architecture-of-binary-file-in-linux-library-or-executable">post</a> gives an example in Linux.

How do I determine the target architecture of static library (.a) on Mac OS X?

Linux

我有兴趣验证给定的iPhone静态库是否是为ARM或英特尔构建的。好奇心比任何东西都要强。有没有某种Mac或BSD特定的工具可以做到这一点？这个给出了Linux中的一个例子。

问如何确定Mac上静态库(.a)的目标架构？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何确定Mac上静态库(.a)的目标架构？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何确定Mac上静态库(.a)的目标架构？
EN