All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: meta-freescale@yoctoproject.org
Subject: [meta-fsl-arm][PATCH] Adding -lEGL and -lGAL to glesv2.pc
Date: Thu, 20 Jun 2013 16:31:04 +0200	[thread overview]
Message-ID: <2169791.BFDmuhoxsk@rudolf> (raw)

From: Thomas Senyk <thomas.senyk@pelagicore.com>

libGLESv2 has undefined symbols, which get provided by libEGL and libGAL,
but libGLESv2 has no implicit 'link' to those libs.
So if you link against libGLESv2 but not against libEGL and libGAL,
you'll get 'undefined symbol'-errors.

Signed-off-by: Thomas Senyk <thomas.senyk@pelagicore.com>
---
 recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q/glesv2.pc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q/glesv2.pc 
b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q/glesv2.pc
index e92620b..9be46f2 100644
--- a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q/glesv2.pc
+++ b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q/glesv2.pc
@@ -7,6 +7,6 @@ Name: glesv2
 Description: Vivante OpenGL ES 2.0 library
 Requires.private:
 Version: 8.0
-Libs: -L${libdir} -lGLESv2
+Libs: -L${libdir} -lGLESv2 -lEGL -lGAL
 Libs.private: -lpthread -lrt
 Cflags: -I${includedir}
-- 
1.8.3.1


             reply	other threads:[~2013-06-20 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 14:31 Thomas Senyk [this message]
2013-06-20 20:00 ` [meta-fsl-arm][PATCH] Adding -lEGL and -lGAL to glesv2.pc Otavio Salvador
2013-06-20 20:33   ` Otavio Salvador
2013-06-21  9:08     ` Thomas Senyk
2013-06-21 11:52       ` Thomas Senyk
2013-06-21 12:35         ` Otavio Salvador
2013-06-21 13:02           ` Thomas Senyk
2013-06-21 13:43             ` Otavio Salvador
2013-06-21 14:24               ` Thomas Senyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2169791.BFDmuhoxsk@rudolf \
    --to=thomas.senyk@pelagicore.com \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.