possible alternate locations for ffmpegsumo.so in Mac CEF?

[fernandomorgan]

Still in the xcode6 saga, code signing in Yosemite with Xcode6 or Xcode6.1 fails with the error message of:

"unsealed contents present in the root directory of an embedded framework"

this is because CEF's framework requires Libraries at the root level - is it was possible to load it from a path relative to the actual framework binary?

[fernandomorgan]

update: It seems that a symbolic might work

ln -s "${BINARY_NAME}/Contents/Frameworks/Chromium Embedded Framework.framework/Versions/Current/Libraries" "${BINARY_NAME}/Contents/Frameworks/Chromium Embedded Framework.framework/Libraries"

and code signing it as part of the xcode6 build (actually, the command line, xcodebuild)

[magreenblatt]

See the call to InitializeMediaLibrary in libcef/renderer/content_renderer_client.cc. DIR_MEDIA_LIBS is set in content/common/content_paths.cc.

[magreenblatt]

Note that Chromium managed to get code signing working without a versioned framework directory. The relevant commit is here. Unfortunately the associated bug is view restricted and I'm not familiar enough with the Chrome installer setup to translate this change into something useful for other people.

[fernandomorgan]

thanks for both posts!

looking into Google's workaround for Gatekeeper 2, seems to be a better solution then what I am doing.