Re: Weird Problem with Embedding Frameworks
Re: Weird Problem with Embedding Frameworks
- Subject: Re: Weird Problem with Embedding Frameworks
- From: Marc Weil <email@hidden>
- Date: Wed, 11 Jun 2003 16:06:59 -0400
I tried what you suggested, but it still won't work. Moving the framework to
this other folder and then adding it to the project also adds
~/Library/EmbeddedDevelopmentFrameworks to the search path, and removing it
from the search path prevents the application from opening because it can't
find the framework to link against.
This is still completely baffling me, and I cannot figure out what could
possibly be wrong. I have followed all of the steps on all of the web sites
I have come across, and have followed the advice that people have given me.
Do you perhaps have the URL to the page with the information you described
to me? Maybe there is something else on that page that would give me a clue
as to what I am doing wrong.
Thanks for the help, though. I wish it had worked...
Any other suggestions?
-- Marc Weil
On 6/10/03 10:44 PM, "Andrew Duncan" <email@hidden> wrote:
>
>
Here's a great tip I picked from somewhere on the Mulle-Kybernetik site (in
>
fact it was using the EDCommon frameworks (et al) that led to my
>
discovering this tip):
>
>
Create a new folder at ~/Library/EmbeddedDevelopmentFrameworks and put your
>
embedded frameworks in there. Since it's outside the usual frameworks
>
search path, there is no possibility of it being found "by default".
>
>
By extension, this means that, unless you have your project set up
>
correctly, those frameworks won't be found. Counter-intuitive perhaps, but
>
it worked well for me, and I moved a couple of other frameworks in there
>
also.
>
>
On a related note, for your deployment target, you should uncheck both the
>
Public and Private checkboxes, since either of them will result in the
>
headers being copied into you built product. Even this may not be enough
>
(apparently), and you can add a Shell Script build phase to find and delete
>
the Headers folders, thusly:
>
>
cd "${BUILD_DIR}/${PRODUCT_NAME}.${WRAPPER_EXTENSION}"
>
find . -name Headers -type d -exec rm -r {} \;
>
find . -name Headers -exec rm {} \;
>
>
I ran into this while using an XSLT framework which has a large number of
>
headers, and which greatly bloated the built application. The above snippet
>
fixed that, and takes almost no time to run, so it doesn't slow down your
>
builds.
>
>
Hope this helps,
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.