Re: Larger application size
Re: Larger application size
- Subject: Re: Larger application size
- From: SA Dev <email@hidden>
- Date: Wed, 6 Jul 2005 15:20:06 -0400
Lorenzo:
In a production app, I once messed with my XCode project and
managed to do much the same thing (included a file I shouldn't have
in the built product). The problem was, it was the project notes file
I create for each project.
The *real* problem was, it had not only past problems and design
notes (fixed bugs, etc), but plans for future versions, complete with
colorful metaphors and even e-mail addresses of a few users who found
a rare bug or two that only they were experiencing.
The file was included in no less than FIVE released version
increments before I next nosed around in the app bundle and had the
naturally-resultant heart attack ...
Most unfortunate indeed. :-D
On Jul 6, 2005, at 3:06 PM, Lorenzo wrote:
Hi,
I build only for PowerPC.
I found the origin of the problem, maybe it's a bug of XCode, maybe
it's my
fault. I defined (in XCode 2.0) a Copy Phase which copies an unix
executable
file to the resource folder within my app package. Well, the original
executable file is 600 KB, and the copy made by XCode 2.1 within
the app
package is 2.3 MB !!! With Xcode 2.0 this never occurred.
I deleted the copy phase and remade it, and now it works properly.
Thank you for your support. Great list.
Best Regards
--
Lorenzo
email: email@hidden
From: SA Dev <email@hidden>
Date: Wed, 06 Jul 2005 11:22:58 -0400
To: Lorenzo <email@hidden>
Cc: Gary Yuen <email@hidden>, email@hidden
Subject: Re: Unwanted Deployment folder
Lorenzo:
Silly question: Are you building for both PowerPC and Intel
architecture?
On Jul 6, 2005, at 11:19 AM, Lorenzo wrote:
Thank you. The Gary's solution worked very well.
Now a new problems shows up. The old version of my app compiled
with XCode
2.0 was 1.3 MB large. This new version of my app compiled with
XCode 2.1 is
2.7 MB. I compiled as deployment, and I didn't touch the settings.
Just
launched the old .xcode project and let XCode 2.1 create the
new .xcodeproj
file.
I even tried to strip the executable but I didn't get any
improvement.
Best Regards
--
Lorenzo
email: email@hidden
From: Gary Yuen <email@hidden>
Date: Wed, 06 Jul 2005 20:22:38 +0800
To: Lorenzo <email@hidden>
Cc: email@hidden
Subject: Re: Unwanted Deployment folder
Hi Lorenzo,
Do this:
1. Open up properties for your Target
2. got to build tab
3. check "Deployment Location"
4. "/" for Installation Builds Product Location
5. Set Installation Directory to /Users/you/Library/Screen Savers/
I was curious too but never looked until you asked. There you go.
Gary
On 06/07/2005, at 10:55, Lorenzo wrote:
Hi,
how can I tell XCode 2.1 to not to save my application within the
folder
Deployment? I need to buil my app within
(Home)/Library/Screen Savers
So I can test the screensaver at any build in a while.
Instead now XCode 2.1 builds it within
(Home)/Library/Screen Savers/Deployment
so it cannot work from there. Some idea to prevent the creation
of the
folder "Deployment"? Thank you.
Best Regards
--
-----
Supposing truth is a woman--what then? Are there not grounds for
the
suspicion that all philosophers, insofar as they were dogmatists,
have been very inexpert about women? That the gruesome seriousness,
the clumsy obstrusiveness with which they have usually approached
truth so far have been awkward and very improper methods for
winning
a woman's heart? - Nietzsche
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40silentalcove.net
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden