[cairo] Performance issue with get_text_extents

Dimiter 'malkia' Stanev malkia at gmail.com
Fri Mar 30 16:44:32 PDT 2012

	If this helps, here are the undecorated versions of these C++ symbols 
using the undname tool from Microsoft SDK:

	??0Device at Cairo@@QAE at PAU_cairo_device@@_N at Z
	public: __thiscall Cairo::Device::Device(struct _cairo_device *,bool)

	?get_device at Surface@Cairo@@QAE?AV?$RefPtr at VDevice@Cairo@@@2 at XZ
	public: class Cairo::RefPtr<class Cairo::Device> __thiscall 

	And as cairo is "C" only, you would never see such symbols in there. So 
probably these are coming from gtkmm, or anything that wraps cairo in 
C++ (cairomm?)

	From my understanding "public: __thiscall" means that the function is a 
class member function marked as public.

On 3/30/2012 4:37 PM, Robert Prückl wrote:
> Hi again,
> as so far nobody seem to have an idea about my previous post I wanted
> to upgrade to a more up-to-date version of the whole thing.
> The problem is: I cannot link cairomm 1.9.8 against cairo 1.10.2.
> The linker writes the following:
> surface.obj : error LNK2019: unresolved external symbol "public:
> __thiscall Cairo::Device::Device(struct _cairo_device *,bool)"
> (??0Device at Cairo@@QAE at PAU_cairo_device@@_N at Z) referenced in function
> "public: class Cairo::RefPtr<class Cairo::Device>  __thiscall
> Cairo::Surface::get_device(void)"
> (?get_device at Surface@Cairo@@QAE?AV?$RefPtr at VDevice@Cairo@@@2 at XZ)
> Win32\Debug\cairomm-vc100-d-1_0.dll : fatal error LNK1120: 1
> unresolved externals
> This is the only error while compiling/linking.
> Any ideas about this?
> best,
> R
> --
> cairo mailing list
> cairo at cairographics.org
> http://lists.cairographics.org/mailman/listinfo/cairo

More information about the cairo mailing list