-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TIKA-4309] Mach-O Universal in tika-mimetypes.xml #1963
[TIKA-4309] Mach-O Universal in tika-mimetypes.xml #1963
Conversation
2f90c82
to
00db3a6
Compare
@Gagravarr if you have any time to review this. If there's a way to simplify the various mach-o types, that'd be great. Also, any input on the choices for mime type names. For 3.x, we'll still have some time to modify this. |
00db3a6
to
5845556
Compare
Figured it out, |
5845556
to
44d9824
Compare
Updated to make it a non-breaking change |
4d75dcc
to
b934e75
Compare
Aren't the magic bits at 4096 important for jnilib? Or what is the difference between what we were detecting as
|
b934e75
to
eebdd8a
Compare
Yes and no. There's no guarantee they are at 4096 offset, that's empiric - at least based on what I know as of now. The offset should be read from the file itself - that's why I've asked about dynamic offset. An top of that, we should check that it's a library, not that it's a Mach-O, so technically those checks aren't ideal either. So far we're mimicking the
|
With that said, there's no explicit difference (known to me) between a regular universal Mach-O shared library and a JNI one, except for that extension. |
K, that's what I was trying to figure out -- the diff between what we were calling a jnilib (https://issues.apache.org/jira/browse/TIKA-1169 for the original work on |
A follow-up to #1947 & #1961 & #1962: Mach-O universal + optimized Mach-O
cc @tballison