We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 5031 - Signing SDL2_image.framework is ambigious
Summary: Signing SDL2_image.framework is ambigious
Status: ASSIGNED
Alias: None
Product: SDL_image
Classification: Unclassified
Component: misc (show other bugs)
Version: 2.0.4
Hardware: x86_64 macOS 10.15
: P2 major
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-15 10:23 UTC by lennard.berger
Modified: 2020-03-20 19:42 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description lennard.berger 2020-03-15 10:23:53 UTC 
Dear SDL2 maintainers.
We are currently trying to embed SDL2_image into a consumer product using the SDL2_image.framework file on OSX.

With the introduction of the new signing policy we need to force sign framework files as well (SDL2, SDL2_mixer). With the other components this is not an issue.

When I try to do the following:

codesign -s "Developer ID Application: blab" --timestamp --options runtime --deep --strict -f SDL2_image.framework

Codesign responds with:

SDL2_image.framework: replacing existing signature
SDL2_image.framework: bundle format is ambiguous (could be app or framework)

I copied the executable binary distribution from the website. This works fine for SDL2.framework and SDL2_mixer.framework.

Looking at the contents of SDL2_image.framework/Resources/Info.plist indicates that the CFPBundleSupportedPlatforms key is set (which appeared to be a bug in earlier versions).

Any help on resolving the matter is greatly appreciated.
Comment 1 lennard.berger 2020-03-20 19:08:34 UTC 
I can verify that this is because the following Frameworks:

- FLAC.framework
- Opus.framework
- OpusFile.framework
- modplug.framework
- mpg123.framework

Do not have 

	<key>CFBundleSupportedPlatforms</key>
	<array>
		<string>MacOSX</string>
	</array>

set in the Info.plist files.
Adding these keys fixes the problem. How do you suggest we proceed? Should tickets at the upstream packages be created?
Comment 2 Sam Lantinga 2020-03-20 19:42:49 UTC 
I'll take care of it for the next release, thanks!