Disable nib-stripping in Camino/prefPanes and Sparkle. There's no reason for us not to be doing that per bug 514495 comment 22 anyway. Since Sparkle still hasn't fixed their nib, turning stripping off in-tree removes one small level of hack needed for building on 10.6.
Created attachment 519501 [details] [diff] [review] Disables nib-stripping for Camino, prefPanes, and Sparkle This should do what we want to do. 1) It should get the stripping-fails-on-SUStatus.nib-with-Xcode-3.something-on-10.6 fix into the tree, complete with README update. 2) It should ensure that a theoretical Camino release built on 10.6 would produce unstripped nibs for Camino, prefPanes, and Sparkle, so that l10n could take our release build and run l10n tools on the nibs to localize (Breakpad.nib is localized entirely from strings, with layout adjustment done in code, so no need to change Breakpad). This is more future-proofing than anything else, but it makes sense to do it while we're thinking about it. To test the whole fix, someone on 10.6 would need to 1) build all the way through? (at the very least ensure Sparkle is entirely rebuilt) and 2) test that each prefPane's nib and an assortment of nibs in Camino.app/Contents/Resources/Englihs.lproj/ and Camino.app/Contents/Frameworks/Sparkle.framework/Versions/A/Resources/en.lproj will open in Interface Builder following the build. philippe, can you take this for a spin?
Comment on attachment 519501 [details] [diff] [review] Disables nib-stripping for Camino, prefPanes, and Sparkle * Patch builds without problems (both 10.4u and 10.5sdk, in both cases all the way through - make -f client.mk clean, etc ) * I successfully opened all Preference Pane nibs, the Sparkle nibs and a random number of other nibs in Camino.app/Contents/Resources/English.lproj/ for both builds * both builds are fully functional, preference panes open correctly, etc.
7 years ago
Comment on attachment 519501 [details] [diff] [review] Disables nib-stripping for Camino, prefPanes, and Sparkle sr=smorgan Long term we want to strip Sparkle though don't we, since localizations come from upstream anyway?
(In reply to comment #4) > Comment on attachment 519501 [details] [diff] [review] > Disables nib-stripping for Camino, prefPanes, and Sparkle > > sr=smorgan > > Long term we want to strip Sparkle though don't we, since localizations come > from upstream anyway? Many of the Sparkle localizations go upstream from Camino's localizers, actually. But our third-party code localization story is messy, given how Cocoa l10n tools work and the fact we strip l10ns from our build (Sparkle) or don't have them in the tree at all (Breakpad). We'll have to sort out these issues along with the ones in http://wiki.caminobrowser.org/User:Sardisson/Towards_a_single_Camino_binary when we get there.
http://hg.mozilla.org/camino/rev/b315902eb2c4 Everyone remember to remove the Sparkle patch from bug 514495 before updating your tree(s).