Hi All
I've been spending the last few hours trying to save some extra KB off of my
final exe size onIOS.
In the end I got my final exe from nearly 10 MB down to 3.T MB, sweet ay
I'm using OpenThreads, osg, osgUtil, osgGA, osgViewer, osgDB, depreciated osg
pugin and imageio plugin.
The trick
Okay... so the libraries need to have all of that (ie, all symbols), but
when the .app is created and "dead code stripping" is enabled, any
unneeded symbols are stripped away. This leaves me with an .app size of
around 15-20MB.
Thanks for everyone's help,
Mike
On 10-12-02 12:10 PM, Mike Wozni
On 10-12-02 10:43 AM, Garrett Potts wrote:
Hello Mike:
I have not tried to build the iphone OS port but it appears in your cut and
paste you have the Active configuration as Debug as seen with the link path
.Debug-iphoneos/osg.build/osg-generated-files.hmap.
Hi Garrett,
Yeah, sorry; that
Hello Mike:
I have not tried to build the iphone OS port but it appears in your cut and
paste you have the Active configuration as Debug as seen with the link path
.Debug-iphoneos/osg.build/osg-generated-files.hmap. What are the Active
configuration targets available and if a Release targe
On 10-12-02 4:53 AM, Ulrich Hertlein wrote:
On 2/12/10 15:13 , Mike Wozniewski wrote:
On 2/12/10 12:49 , Mike Wozniewski wrote:
$ du -hs *.a
328KlibOpenThreads.a
240Mlibosg.a
51MlibosgAnimation.a
116MlibosgDB.a
34MlibosgFX.a
75MlibosgGA.a
67MlibosgManipul
Hi,
Am 02.12.10 03:54, schrieb Chris 'Xenon' Hanson:
> I don't know if you can static link on iOS, or how you would go about doing
> it.
For now static linking is the only way on IOS. So the lib sizes do not
matter, as only needed code get linked into the app. And: most of the
time I am only us
On 2/12/10 15:13 , Mike Wozniewski wrote:
>> On 2/12/10 12:49 , Mike Wozniewski wrote:
>>> $ du -hs *.a
>>> 328KlibOpenThreads.a
>>> 240Mlibosg.a
>>> 51MlibosgAnimation.a
>>> 116MlibosgDB.a
>>> 34MlibosgFX.a
>>> 75MlibosgGA.a
>>> 67MlibosgManipulator.a
>>> 75M
On 10-12-01 9:03 PM, Ulrich Hertlein wrote:
On 2/12/10 12:49 , Mike Wozniewski wrote:
Just wondering about the feasibility of posting something on the app store due
to size
constraints. I'm noticing that OSG is pretty massive:
$ du -hs *.a
328KlibOpenThreads.a
240Mlibosg.a
51Mlib
On 12/1/2010 6:49 PM, Mike Wozniewski wrote:
> It's not an option to use 1GB of storage for OSG libraries. Does anyone have
> ideas of how
> to simplify the build? Is there a way to automatically remove library items
> that are not
> used?
Static linking makes a BIG difference, though it intro
On 2/12/10 12:49 , Mike Wozniewski wrote:
> Just wondering about the feasibility of posting something on the app store
> due to size
> constraints. I'm noticing that OSG is pretty massive:
>
> $ du -hs *.a
> 328KlibOpenThreads.a
> 240Mlibosg.a
> 51MlibosgAnimation.a
> 116MlibosgD
Hi all,
I've been playing around with the iPhone version of OSG lately, and I'm
pretty happy.
Just wondering about the feasibility of posting something on the app
store due to size constraints. I'm noticing that OSG is pretty massive:
$ du -hs *.a
328KlibOpenThreads.a
240Mlibosg.a
11 matches
Mail list logo
