Re: Porting windows app to OS X and it's extremely huge as a result
Re: Porting windows app to OS X and it's extremely huge as a result
- Subject: Re: Porting windows app to OS X and it's extremely huge as a result
- From: Greg Guerin <email@hidden>
- Date: Sat, 24 May 2008 10:07:11 -0700
Platon Fomichev wrote:
The application gets downloaded to the user each time, so that's
why I am so troubled. Mac binaries will be split into all possible
architectures and small helper tool will download the executable
for each architecture. Yes, here the size and d/l speed is that
important. Believe me Mac users are no different to Windows when it
comes to waiting time.
Then you should definitely be using compressed transfers and a local
cache.
Runs of zeros compress very well. When I run gzip on the 78K example
you gave, it compresses to about 1400 bytes. Jason's 12K example
compresses to 683 bytes. The gzip algorithm is available as a library.
Also, you should be using a local cache stored on disk so the app
doesn't have to get downloaded (or decompressed) each time. It
should only get downloaded if it changed, or if there's no cached copy.
Compressing and caching are very widely used for speeding up
transfers. If you're not already using these fairly simple
techniques, you should be.
Finally, what version of gcc are you using, on what OS version?
gcc --version
I got an a.out of 78K on 10.4.9 (Xcode 2.4.1), but 12K on 10.5
Leopard (Xcode 3.0), so simply using newer tools would make a big
difference.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden