Re: how to reduce runtime memory footprint and reduce object code

[Soho Soho123 <soho123 2012 gmail com>]

Dear Jens,

You mean:
I have to remove the code manually, right?
Even disabling transcoding that is not necessary, right?
And,
the another issue:
if I would like to remove "Video" related code , is it possible?
Or I have to remove by manually ,too?
And,
Is it possible to set max memory buffer for Rygel in run time?
Because per the testing yesterday I did, rygel will use the max free
memory for MedixExport and Renderer in run time.
In our embedd platform, there are also many applications included, not
Rygel ONLY.
Hence, if Rygel use the max free memory buffer, then other application
can not be serviced by kernel.
Could you kindly provide the idea for reducing footprint in memory buffer usage?

Thanks a lot!!!!

2012/7/10 Jens Georg <mail jensge org>:
> On Mo, 2012-07-09 at 22:18 +0800, Soho Soho123 wrote:
>
>> If I just want to use "MediaExport" and "Renderer" function only.
>> How to build the object code for MediaExport and Renderer only?
>> Not only disable other plungin but also without the code in the folder
>> /src/rygel/* that are not for MediaExport and Renderer.
>
> That's not possible without patching the code.
>
>> Because I can see rygel use the memory about 30MB when MediaExport enabled.
>> It is too much for our embedded system. My target platform max memory
>> is 64MB only.
>
>
>> And the other side,
>> How to reduce the size of Rygel's object code?
>> How many code are not necessary for MediaExport and renderer in /src/rygel/*?
>
> If you use a server and a renderer, you're virtually using everything,
> you could reduce it by disabling transcoding, though that would need
> some patching.
>
>> =====================================================================================
>> And If I just want to use Renderer ONLY,
>
> If you only want to use the renderer, you could drop a lot of source
> files there, but that would mean manipulating the build. It should be
> anything relating to http, transcoding, items and containers.
>
>