[cairo] Cairo in an embedded environment: removing fontconfig,
16-bit RGB, porting issues
domlachowicz at gmail.com
Wed May 31 12:19:21 PDT 2006
> proper (not so much in pixman) but there are exceptions, such as
> several Cairo source files that directly include stdlib.h. Is
> there a reason for this? Would changes to such things be
stdlib.h is specified by the ANSI C standard and defines things like
malloc(), free(), NULL, and a grab-bag of other useful functionality.
As such, it doesn't seem to be an unreasonable dependency to me (not
that my opinion carries much weight 'round here).
Does your embedded platform not provide the header? If not, how does
it handle (eg.) userland memory allocation?
Counting bodies like sheep to the rhythm of the war drums.
More information about the cairo