[Adium-devl] Changes to AIUtilities-Framework

Evan Schoenberg evan at adiumx.com
Wed Apr 18 13:10:58 UTC 2007


> Christopher Harms wrote:
>
>> Hi Chris,
>> I changed something and then it worked. I'm not sure, but I guess it
>> was changing the role (see Targets -> AIUtilities) from "project" to
>> "public".
'project' files can only be used within the project.  they aren't  
copied into the built framework.  This is the correct and necessary  
solution.

On Apr 18, 2007, at 8:19 AM, Chris Forsythe wrote:
> I've found that with framework changes, and more notoriously,  
> info.plist
> changes, you tend to need a clean build with xcode.
Clean builds are overkill.  Delete your built Adium.app and the built  
framework, then rebuild.  It's a lot cheaper :)

All my scripts for moving frameworks around do this automatically.  
For example, psm updates to a build PSMTabBarControl:
----
cd ~/Coding_Other/PSMTabBarControl/build/Release/
tar cvf PSMTabBarControl.framework.tar PSMTabBarControl.framework/
mv *.tar /Users/evands/adium/Frameworks
cd /Users/evands/adium/Frameworks
tar xvf PSMTabBarControl.framework.tar
rm -rf /Users/evands/adium/build/*/Adium.app/Contents/Frameworks/ 
PSMTabBarControl.framework
---

None of this is necessary if the framework in question is actually  
built by one of our xcode project files, though -- that means that if  
*you* build the AIUtilities change, xcode knows about it.

The real problem is that the binary gets its modification date  
updated but the framework's root doesn't.  So if I commit a new  
Libpurple.framework, it's Libpurple.framework/Contents/MacOS/ 
Libpurple which has an updated modification date; Libpurple.framework  
itself looks the same.

-Evan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070418/b2ecff4c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070418/b2ecff4c/attachment.sig>


More information about the devel mailing list