Re: Porting librsvg to an Embedded Platform

Hi Mohit,

>  I am afraid, we do not have a dedicated FPU on our system. Since we are
> still in the design stage, RAM and HD are not yet finalised. Could you give
> me the minimum RAM and HD requirements for librsvg? Also, would it be
> possible to port librsvg and Cairo to Fixed-Point?

Of course it would be possible (provided that there was no API/ABI
breakage). There are some patches already that port Cairo to fixed
point. I don't know how complete they are, or what their chances of
being merged upstream are.

>  "the driver interface" referred to the underlying Graphics API running on
> the system. I am assuming that librsvg runs over some Graphics API which
> allows it to interface with the display driver. Are there any minimum
> requirements on such a Graphics API?

Cairo is this "driver interface". It interfaces with a lot of Graphics
APIs, such as X11/Win32/OSX/BeOS, and also things like PNGs, PDFs, PS,
...

>  In short, would you recommend using librsvg as a starting point for porting
> it to an embedded platform (SVG-Tiny) or would you rather recommend that we
> use an existing SVG-Tiny library and port it?

Well, I can't say for sure. I don't fully understand your requirements
and schedule. I also don't know about the status of other SVG-Tiny
renderers. I do know that people have gotten librsvg to work on some
"embedded" devices, such as the Nokia 770 platform.

Best,
Dom
-- 
Counting bodies like sheep to the rhythm of the war drums

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV