Avoiding Bloated Binary - Choose Included Library When Compiling

Solar2D Daily Builds and Public Releases
#1

Hello,

We have used Corona for a while, from the time when there are no third-party library until now when there are so many third party libraries like OpenFeint, SuperRewards, InMobi, Papaya, Flurry, Analytics, etc.

This is a good things since third-party acknowledge Corona as cross-platform apps dev!

However, from my observation, Corona’s compiled binary, whether APK on android or IPA on iphone is getting “fat” or bloated. If you inspect the resulted IPA, you would find many third-party .nib files in your IPA, which is sometimes unnecessary. Same thing goes to the resulted APK, you could decode the APK and look at the package…

Soon, there will be many more third-party library integrated with Corona. If Corona strive for smallest binary possible like the old time, i think it is a good idea to be able to choose included library when compiling Corona apps.

What do you guys think? [import]uid: 41267 topic_id: 14783 reply_id: 314783[/import]

#2

I’m not so long with Corona, but when I took a look in the builded packages I thought the same.

I think the way as it is, it is easier for “make something colorful and let it grow” developers to avoid pitfalls and easier for Ansca to support them and maybe a lesser configurable build process is also easier, but I’d like to make a clear configuration what I need and what I can let out of the resulting package.

It reminds me to the problem with the Android permission on the Wifi only Galaxy Tab which is just there because someone could use the Papaya features.

One could make a “Yes I can” configure my creation - and based on this step in to the fine tuning - so everybody could go for the way he like - Joke: US Style: We make everything bigger - Yes we can! Asian Style: Proud to be smart and smaller - As European I’m hopefully anywhere in the middle :wink:

Some developers do fiddling around in the builded packages to come closer to fat free builds and go around the permission problem, but I think that’s not the way how it should work.

Sorry for my worried English… [import]uid: 70114 topic_id: 14783 reply_id: 54688[/import]

#3

Oh! Right now I found out Ansca is thinking in the same direction:

http://developer.anscamobile.com/forum/2011/09/06/whats-all-ppy-resources

[import]uid: 70114 topic_id: 14783 reply_id: 54689[/import]

#4

Additionally, it’s not only Android’s APK which is bloated, in IOS you could also see unnecessary .nib files when you open the .app package.

And yes, i am subscribed users using latest daily build :slight_smile: [import]uid: 41267 topic_id: 14783 reply_id: 54690[/import]