[python-ogre] Python-ogre questions

5 views
Skip to first unread message

Aleh Arol

unread,
Apr 25, 2010, 2:16:36 AM4/25/10
to python-ogre...@googlegroups.com
Hi. I thought I will found answers by searching the ML and forum but
quick search didn't get results. So:

1) _ogre.so I'm having is about 80 mb (1.7RC1). The question is how I
can reduce its size? I found some mentions about gcc visibility flag but
it's not completely clear how I can use it (there are some notes about
enabling/disabling this flag in different places so I'm unsure what
exactly to do).

2) I want to be able to trace python- ogre calls into ogre itself. And I
know I need debug versions of python and ogre at least. Now I have
release versions of everything and I'd like to have both at once and to
be able to switch between them. So the question: what steps I need to
repeat in order to get a debug version while I already have release(I
guess I don't need generating code again)? Do I need to recompile py++
generated code with -g and without O's as well and have 2 separate
python packages for debug and release?

And thank you all for python-ogre:).

--
You received this message because you are subscribed to the Google Groups "Python Ogre Developers" group.
To post to this group, send email to python-ogre...@googlegroups.com.
To unsubscribe from this group, send email to python-ogre-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/python-ogre-developers?hl=en.

Enrico Zschemisch

unread,
Apr 25, 2010, 7:46:25 AM4/25/10
to python-ogre...@googlegroups.com

Hi,

> 1) _ogre.so I'm having is about 80 mb (1.7RC1). The question is how I
> can reduce its size?
I dont think there is any way to reduce the size by a reasonable amount.
python-ogre is huge load of C++-code, which easily generates so big files.
You could try "strip" on the files.

> what steps I need to
> repeat in order to get a debug version while I already have release(I
> guess I don't need generating code again)? Do I need to recompile py++
> generated code with -g and without O's as well and have 2 separate
> python packages for debug and release?
Yes, that is exactly the way I would propose. First get Ogre in a debug
compiled fashion, then recompile python-ogre with debug.


Regards,
Enrico
Reply all
Reply to author
Forward
0 new messages