[kde-embedded] Kde porting on embedded board

Sun Jan 14 10:59:15 UTC 2018

I've encountered this issue now as well, in my case caused by an ancient 
vendor GL stack that misses a few #ifdefs that epoxy expects (vanilla Mesa 
works fine). The below patch fixed it for me, maybe something similar helps in 
your case too.

--- a/interface/khronos/include/GLES2/gl2.h
+++ b/interface/khronos/include/GLES2/gl2.h
@@ -67,6 +67,7 @@
 #endif

 /* OpenGL ES core versions */
+#ifndef GL_ES_VERSION_2_0
 #define GL_ES_VERSION_2_0                 1

 /* ClearBufferMask */
@@ -642,6 +643,7 @@
 GL_APICALL void         GL_APIENTRY glVertexAttribPointer (GLuint indx, GLint 
size, GLenum type, GLboolean normalized, GLsizei stride, const GLvoid* ptr);
 GL_APICALL void         GL_APIENTRY glViewport (GLint x, GLint y, GLsizei 
width, GLsizei height);

+#endif
 #ifdef __cplusplus
 }
 #endif


On Tuesday, 5 December 2017 12:32:54 CET prakash m wrote:
> Hi Volker,
> 
> Currently I am facing some redeclaration issue with epoxy and gle2 headers.
> Could you please give some idea to skip  this?
> 
> /home/prakash/tickets/anritusu_yocto/aniritusu_bak/build-kde-new/tmp/sysroot
> s/zcu102-zynqmp/usr/include/epoxy/gl_generated.h:15055:49: note: previous
> declaration 'void (* epoxy_glVertexAttrib4f)(GLuint, GLfloat, GLfloat,
> GLfloat, GLfloat)'
> 
> |  extern EPOXY_IMPORTEXPORT void (EPOXY_CALLSPEC
> 
> *epoxy_glVertexAttrib4f)(GLuint index, GLfloat x, GLfloat y, GLfloat z,
> GLfloat w);
> 
> |                                                  ^~~~~~~~~~~~~~~~~~~~~~
> | 
> | In file included from
> 
> /home/prakash/tickets/anritusu_yocto/aniritusu_bak/build-kde-new/tmp/sysroot
> s/zcu102-zynqmp/usr/include/qt5/QtGui/qopengl.h:109:0,
> |                  from
> 
> /home/prakash/tickets/anritusu_yocto/aniritusu_bak/build-kde-new/tmp/sysroot
> s/zcu102-zynqmp/usr/include/qt5/QtGui/qopenglcontext.h:60,
> |                  from
> 
> /home/prakash/tickets/anritusu_yocto/aniritusu_bak/build-kde-new/tmp/sysroot
> s/zcu102-zynqmp/usr/include/qt5/QtGui/QOpenGLContext:1,
> 
>  /home/prakash/tickets/anritusu_yocto/aniritusu_bak/build-kde-new/tmp/sysroo
> ts/zcu102-zynqmp/usr/include/GLES2/gl2.h:612:90: error: 'void
> epoxy_glVertexAttrib4fv(GLuint, const GLfloat*)' redeclared as different
> kind of symbol
> 
> |  GL_APICALL void         GL_APIENTRY glVertexAttrib4fv (GLuint indx,
> 
> const GLfloat* values);
> 
> 
> Thanks in Advance !!
> 
> Regards
> 
> Prakash M
> 
> On Tue, Dec 5, 2017 at 2:17 PM, prakash m <prakash56755 at gmail.com> wrote:
> > Ok,thank you very much for the clarification
> > 
> > On 5 Dec 2017 14:12, "Volker Krause" <vkrause at kde.org> wrote:
> >> Hi,
> >> 
> >> On Sunday, 3 December 2017 13:29:02 CET prakash m wrote:
> >> > Many thanks for your reply, Now I understood that differece between
> >> > both
> >> > layers.
> >> > 
> >> > Could you please clarify this?
> >> > 
> >> > We have a hardware accelerated Xserver, but not accelerated wayland.if
> >> 
> >> KDE
> >> 
> >> > will run it on X paltform, then why it requires Kwayland?
> >> 
> >> This is probably an oversight in the recipes, the Wayland scenario is
> >> much
> >> better tested than the X11 one.
> >> 
> >> > What is the difference between plasma desktop and plasma mobile in
> >> 
> >> yocto?
> >> 
> >> I don't think our recipes contain Plasma Desktop components yet, so not
> >> sure
> >> what you are referring to here. In general those are two different shells
> >> for
> >> Plasma, one for desktop devices and one for phones.
> >> 
> >> > As of know I ported the yocto-meta-kf5, now I need to have application
> >> 
> >> like
> >> 
> >> > desktop. So could you please point out some of the kde application with
> >> > desktop.
> >> 
> >> As mentioned before, we do not have Yocto recipes for applications yet.
> >> 
> >> > While porting , i face some issues on compiling , i will send some
> >> 
> >> issues
> >> 
> >> > tomorrow.
> >> > 
> >> > Example the desktoptojson binaries in native will always look the qt5
> >> > native bianries in /usr/lib/x86-64-linux-gnu/
> >> > Instead of yocto native qt5 binaries.
> >> 
> >> I didn't see this here, so no idea how that would happen, sorry.
> >> 
> >> Regards,
> >> Volker
> >> 
> >> > Thanks
> >> > 
> >> > Prakash M
> >> > 
> >> > On 3 Dec 2017 16:55, "Volker Krause" <vkrause at kde.org> wrote:
> >> > > Hi,
> >> > > 
> >> > > On Friday, 1 December 2017 15:14:12 CET prakash m wrote:
> >> > > > Currently we have qt5 running with x11 paltform and we need to have
> >> 
> >> kde
> >> 
> >> > > > with plasma framework.So which layer will be suitable for us
> >> > > > 
> >> > > > 1. yocto-meta-kde
> >> > > > 2. yocto-meta-kf5
> >> > > > 
> >> > > > Could you please explain, what is the difference between two
> >> > > > layers?
> >> > > 
> >> > > meta-kf5 contains just the KDE Frameworks 5 recipes, which is a
> >> > > prerequisite
> >> > > for Plasma or the other stuff in meta-kde.
> >> > > 
> >> > > > In yocto-meta-kde , I have seen the pacakagegroup like
> >> 
> >> plasma-mobile and
> >> 
> >> > > I
> >> > > 
> >> > > > included this packagegroup in my target.Could you please tell me
> >> 
> >> how to
> >> 
> >> > > use
> >> > > 
> >> > > > this?
> >> > > 
> >> > > Sorry to disappoint you there, but unlike meta-kf5, meta-kde is work
> >> 
> >> in
> >> 
> >> > > progress and far from complete. There are just a few of many needed
> >> > > recipes in
> >> > > there at this point to get a full Plasma (Mobile) built.
> >> > > 
> >> > > > while integrating the yocto-meta-kf5, I got the error in baloo
> >> 
> >> framework
> >> 
> >> > > > like no member defined
> >> > > > 
> >> > > >  error: 'org::kde::baloo::fileindexer {aka class
> >> > > > 
> >> > > > OrgKdeBalooFileindexerInterface}' has no member named
> >> 
> >> 'registerMonitor';
> >> 
> >> > > > did you mean 'registerUserData'?
> >> > > 
> >> > > Which Qt version are you using, and where did you take the Qt recipes
> >> > > from?
> >> > > This is a known issues with Qt 5.8 (and possibly older) from the
> >> 
> >> meta-qt
> >> 
> >> > > layer
> >> > > on Github. Qt 5.9.1 from code.qt.io fixed that me.
> >> > > 
> >> > > Regards,
> >> > > Volker

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-embedded/attachments/20180114/861bb7c9/attachment.sig>
