Mac: Unversioned framework structure may cause code signing issues with Xcode 6+

[GoogleCodeExporter]

When you create a framework with Xcode it has this structure:

DoNothing.framework
DoNothing.framework/DoNothing
DoNothing.framework/Headers
DoNothing.framework/Modules
DoNothing.framework/Resources
DoNothing.framework/Versions
DoNothing.framework/Versions/A
DoNothing.framework/Versions/A/DoNothing
DoNothing.framework/Versions/A/Headers
DoNothing.framework/Versions/A/Headers/DoNothing.h
DoNothing.framework/Versions/A/Modules
DoNothing.framework/Versions/A/Modules/module.modulemap
DoNothing.framework/Versions/A/Resources
DoNothing.framework/Versions/A/Resources/Info.plist
DoNothing.framework/Versions/Current

which apparently is conventional, but Chromium Embedded Framework.framework 
doesn't follow it:

Chromium Embedded Framework.framework
Chromium Embedded Framework.framework/Chromium Embedded Framework
Chromium Embedded Framework.framework/Libraries
Chromium Embedded Framework.framework/Libraries/ffmpegsumo.so
Chromium Embedded Framework.framework/Libraries/PDF.plugin
Chromium Embedded Framework.framework/Libraries/PDF.plugin/Contents
Chromium Embedded Framework.framework/Libraries/PDF.plugin/Contents/Info.plist
Chromium Embedded Framework.framework/Libraries/PDF.plugin/Contents/MacOS
Chromium Embedded Framework.framework/Libraries/PDF.plugin/Contents/MacOS/PDF
Chromium Embedded Framework.framework/Resources
Chromium Embedded Framework.framework/Resources/...

This might be ok, but it may be causing issues here and there, like this one: 
http://stackoverflow.com/questions/28751092/after-i-added-chromium-embedded-fram
ework-code-signing-is-failing

Original issue reported on code.google.com by pup...@pupeno.com on 26 Feb 2015 at 10:20

[GoogleCodeExporter]

CEF currently uses the same unversioned framework structure as Google Chrome. 
Code signing of unversioned frameworks may be problematic in Xcode 6+ but 
should work fine in older versions. See 
http://www.magpcss.org/ceforum/viewtopic.php?f=6&t=12113 for related discussion.

Original comment by magreenb...@gmail.com on 26 Feb 2015 at 10:42

• Changed title: Mac: Unversioned framework structure may cause code signing issues with Xcode 6+

[GoogleCodeExporter]

Also related: http://www.magpcss.org/ceforum/viewtopic.php?f=6&t=11651

Original comment by magreenb...@gmail.com on 26 Feb 2015 at 10:43

[GoogleCodeExporter]

CEF is transitioning from Google Code to Bitbucket project hosting. If you 
would like to continue receiving notifications on this issue please add 
yourself as a Watcher at the new location: 
https://bitbucket.org/chromiumembedded/cef/issue/1553

Original comment by magreenb...@gmail.com on 14 Mar 2015 at 3:38