Bug 55765

Summary:	EGL missing GLESv2
Product:	cairo	Reporter:	Chinasaur <chinasaurli>
Component:	gl backend	Assignee:	cairo-bugs mailing list <cairo-bugs>
Status:	RESOLVED MOVED	QA Contact:	cairo-bugs mailing list <cairo-bugs>
Severity:	minor
Priority:	medium	CC:	sergio.correia
Version:	1.12.4
Hardware:	ARM
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Chinasaur 2012-10-08 13:44:20 UTC

I'm trying to build Cairo with OpenVG support for RaspberryPi.  I wanted to be able to use Cairo to show some graphics with only a terminal session and no X.  The first thing I tried was building with only --enable-vg, but I was getting a link error with libEGL failing to find some stuff in libGLESv2.

Adding --enable-glesv2 fixes it.  But seems like if this is required by --enable-vg then maybe this should be handled automatically?  Or maybe with more preprocessing it would be possible to use EGL for OpenVG without pulling in the GLESv2 stuff?

Comment 1 Uli Schlachter 2012-10-08 14:07:33 UTC

Could you show us the error you are getting? The missing symbols from libEGL sound more like a bug in libEGL (if it needs it, it should link against it).

Comment 2 Chinasaur 2012-10-08 15:34:42 UTC

True.  My understanding from forum posts is that this only started with recent versions of the RPi videocore/GL libs.  Someone also said it had to do with pthread includes, but that didn't make much sense to me.

Will take me a bit of time to recreate errors locally but I'm 99% sure they are the same as given here: http://www.raspberrypi.org/phpBB3/viewtopic.php?t=7090&p=189926

Comment 3 GitLab Migration User 2018-08-25 13:34:14 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/cairo/cairo/issues/74.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.