[Development] Important OSX 10.9.5 & 10.10 codesign changes

Jake Petroules jake.petroules at petroules.com
Fri Sep 19 17:34:55 CEST 2014


On 2014-09-19, at 11:27 AM, Adam Strzelecki <ono at java.pl> wrote:

>> codesigning complaining on this _debug reference
>> 	<key>CFBundleExecutable</key>
>> 	<string>QtPrintSupport_debug</string>
> 
> Shouldn't be debug another version within multiversioned bundle? E.g.:
> 
> 	QtCore -> Versions/Current/QtCore
> 	Resources -> Versions/Current/Resources
> 	Versions/
> 		Current -> 5
> 		5/
> 			QtCore
> 			Resources/
> 				Info.plist
> 		5-debug/
> 			QtCore
> 			Resources/
> 				Info.plist
> 
> This would solve the solving issue.
> 
> --Adam
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

No. _debug should simply never appear anywhere in the Info.plist. The bundle should be structured like so:

QtCore.framework/
	QtCore -> Versions/Current/QtCore
	QtCore_debug -> Versions/Current/QtCore_debug
	Resources -> Versions/Current/Resources
	Versions/
		Current -> 5
		5/
			QtCore
			QtCore_debug
			_CodeSignature/
				CodeResources
			Resources/
				Info.plist
				...

And the Info.plist should *always* set CFBundleExecutable to QtCore. To use the debug version you set the DYLD_IMAGE_SUFFIX environment variable to _debug prior to execution.

As far as I'm aware, we already do this correctly (aside from Info.plist being in the wrong place), and the only reason _debug is showing up in an Info.plist somewhere is probably due to some simple typo or omission.
-- 
Jake Petroules - jake.petroules at petroules.com
Chief Technology Officer - Petroules Corporation


More information about the Development mailing list