Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Ulf Samuelsson]

[-- Attachment #1: Type: text/plain, Size: 6122 bytes --]


-------- Ursprungligt meddelande -------
Ämne: 	Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, 
but completes after cleaning qtbase.
Datum: 	Wed, 2 Jul 2014 09:32:27 -0400
Från: 	Denys Dmytriyenko <denys@ti.com>
Till: 	Ulf Samuelsson <meta-ti@emagii.com>
Kopia: 	<meta-ti@yoctoproject.org>



On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> When I build an image with QT5 using meta-arago, qtbase fails with a
> lot of error messages.

> This is the wrong mailing list - meta-ti has nothing to do with qtbase.

> Moreover, why are you still using 5.1.1? There were many fixes in Qt5 5.2.x
> and 5.3.x. Also, it depends on your setup and what layers and features you
> configure. Either way, it's a discussion for a distro layer, you can use
> meta-arago mailing list for that...


I looked through meta-arago and meta-qt5 about a month ago for compatability.

I checked again today:

meta-qt5/master	= 5.3.0
meta-qt5/daisy	= 5.2.1
meta-qt5/dora	= 5.1.1

meta-arago/master = 5.2.0
meta-arago/dora   = 5.2.0 (used to be 5.1.1)
There is no meta-arago/daisy branch.

The only revision I could find which was available in both was 5.1.1.
and that is why I used it.

It would make sense if the qt5 related recipes in meta-arago matched those in meta-qt5.

Now meta-arago is using 5.2.0 which is not present in any branch of meta-qt5 (did not check old branches, only dora and daisy).

I dont understand why the meta-arago:dora recipes for qt5 has been updated from 5.1.1 to 5.2.0,
thus making it incompatible with meta-qt5:dora. Isn't this a mistake.



> Some errors:
>
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:52:1:
> error: expected class-name before '{' token
> linking part1
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
> In destructor 'virtual OpenGLWindow::~OpenGLWindow()':
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> warning: possible problem detected in invocation of delete operator:
> [enabled by default]
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> warning: invalid use of incomplete type 'class QOpenGLPaintDevice'
> [enabled by default]
> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> warning: forward declaration of 'class QOpenGLPaintDevice' [enabled
> by default]
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> note: neither the destructor nor the class-specific operator delete
> will be called, even if they are declared when the class is defined
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
> In member function 'virtual void OpenGLWindow::render()':
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:78:24:
> error: invalid use of incomplete type 'class QOpenGLPaintDevice'
> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> error: forward declaration of 'class QOpenGLPaintDevice'
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:13:
> error: 'GL_COLOR_BUFFER_BIT' was not declared in this scope
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:35:
> error: 'GL_DEPTH_BUFFER_BIT' was not declared in this scope
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:57:
> error: 'GL_STENCIL_BUFFER_BIT' was not declared in this scope
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:78:
> error: 'glClear' was not declared in this scope
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:82:13:
> error: invalid use of incomplete type 'class QOpenGLPaintDevice'
> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> error: forward declaration of 'class QOpenGLPaintDevice'
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
> error: no matching function for call to
> 'QPainter::QPainter(QOpenGLPaintDevice*&)'
> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
> note: candidates are:
> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/qpainter.h:1:0,
>                  from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/QPainter:1,
>                  from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:47:
>
> Googling indicates that this is because:
>
>    "If -no-opengl is specified and OpenGL development files are
> installed, the error does occur."
>
> If I clean out qtbase, and then continue build, it will complete.
> $ bitbase -c cleansstate qtbase
> $ bitbake <image>
>
> My guess is that during configuration, OpenGL cannot be found, but
> it is there during compile.
> There seems to be a dependency error (libgles-omap3?).
>
>
>
>
> BR
> Ulf Samuelsson
> --
> _______________________________________________
> meta-ti mailing list
>meta-ti@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-ti






[-- Attachment #2: Type: text/html, Size: 8400 bytes --]

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Denys Dmytriyenko]

On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> 
> -------- Ursprungligt meddelande -------
> Ämne: 	Re: [meta-ti] Build of qtbase fails due to no OpenGL
> libraries, but completes after cleaning qtbase.
> Datum: 	Wed, 2 Jul 2014 09:32:27 -0400
> Från: 	Denys Dmytriyenko <denys@ti.com>
> Till: 	Ulf Samuelsson <meta-ti@emagii.com>
> Kopia: 	<meta-ti@yoctoproject.org>
> 
> 
> 
> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> >When I build an image with QT5 using meta-arago, qtbase fails with a
> >lot of error messages.
> 
> >This is the wrong mailing list - meta-ti has nothing to do with qtbase.
> 
> >Moreover, why are you still using 5.1.1? There were many fixes in Qt5 5.2.x
> >and 5.3.x. Also, it depends on your setup and what layers and features you
> >configure. Either way, it's a discussion for a distro layer, you can use
> >meta-arago mailing list for that...
> 
> 
> I looked through meta-arago and meta-qt5 about a month ago for compatability.
> 
> I checked again today:
> 
> meta-qt5/master	= 5.3.0
> meta-qt5/daisy	= 5.2.1
> meta-qt5/dora	= 5.1.1
> 
> meta-arago/master = 5.2.0
> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> There is no meta-arago/daisy branch.
> 
> The only revision I could find which was available in both was 5.1.1.
> and that is why I used it.
> 
> It would make sense if the qt5 related recipes in meta-arago matched those in meta-qt5.
> 
> Now meta-arago is using 5.2.0 which is not present in any branch of meta-qt5 
> (did not check old branches, only dora and daisy).
> 
> I dont understand why the meta-arago:dora recipes for qt5 has been updated from 5.1.1 to 5.2.0,
> thus making it incompatible with meta-qt5:dora. Isn't this a mistake.

meta-qt5 for long time only had master, moreover, due to some requirements, we 
needed latest 5.2 version of qt5, which was only available from master and 
not from Dora, while meta-arago was generally Dora based. Since then meta-qt5 
was updated to 5.2.1, and meta-arago has recently switched to Daisy - some 
cleanup is still going on...


> 
> 
> >Some errors:
> >
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:52:1:
> >error: expected class-name before '{' token
> >linking part1
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
> >In destructor 'virtual OpenGLWindow::~OpenGLWindow()':
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> >warning: possible problem detected in invocation of delete operator:
> >[enabled by default]
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> >warning: invalid use of incomplete type 'class QOpenGLPaintDevice'
> >[enabled by default]
> >In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> >warning: forward declaration of 'class QOpenGLPaintDevice' [enabled
> >by default]
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> >note: neither the destructor nor the class-specific operator delete
> >will be called, even if they are declared when the class is defined
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
> >In member function 'virtual void OpenGLWindow::render()':
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:78:24:
> >error: invalid use of incomplete type 'class QOpenGLPaintDevice'
> >In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> >error: forward declaration of 'class QOpenGLPaintDevice'
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:13:
> >error: 'GL_COLOR_BUFFER_BIT' was not declared in this scope
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:35:
> >error: 'GL_DEPTH_BUFFER_BIT' was not declared in this scope
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:57:
> >error: 'GL_STENCIL_BUFFER_BIT' was not declared in this scope
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:78:
> >error: 'glClear' was not declared in this scope
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:82:13:
> >error: invalid use of incomplete type 'class QOpenGLPaintDevice'
> >In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> >error: forward declaration of 'class QOpenGLPaintDevice'
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
> >error: no matching function for call to
> >'QPainter::QPainter(QOpenGLPaintDevice*&)'
> >$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
> >note: candidates are:
> >In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/qpainter.h:1:0,
> >                 from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/QPainter:1,
> >                 from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:47:
> >
> >Googling indicates that this is because:
> >
> >   "If -no-opengl is specified and OpenGL development files are
> >installed, the error does occur."
> >
> >If I clean out qtbase, and then continue build, it will complete.
> >$ bitbase -c cleansstate qtbase
> >$ bitbake <image>
> >
> >My guess is that during configuration, OpenGL cannot be found, but
> >it is there during compile.
> >There seems to be a dependency error (libgles-omap3?).
> >
> >
> >
> >
> >BR
> >Ulf Samuelsson
> >--
> >_______________________________________________
> >meta-ti mailing list
> >meta-ti@yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/meta-ti
> 
> 
> 
> 
> 

> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Ulf Samuelsson]

2014-07-02 20:13, Denys Dmytriyenko skrev:
> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
>> -------- Ursprungligt meddelande -------
>> Ämne: 	Re: [meta-ti] Build of qtbase fails due to no OpenGL
>> libraries, but completes after cleaning qtbase.
>> Datum: 	Wed, 2 Jul 2014 09:32:27 -0400
>> Från: 	Denys Dmytriyenko <denys@ti.com>
>> Till: 	Ulf Samuelsson <meta-ti@emagii.com>
>> Kopia: 	<meta-ti@yoctoproject.org>
>>
>>
>>
>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
>>> When I build an image with QT5 using meta-arago, qtbase fails with a
>>> lot of error messages.
>>> This is the wrong mailing list - meta-ti has nothing to do with qtbase.
>>> Moreover, why are you still using 5.1.1? There were many fixes in Qt5 5.2.x
>>> and 5.3.x. Also, it depends on your setup and what layers and features you
>>> configure. Either way, it's a discussion for a distro layer, you can use
>>> meta-arago mailing list for that...
>>
>> I looked through meta-arago and meta-qt5 about a month ago for compatability.
>>
>> I checked again today:
>>
>> meta-qt5/master	= 5.3.0
>> meta-qt5/daisy	= 5.2.1
>> meta-qt5/dora	= 5.1.1
>>
>> meta-arago/master = 5.2.0
>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
>> There is no meta-arago/daisy branch.
>>
>> The only revision I could find which was available in both was 5.1.1.
>> and that is why I used it.
>>
>> It would make sense if the qt5 related recipes in meta-arago matched those in meta-qt5.
>>
>> Now meta-arago is using 5.2.0 which is not present in any branch of meta-qt5
>> (did not check old branches, only dora and daisy).
>>
>> I dont understand why the meta-arago:dora recipes for qt5 has been updated from 5.1.1 to 5.2.0,
>> thus making it incompatible with meta-qt5:dora. Isn't this a mistake.
> meta-qt5 for long time only had master, moreover, due to some requirements, we
> needed latest 5.2 version of qt5, which was only available from master and
> not from Dora, while meta-arago was generally Dora based. Since then meta-qt5
> was updated to 5.2.1, and meta-arago has recently switched to Daisy - some
> cleanup is still going on...
>
I think in order to clean up:
1) meta-arago:dora should switch back to 5.1.1
2) a daisy branch should be added to meta-arago (or daisy-devel) using 5.2.1
3) meta-arago:master should be 5.3.0

5.2.0 recipes should be deleted, or moved to an intermediate branch 
(daisy-rc1?)

/Ulf


>>
>>> Some errors:
>>>
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:52:1:
>>> error: expected class-name before '{' token
>>> linking part1
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
>>> In destructor 'virtual OpenGLWindow::~OpenGLWindow()':
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
>>> warning: possible problem detected in invocation of delete operator:
>>> [enabled by default]
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
>>> warning: invalid use of incomplete type 'class QOpenGLPaintDevice'
>>> [enabled by default]
>>> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
>>> warning: forward declaration of 'class QOpenGLPaintDevice' [enabled
>>> by default]
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
>>> note: neither the destructor nor the class-specific operator delete
>>> will be called, even if they are declared when the class is defined
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
>>> In member function 'virtual void OpenGLWindow::render()':
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:78:24:
>>> error: invalid use of incomplete type 'class QOpenGLPaintDevice'
>>> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
>>> error: forward declaration of 'class QOpenGLPaintDevice'
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:13:
>>> error: 'GL_COLOR_BUFFER_BIT' was not declared in this scope
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:35:
>>> error: 'GL_DEPTH_BUFFER_BIT' was not declared in this scope
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:57:
>>> error: 'GL_STENCIL_BUFFER_BIT' was not declared in this scope
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:78:
>>> error: 'glClear' was not declared in this scope
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:82:13:
>>> error: invalid use of incomplete type 'class QOpenGLPaintDevice'
>>> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
>>> error: forward declaration of 'class QOpenGLPaintDevice'
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
>>> error: no matching function for call to
>>> 'QPainter::QPainter(QOpenGLPaintDevice*&)'
>>> $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
>>> note: candidates are:
>>> In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/qpainter.h:1:0,
>>>                  from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/QPainter:1,
>>>                  from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:47:
>>>
>>> Googling indicates that this is because:
>>>
>>>    "If -no-opengl is specified and OpenGL development files are
>>> installed, the error does occur."
>>>
>>> If I clean out qtbase, and then continue build, it will complete.
>>> $ bitbase -c cleansstate qtbase
>>> $ bitbake <image>
>>>
>>> My guess is that during configuration, OpenGL cannot be found, but
>>> it is there during compile.
>>> There seems to be a dependency error (libgles-omap3?).
>>>
>>>
>>>
>>>
>>> BR
>>> Ulf Samuelsson
>>> --
>>> _______________________________________________
>>> meta-ti mailing list
>>> meta-ti@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-ti
>>
>>
>>
>>
>> _______________________________________________
>> meta-arago mailing list
>> meta-arago@arago-project.org
>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Denys Dmytriyenko]

On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> 2014-07-02 20:13, Denys Dmytriyenko skrev:
> >On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> >>-------- Ursprungligt meddelande -------
> >>Ämne: 	Re: [meta-ti] Build of qtbase fails due to no OpenGL
> >>libraries, but completes after cleaning qtbase.
> >>Datum: 	Wed, 2 Jul 2014 09:32:27 -0400
> >>Från: 	Denys Dmytriyenko <denys@ti.com>
> >>Till: 	Ulf Samuelsson <meta-ti@emagii.com>
> >>Kopia: 	<meta-ti@yoctoproject.org>
> >>
> >>
> >>
> >>On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> >>>When I build an image with QT5 using meta-arago, qtbase fails with a
> >>>lot of error messages.
> >>>This is the wrong mailing list - meta-ti has nothing to do with qtbase.
> >>>Moreover, why are you still using 5.1.1? There were many fixes in Qt5 5.2.x
> >>>and 5.3.x. Also, it depends on your setup and what layers and features you
> >>>configure. Either way, it's a discussion for a distro layer, you can use
> >>>meta-arago mailing list for that...
> >>
> >>I looked through meta-arago and meta-qt5 about a month ago for compatability.
> >>
> >>I checked again today:
> >>
> >>meta-qt5/master	= 5.3.0
> >>meta-qt5/daisy	= 5.2.1
> >>meta-qt5/dora	= 5.1.1
> >>
> >>meta-arago/master = 5.2.0
> >>meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> >>There is no meta-arago/daisy branch.
> >>
> >>The only revision I could find which was available in both was 5.1.1.
> >>and that is why I used it.
> >>
> >>It would make sense if the qt5 related recipes in meta-arago matched those in meta-qt5.
> >>
> >>Now meta-arago is using 5.2.0 which is not present in any branch of meta-qt5
> >>(did not check old branches, only dora and daisy).
> >>
> >>I dont understand why the meta-arago:dora recipes for qt5 has been updated from 5.1.1 to 5.2.0,
> >>thus making it incompatible with meta-qt5:dora. Isn't this a mistake.
> >meta-qt5 for long time only had master, moreover, due to some requirements, we
> >needed latest 5.2 version of qt5, which was only available from master and
> >not from Dora, while meta-arago was generally Dora based. Since then meta-qt5
> >was updated to 5.2.1, and meta-arago has recently switched to Daisy - some
> >cleanup is still going on...
> >
> I think in order to clean up:
> 1) meta-arago:dora should switch back to 5.1.1
> 2) a daisy branch should be added to meta-arago (or daisy-devel) using 5.2.1
> 3) meta-arago:master should be 5.3.0
> 
> 5.2.0 recipes should be deleted, or moved to an intermediate branch
> (daisy-rc1?)

No.


> >>>Some errors:
> >>>
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:52:1:
> >>>error: expected class-name before '{' token
> >>>linking part1
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
> >>>In destructor 'virtual OpenGLWindow::~OpenGLWindow()':
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> >>>warning: possible problem detected in invocation of delete operator:
> >>>[enabled by default]
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> >>>warning: invalid use of incomplete type 'class QOpenGLPaintDevice'
> >>>[enabled by default]
> >>>In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> >>>warning: forward declaration of 'class QOpenGLPaintDevice' [enabled
> >>>by default]
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:63:12:
> >>>note: neither the destructor nor the class-specific operator delete
> >>>will be called, even if they are declared when the class is defined
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:
> >>>In member function 'virtual void OpenGLWindow::render()':
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:78:24:
> >>>error: invalid use of incomplete type 'class QOpenGLPaintDevice'
> >>>In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> >>>error: forward declaration of 'class QOpenGLPaintDevice'
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:13:
> >>>error: 'GL_COLOR_BUFFER_BIT' was not declared in this scope
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:35:
> >>>error: 'GL_DEPTH_BUFFER_BIT' was not declared in this scope
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:57:
> >>>error: 'GL_STENCIL_BUFFER_BIT' was not declared in this scope
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:80:78:
> >>>error: 'glClear' was not declared in this scope
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:82:13:
> >>>error: invalid use of incomplete type 'class QOpenGLPaintDevice'
> >>>In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:41:0:
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.h:47:7:
> >>>error: forward declaration of 'class QOpenGLPaintDevice'
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
> >>>error: no matching function for call to
> >>>'QPainter::QPainter(QOpenGLPaintDevice*&)'
> >>>$TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:84:30:
> >>>note: candidates are:
> >>>In file included from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/qpainter.h:1:0,
> >>>                 from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/include/QtGui/QPainter:1,
> >>>                 from $TMP/$WORKDIR/5.1.1-r0-arago1/qtbase-opensource-src-5.1.1/examples/gui/openglwindow/openglwindow.cpp:47:
> >>>
> >>>Googling indicates that this is because:
> >>>
> >>>   "If -no-opengl is specified and OpenGL development files are
> >>>installed, the error does occur."
> >>>
> >>>If I clean out qtbase, and then continue build, it will complete.
> >>>$ bitbase -c cleansstate qtbase
> >>>$ bitbake <image>
> >>>
> >>>My guess is that during configuration, OpenGL cannot be found, but
> >>>it is there during compile.
> >>>There seems to be a dependency error (libgles-omap3?).
> >>>
> >>>
> >>>
> >>>
> >>>BR
> >>>Ulf Samuelsson
> >>>--
> >>>_______________________________________________
> >>>meta-ti mailing list
> >>>meta-ti@yoctoproject.org
> >>>https://lists.yoctoproject.org/listinfo/meta-ti
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>meta-arago mailing list
> >>meta-arago@arago-project.org
> >>http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> 

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Ulf Samuelsson]

2014-07-02 21:18, Denys Dmytriyenko skrev:
> On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
>> 2014-07-02 20:13, Denys Dmytriyenko skrev:
>>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
>>>
>>>
>>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
>>>>> When I build an image with QT5 using meta-arago, qtbase fails with a
>>>>> lot of error messages.
>>>>> This is the wrong mailing list - meta-ti has nothing to do with qtbase.
>>>>> Moreover, why are you still using 5.1.1? There were many fixes in Qt5 5.2.x
>>>>> and 5.3.x. Also, it depends on your setup and what layers and features you
>>>>> configure. Either way, it's a discussion for a distro layer, you can use
>>>>> meta-arago mailing list for that...
>>>> I looked through meta-arago and meta-qt5 about a month ago for compatability.
>>>>
>>>> I checked again today:
>>>>
>>>> meta-qt5/master	= 5.3.0
>>>> meta-qt5/daisy	= 5.2.1
>>>> meta-qt5/dora	= 5.1.1
>>>>
>>>> meta-arago/master = 5.2.0
>>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
>>>> There is no meta-arago/daisy branch.
>>>>
>>>> The only revision I could find which was available in both was 5.1.1.
>>>> and that is why I used it.
>>>>
>>>> It would make sense if the qt5 related recipes in meta-arago matched those in meta-qt5.
>>>>
>>>> Now meta-arago is using 5.2.0 which is not present in any branch of meta-qt5
>>>> (did not check old branches, only dora and daisy).
>>>>
>>>> I dont understand why the meta-arago:dora recipes for qt5 has been updated from 5.1.1 to 5.2.0,
>>>> thus making it incompatible with meta-qt5:dora. Isn't this a mistake.
>>> meta-qt5 for long time only had master, moreover, due to some requirements, we
>>> needed latest 5.2 version of qt5, which was only available from master and
>>> not from Dora, while meta-arago was generally Dora based. Since then meta-qt5
>>> was updated to 5.2.1, and meta-arago has recently switched to Daisy - some
>>> cleanup is still going on...
>>>
>> I think in order to clean up:
>> 1) meta-arago:dora should switch back to 5.1.1
>> 2) a daisy branch should be added to meta-arago (or daisy-devel) using 5.2.1
>> 3) meta-arago:master should be 5.3.0
>>
>> 5.2.0 recipes should be deleted, or moved to an intermediate branch
>> (daisy-rc1?)
> No.
So whats the plan?
Does it make sense to have different version numbers in meta-arago, than 
in meta-qt5?

Is there a time schedule to have 5.2.1/5,3,0 support?

BR
Ulf Samuelsson

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Cooper Jr., Franklin]

> -----Original Message-----
> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> bounces@arago-project.org] On Behalf Of Ulf Samuelsson
> Sent: Wednesday, July 02, 2014 2:23 PM
> To: Dmytriyenko, Denys
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase fails due to
> no OpenGL libraries, but completes after cleaning qtbase.
> 
> 2014-07-02 21:18, Denys Dmytriyenko skrev:
> > On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> >> 2014-07-02 20:13, Denys Dmytriyenko skrev:
> >>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> >>>
> >>>
> >>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> >>>>> When I build an image with QT5 using meta-arago, qtbase fails with
> >>>>> a lot of error messages.
> >>>>> This is the wrong mailing list - meta-ti has nothing to do with qtbase.
> >>>>> Moreover, why are you still using 5.1.1? There were many fixes in
> >>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
> >>>>> layers and features you configure. Either way, it's a discussion
> >>>>> for a distro layer, you can use meta-arago mailing list for that...
> >>>> I looked through meta-arago and meta-qt5 about a month ago for
> compatability.
> >>>>
> >>>> I checked again today:
> >>>>
> >>>> meta-qt5/master	= 5.3.0
> >>>> meta-qt5/daisy	= 5.2.1
> >>>> meta-qt5/dora	= 5.1.1
> >>>>
> >>>> meta-arago/master = 5.2.0
> >>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> >>>> There is no meta-arago/daisy branch.
> >>>>
> >>>> The only revision I could find which was available in both was 5.1.1.
> >>>> and that is why I used it.
> >>>>
> >>>> It would make sense if the qt5 related recipes in meta-arago matched
> those in meta-qt5.
> >>>>
> >>>> Now meta-arago is using 5.2.0 which is not present in any branch of
> >>>> meta-qt5 (did not check old branches, only dora and daisy).
> >>>>
> >>>> I dont understand why the meta-arago:dora recipes for qt5 has been
> >>>> updated from 5.1.1 to 5.2.0, thus making it incompatible with meta-
> qt5:dora. Isn't this a mistake.
> >>> meta-qt5 for long time only had master, moreover, due to some
> >>> requirements, we needed latest 5.2 version of qt5, which was only
> >>> available from master and not from Dora, while meta-arago was
> >>> generally Dora based. Since then meta-qt5 was updated to 5.2.1, and
> >>> meta-arago has recently switched to Daisy - some cleanup is still going
> on...
> >>>
> >> I think in order to clean up:
> >> 1) meta-arago:dora should switch back to 5.1.1
> >> 2) a daisy branch should be added to meta-arago (or daisy-devel)
> >> using 5.2.1
> >> 3) meta-arago:master should be 5.3.0
> >>
> >> 5.2.0 recipes should be deleted, or moved to an intermediate branch
> >> (daisy-rc1?)
> > No.
> So whats the plan?
> Does it make sense to have different version numbers in meta-arago, than in
> meta-qt5?
> 
> Is there a time schedule to have 5.2.1/5,3,0 support?
[Franklin] The way meta-qt5 and meta-arago works is indeed different compared to other layers. Meta-arago master tracks meta-qt5 master. Meta-arago dora tracks meta-arago daisy. I think we need to properly document this and even include it in the README file but of course work on daisy is still being done so it might just be on someone's short term todo list. 

Ulf,
Are you still having issues with Qt5 support when you use meta-qt5 master?
> 
> BR
> Ulf Samuelsson
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Denys Dmytriyenko]

On Wed, Jul 02, 2014 at 03:34:38PM -0400, Cooper Jr., Franklin wrote:
> 
> 
> > -----Original Message-----
> > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > bounces@arago-project.org] On Behalf Of Ulf Samuelsson
> > Sent: Wednesday, July 02, 2014 2:23 PM
> > To: Dmytriyenko, Denys
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase fails due to
> > no OpenGL libraries, but completes after cleaning qtbase.
> > 
> > 2014-07-02 21:18, Denys Dmytriyenko skrev:
> > > On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> > >> 2014-07-02 20:13, Denys Dmytriyenko skrev:
> > >>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> > >>>
> > >>>
> > >>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> > >>>>> When I build an image with QT5 using meta-arago, qtbase fails with
> > >>>>> a lot of error messages.
> > >>>>> This is the wrong mailing list - meta-ti has nothing to do with qtbase.
> > >>>>> Moreover, why are you still using 5.1.1? There were many fixes in
> > >>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
> > >>>>> layers and features you configure. Either way, it's a discussion
> > >>>>> for a distro layer, you can use meta-arago mailing list for that...
> > >>>> I looked through meta-arago and meta-qt5 about a month ago for
> > compatability.
> > >>>>
> > >>>> I checked again today:
> > >>>>
> > >>>> meta-qt5/master	= 5.3.0
> > >>>> meta-qt5/daisy	= 5.2.1
> > >>>> meta-qt5/dora	= 5.1.1
> > >>>>
> > >>>> meta-arago/master = 5.2.0
> > >>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> > >>>> There is no meta-arago/daisy branch.
> > >>>>
> > >>>> The only revision I could find which was available in both was 5.1.1.
> > >>>> and that is why I used it.
> > >>>>
> > >>>> It would make sense if the qt5 related recipes in meta-arago matched
> > those in meta-qt5.
> > >>>>
> > >>>> Now meta-arago is using 5.2.0 which is not present in any branch of
> > >>>> meta-qt5 (did not check old branches, only dora and daisy).
> > >>>>
> > >>>> I dont understand why the meta-arago:dora recipes for qt5 has been
> > >>>> updated from 5.1.1 to 5.2.0, thus making it incompatible with meta-
> > qt5:dora. Isn't this a mistake.
> > >>> meta-qt5 for long time only had master, moreover, due to some
> > >>> requirements, we needed latest 5.2 version of qt5, which was only
> > >>> available from master and not from Dora, while meta-arago was
> > >>> generally Dora based. Since then meta-qt5 was updated to 5.2.1, and
> > >>> meta-arago has recently switched to Daisy - some cleanup is still going
> > on...
> > >>>
> > >> I think in order to clean up:
> > >> 1) meta-arago:dora should switch back to 5.1.1
> > >> 2) a daisy branch should be added to meta-arago (or daisy-devel)
> > >> using 5.2.1
> > >> 3) meta-arago:master should be 5.3.0
> > >>
> > >> 5.2.0 recipes should be deleted, or moved to an intermediate branch
> > >> (daisy-rc1?)
> > > No.
> > So whats the plan?
> > Does it make sense to have different version numbers in meta-arago, than in
> > meta-qt5?
> > 
> > Is there a time schedule to have 5.2.1/5,3,0 support?

> [Franklin] The way meta-qt5 and meta-arago works is indeed different 
> compared to other layers. Meta-arago master tracks meta-qt5 master. 
> Meta-arago dora tracks meta-arago daisy. I think we need to properly 

What? Complete nonsense!


> document this and even include it in the README file but of course work on 
> daisy is still being done so it might just be on someone's short term todo 
> list.
> 
> Ulf,
> Are you still having issues with Qt5 support when you use meta-qt5 master?
> > 
> > BR
> > Ulf Samuelsson
> > 
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Cooper Jr., Franklin]

> -----Original Message-----
> From: Dmytriyenko, Denys
> Sent: Wednesday, July 02, 2014 2:37 PM
> To: Cooper Jr., Franklin
> Cc: Ulf Samuelsson; meta-arago@arago-project.org
> Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase fails due to
> no OpenGL libraries, but completes after cleaning qtbase.
> 
> On Wed, Jul 02, 2014 at 03:34:38PM -0400, Cooper Jr., Franklin wrote:
> >
> >
> > > -----Original Message-----
> > > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > > bounces@arago-project.org] On Behalf Of Ulf Samuelsson
> > > Sent: Wednesday, July 02, 2014 2:23 PM
> > > To: Dmytriyenko, Denys
> > > Cc: meta-arago@arago-project.org
> > > Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase
> > > fails due to no OpenGL libraries, but completes after cleaning qtbase.
> > >
> > > 2014-07-02 21:18, Denys Dmytriyenko skrev:
> > > > On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> > > >> 2014-07-02 20:13, Denys Dmytriyenko skrev:
> > > >>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> > > >>>
> > > >>>
> > > >>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> > > >>>>> When I build an image with QT5 using meta-arago, qtbase fails
> > > >>>>> with a lot of error messages.
> > > >>>>> This is the wrong mailing list - meta-ti has nothing to do with
> qtbase.
> > > >>>>> Moreover, why are you still using 5.1.1? There were many fixes
> > > >>>>> in
> > > >>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
> > > >>>>> layers and features you configure. Either way, it's a
> > > >>>>> discussion for a distro layer, you can use meta-arago mailing list for
> that...
> > > >>>> I looked through meta-arago and meta-qt5 about a month ago for
> > > compatability.
> > > >>>>
> > > >>>> I checked again today:
> > > >>>>
> > > >>>> meta-qt5/master	= 5.3.0
> > > >>>> meta-qt5/daisy	= 5.2.1
> > > >>>> meta-qt5/dora	= 5.1.1
> > > >>>>
> > > >>>> meta-arago/master = 5.2.0
> > > >>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> > > >>>> There is no meta-arago/daisy branch.
> > > >>>>
> > > >>>> The only revision I could find which was available in both was 5.1.1.
> > > >>>> and that is why I used it.
> > > >>>>
> > > >>>> It would make sense if the qt5 related recipes in meta-arago
> > > >>>> matched
> > > those in meta-qt5.
> > > >>>>
> > > >>>> Now meta-arago is using 5.2.0 which is not present in any
> > > >>>> branch of
> > > >>>> meta-qt5 (did not check old branches, only dora and daisy).
> > > >>>>
> > > >>>> I dont understand why the meta-arago:dora recipes for qt5 has
> > > >>>> been updated from 5.1.1 to 5.2.0, thus making it incompatible
> > > >>>> with meta-
> > > qt5:dora. Isn't this a mistake.
> > > >>> meta-qt5 for long time only had master, moreover, due to some
> > > >>> requirements, we needed latest 5.2 version of qt5, which was
> > > >>> only available from master and not from Dora, while meta-arago
> > > >>> was generally Dora based. Since then meta-qt5 was updated to
> > > >>> 5.2.1, and meta-arago has recently switched to Daisy - some
> > > >>> cleanup is still going
> > > on...
> > > >>>
> > > >> I think in order to clean up:
> > > >> 1) meta-arago:dora should switch back to 5.1.1
> > > >> 2) a daisy branch should be added to meta-arago (or daisy-devel)
> > > >> using 5.2.1
> > > >> 3) meta-arago:master should be 5.3.0
> > > >>
> > > >> 5.2.0 recipes should be deleted, or moved to an intermediate
> > > >> branch
> > > >> (daisy-rc1?)
> > > > No.
> > > So whats the plan?
> > > Does it make sense to have different version numbers in meta-arago,
> > > than in meta-qt5?
> > >
> > > Is there a time schedule to have 5.2.1/5,3,0 support?
> 
> > [Franklin] The way meta-qt5 and meta-arago works is indeed different
> > compared to other layers. Meta-arago master tracks meta-qt5 master.
> > Meta-arago dora tracks meta-arago daisy. I think we need to properly
> 
> What? Complete nonsense!
[Franklin] Yeah looks like I was a bit off. But I saw your last email and understand your plan. I guess the short answer is that there is work that still needs to be done. 

FYI
Those graphics patches you mentioned I believe were supposed to be pushed upstream to mainline Qt so they might not apply since they have already been up streamed.

> 
> 
> > document this and even include it in the README file but of course
> > work on daisy is still being done so it might just be on someone's
> > short term todo list.
> >
> > Ulf,
> > Are you still having issues with Qt5 support when you use meta-qt5 master?
> > >
> > > BR
> > > Ulf Samuelsson
> > >
> > > _______________________________________________
> > > meta-arago mailing list
> > > meta-arago@arago-project.org
> > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Denys Dmytriyenko]

On Wed, Jul 02, 2014 at 03:42:36PM -0400, Cooper Jr., Franklin wrote:
> 
> 
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Wednesday, July 02, 2014 2:37 PM
> > To: Cooper Jr., Franklin
> > Cc: Ulf Samuelsson; meta-arago@arago-project.org
> > Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase fails due to
> > no OpenGL libraries, but completes after cleaning qtbase.
> > 
> > On Wed, Jul 02, 2014 at 03:34:38PM -0400, Cooper Jr., Franklin wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > > > bounces@arago-project.org] On Behalf Of Ulf Samuelsson
> > > > Sent: Wednesday, July 02, 2014 2:23 PM
> > > > To: Dmytriyenko, Denys
> > > > Cc: meta-arago@arago-project.org
> > > > Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase
> > > > fails due to no OpenGL libraries, but completes after cleaning qtbase.
> > > >
> > > > 2014-07-02 21:18, Denys Dmytriyenko skrev:
> > > > > On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> > > > >> 2014-07-02 20:13, Denys Dmytriyenko skrev:
> > > > >>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> > > > >>>
> > > > >>>
> > > > >>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> > > > >>>>> When I build an image with QT5 using meta-arago, qtbase fails
> > > > >>>>> with a lot of error messages.
> > > > >>>>> This is the wrong mailing list - meta-ti has nothing to do with
> > qtbase.
> > > > >>>>> Moreover, why are you still using 5.1.1? There were many fixes
> > > > >>>>> in
> > > > >>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
> > > > >>>>> layers and features you configure. Either way, it's a
> > > > >>>>> discussion for a distro layer, you can use meta-arago mailing list for
> > that...
> > > > >>>> I looked through meta-arago and meta-qt5 about a month ago for
> > > > compatability.
> > > > >>>>
> > > > >>>> I checked again today:
> > > > >>>>
> > > > >>>> meta-qt5/master	= 5.3.0
> > > > >>>> meta-qt5/daisy	= 5.2.1
> > > > >>>> meta-qt5/dora	= 5.1.1
> > > > >>>>
> > > > >>>> meta-arago/master = 5.2.0
> > > > >>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> > > > >>>> There is no meta-arago/daisy branch.
> > > > >>>>
> > > > >>>> The only revision I could find which was available in both was 5.1.1.
> > > > >>>> and that is why I used it.
> > > > >>>>
> > > > >>>> It would make sense if the qt5 related recipes in meta-arago
> > > > >>>> matched
> > > > those in meta-qt5.
> > > > >>>>
> > > > >>>> Now meta-arago is using 5.2.0 which is not present in any
> > > > >>>> branch of
> > > > >>>> meta-qt5 (did not check old branches, only dora and daisy).
> > > > >>>>
> > > > >>>> I dont understand why the meta-arago:dora recipes for qt5 has
> > > > >>>> been updated from 5.1.1 to 5.2.0, thus making it incompatible
> > > > >>>> with meta-
> > > > qt5:dora. Isn't this a mistake.
> > > > >>> meta-qt5 for long time only had master, moreover, due to some
> > > > >>> requirements, we needed latest 5.2 version of qt5, which was
> > > > >>> only available from master and not from Dora, while meta-arago
> > > > >>> was generally Dora based. Since then meta-qt5 was updated to
> > > > >>> 5.2.1, and meta-arago has recently switched to Daisy - some
> > > > >>> cleanup is still going
> > > > on...
> > > > >>>
> > > > >> I think in order to clean up:
> > > > >> 1) meta-arago:dora should switch back to 5.1.1
> > > > >> 2) a daisy branch should be added to meta-arago (or daisy-devel)
> > > > >> using 5.2.1
> > > > >> 3) meta-arago:master should be 5.3.0
> > > > >>
> > > > >> 5.2.0 recipes should be deleted, or moved to an intermediate
> > > > >> branch
> > > > >> (daisy-rc1?)
> > > > > No.
> > > > So whats the plan?
> > > > Does it make sense to have different version numbers in meta-arago,
> > > > than in meta-qt5?
> > > >
> > > > Is there a time schedule to have 5.2.1/5,3,0 support?
> > 
> > > [Franklin] The way meta-qt5 and meta-arago works is indeed different
> > > compared to other layers. Meta-arago master tracks meta-qt5 master.
> > > Meta-arago dora tracks meta-arago daisy. I think we need to properly
> > 
> > What? Complete nonsense!
> [Franklin] Yeah looks like I was a bit off. But I saw your last email and 
> understand your plan. I guess the short answer is that there is work that 
> still needs to be done.

And while "meta-arago dora tracks meta-arago daisy" is obviously a typo, it 
was funnily recursive :)


> FYI
> Those graphics patches you mentioned I believe were supposed to be pushed 
> upstream to mainline Qt so they might not apply since they have already been 
> up streamed.

Yeah, I checked them quickly previously and noticed that not all of them got 
accepted upstream and sometimes even partially, so I can't really say what's 
in and what's not...


> > > document this and even include it in the README file but of course
> > > work on daisy is still being done so it might just be on someone's
> > > short term todo list.
> > >
> > > Ulf,
> > > Are you still having issues with Qt5 support when you use meta-qt5 master?
> > > >
> > > > BR
> > > > Ulf Samuelsson
> > > >
> > > > _______________________________________________
> > > > meta-arago mailing list
> > > > meta-arago@arago-project.org
> > > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Ulf Samuelsson]

2014-07-02 21:34, Cooper Jr., Franklin skrev:
>
>> -----Original Message-----
>> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
>> bounces@arago-project.org] On Behalf Of Ulf Samuelsson
>> Sent: Wednesday, July 02, 2014 2:23 PM
>> To: Dmytriyenko, Denys
>> Cc: meta-arago@arago-project.org
>> Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase fails due to
>> no OpenGL libraries, but completes after cleaning qtbase.
>>
>> 2014-07-02 21:18, Denys Dmytriyenko skrev:
>>> On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
>>>> 2014-07-02 20:13, Denys Dmytriyenko skrev:
>>>>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
>>>>>
>>>>>
>>>>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
>>>>>>> When I build an image with QT5 using meta-arago, qtbase fails with
>>>>>>> a lot of error messages.
>>>>>>> This is the wrong mailing list - meta-ti has nothing to do with qtbase.
>>>>>>> Moreover, why are you still using 5.1.1? There were many fixes in
>>>>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
>>>>>>> layers and features you configure. Either way, it's a discussion
>>>>>>> for a distro layer, you can use meta-arago mailing list for that...
>>>>>> I looked through meta-arago and meta-qt5 about a month ago for
>> compatability.
>>>>>> I checked again today:
>>>>>>
>>>>>> meta-qt5/master	= 5.3.0
>>>>>> meta-qt5/daisy	= 5.2.1
>>>>>> meta-qt5/dora	= 5.1.1
>>>>>>
>>>>>> meta-arago/master = 5.2.0
>>>>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
>>>>>> There is no meta-arago/daisy branch.
>>>>>>
>>>>>> The only revision I could find which was available in both was 5.1.1.
>>>>>> and that is why I used it.
>>>>>>
>>>>>> It would make sense if the qt5 related recipes in meta-arago matched
>> those in meta-qt5.
>>>>>> Now meta-arago is using 5.2.0 which is not present in any branch of
>>>>>> meta-qt5 (did not check old branches, only dora and daisy).
>>>>>>
>>>>>> I dont understand why the meta-arago:dora recipes for qt5 has been
>>>>>> updated from 5.1.1 to 5.2.0, thus making it incompatible with meta-
>> qt5:dora. Isn't this a mistake.
>>>>> meta-qt5 for long time only had master, moreover, due to some
>>>>> requirements, we needed latest 5.2 version of qt5, which was only
>>>>> available from master and not from Dora, while meta-arago was
>>>>> generally Dora based. Since then meta-qt5 was updated to 5.2.1, and
>>>>> meta-arago has recently switched to Daisy - some cleanup is still going
>> on...
>>>> I think in order to clean up:
>>>> 1) meta-arago:dora should switch back to 5.1.1
>>>> 2) a daisy branch should be added to meta-arago (or daisy-devel)
>>>> using 5.2.1
>>>> 3) meta-arago:master should be 5.3.0
>>>>
>>>> 5.2.0 recipes should be deleted, or moved to an intermediate branch
>>>> (daisy-rc1?)
>>> No.
>> So whats the plan?
>> Does it make sense to have different version numbers in meta-arago, than in
>> meta-qt5?
>>
>> Is there a time schedule to have 5.2.1/5,3,0 support?
> [Franklin] The way meta-qt5 and meta-arago works is indeed different compared to other layers. Meta-arago master tracks meta-qt5 master. Meta-arago dora tracks meta-arago daisy. I think we need to properly document this and even include it in the README file but of course work on daisy is still being done so it might just be on someone's short term todo list.
>
> Ulf,
> Are you still having issues with Qt5 support when you use meta-qt5 master?
I have Beaglebone Black + LCD4 (from 4D systems) running

meta-arago:dora (1 month old checkout using Qt-5.1.1)
meta-qt5:dora
linux_ti_staging-3.12.20

Customer is currently developing on both AM335x and iMX6,
and will make final selection later this year.

Customer wants to be Yocto-1.6 compatible and is using QT 5.2.1 for the 
iMX6 development.
Would like to use the same or later for the Beaglebone Black.

Mixing dora and daisy branches, if true is not intuitive.

One issue which I need to investigate, is the colours.
At boot, the Penguin appears with Blue feet, and not Yellow/Orange
and the customer splash screen and applications also have the wrong colour.

I disabled the meta-arago psplash by

BBMASK = "meta-arago-distro/recipes-core/psplash/"

in 'local.conf' and there is no longer an '-arago' addition to the 
version name.

Have not had the time to study the issue further, but would appreciate 
ideas.


>> BR
>> Ulf Samuelsson
>>
>> _______________________________________________
>> meta-arago mailing list
>> meta-arago@arago-project.org
>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Cooper Jr., Franklin]

> -----Original Message-----
> From: Ulf Samuelsson [mailto:meta-arago@emagii.com]
> Sent: Wednesday, July 02, 2014 3:26 PM
> To: Cooper Jr., Franklin; Dmytriyenko, Denys
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase fails due to
> no OpenGL libraries, but completes after cleaning qtbase.
> 
> 2014-07-02 21:34, Cooper Jr., Franklin skrev:
> >
> >> -----Original Message-----
> >> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> >> bounces@arago-project.org] On Behalf Of Ulf Samuelsson
> >> Sent: Wednesday, July 02, 2014 2:23 PM
> >> To: Dmytriyenko, Denys
> >> Cc: meta-arago@arago-project.org
> >> Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase
> >> fails due to no OpenGL libraries, but completes after cleaning qtbase.
> >>
> >> 2014-07-02 21:18, Denys Dmytriyenko skrev:
> >>> On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> >>>> 2014-07-02 20:13, Denys Dmytriyenko skrev:
> >>>>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> >>>>>
> >>>>>
> >>>>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> >>>>>>> When I build an image with QT5 using meta-arago, qtbase fails
> >>>>>>> with a lot of error messages.
> >>>>>>> This is the wrong mailing list - meta-ti has nothing to do with qtbase.
> >>>>>>> Moreover, why are you still using 5.1.1? There were many fixes
> >>>>>>> in
> >>>>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
> >>>>>>> layers and features you configure. Either way, it's a discussion
> >>>>>>> for a distro layer, you can use meta-arago mailing list for that...
> >>>>>> I looked through meta-arago and meta-qt5 about a month ago for
> >> compatability.
> >>>>>> I checked again today:
> >>>>>>
> >>>>>> meta-qt5/master	= 5.3.0
> >>>>>> meta-qt5/daisy	= 5.2.1
> >>>>>> meta-qt5/dora	= 5.1.1
> >>>>>>
> >>>>>> meta-arago/master = 5.2.0
> >>>>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> >>>>>> There is no meta-arago/daisy branch.
> >>>>>>
> >>>>>> The only revision I could find which was available in both was 5.1.1.
> >>>>>> and that is why I used it.
> >>>>>>
> >>>>>> It would make sense if the qt5 related recipes in meta-arago
> >>>>>> matched
> >> those in meta-qt5.
> >>>>>> Now meta-arago is using 5.2.0 which is not present in any branch
> >>>>>> of
> >>>>>> meta-qt5 (did not check old branches, only dora and daisy).
> >>>>>>
> >>>>>> I dont understand why the meta-arago:dora recipes for qt5 has
> >>>>>> been updated from 5.1.1 to 5.2.0, thus making it incompatible
> >>>>>> with meta-
> >> qt5:dora. Isn't this a mistake.
> >>>>> meta-qt5 for long time only had master, moreover, due to some
> >>>>> requirements, we needed latest 5.2 version of qt5, which was only
> >>>>> available from master and not from Dora, while meta-arago was
> >>>>> generally Dora based. Since then meta-qt5 was updated to 5.2.1,
> >>>>> and meta-arago has recently switched to Daisy - some cleanup is
> >>>>> still going
> >> on...
> >>>> I think in order to clean up:
> >>>> 1) meta-arago:dora should switch back to 5.1.1
> >>>> 2) a daisy branch should be added to meta-arago (or daisy-devel)
> >>>> using 5.2.1
> >>>> 3) meta-arago:master should be 5.3.0
> >>>>
> >>>> 5.2.0 recipes should be deleted, or moved to an intermediate branch
> >>>> (daisy-rc1?)
> >>> No.
> >> So whats the plan?
> >> Does it make sense to have different version numbers in meta-arago,
> >> than in meta-qt5?
> >>
> >> Is there a time schedule to have 5.2.1/5,3,0 support?
> > [Franklin] The way meta-qt5 and meta-arago works is indeed different
> compared to other layers. Meta-arago master tracks meta-qt5 master. Meta-
> arago dora tracks meta-arago daisy. I think we need to properly document
> this and even include it in the README file but of course work on daisy is still
> being done so it might just be on someone's short term todo list.
> >
> > Ulf,
> > Are you still having issues with Qt5 support when you use meta-qt5 master?
> I have Beaglebone Black + LCD4 (from 4D systems) running
> 
> meta-arago:dora (1 month old checkout using Qt-5.1.1) meta-qt5:dora
> linux_ti_staging-3.12.20
> 
> Customer is currently developing on both AM335x and iMX6, and will make
> final selection later this year.
> 
> Customer wants to be Yocto-1.6 compatible and is using QT 5.2.1 for the
> iMX6 development.
> Would like to use the same or later for the Beaglebone Black.
> 
> Mixing dora and daisy branches, if true is not intuitive.
[Franklin] Ignore what I said look at Denys latest response.
> 
> One issue which I need to investigate, is the colours.
> At boot, the Penguin appears with Blue feet, and not Yellow/Orange and the
> customer splash screen and applications also have the wrong colour.
> 
[Franklin] I believe that color issue has to-do with the am335x errata http://www.ti.com/lit/er/sprz360f/sprz360f.pdf (page 8). The BBB is hooked up to display correctly in 16bpp mode but if you use 24bpp then your colors will look messed up.
I recommend posting this question to e2e.ti.com and the right people can help you with this.

> I disabled the meta-arago psplash by
> 
> BBMASK = "meta-arago-distro/recipes-core/psplash/"
> 
> in 'local.conf' and there is no longer an '-arago' addition to the version name.
> 
> Have not had the time to study the issue further, but would appreciate ideas.
> 
> 
> >> BR
> >> Ulf Samuelsson
> >>
> >> _______________________________________________
> >> meta-arago mailing list
> >> meta-arago@arago-project.org
> >> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Color output (was: Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase)

[Ulf Samuelsson]

[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]

 >> One issue which I need to investigate, is the colours.
 >> At boot, the Penguin appears with Blue feet, and not Yellow/Orange 
and the
 >> customer splash screen and applications also have the wrong colour.

 > [Franklin] I believe that color issue has to-do with the am335x errata
 >    (http://www.ti.com/lit/er/sprz360f/sprz360f.pdf (page 8). )
 > The BBB is hooked up to display correctly in 16bpp mode but if you 
use 24bpp then your colors will look messed up.
 > I recommend posting this question to e2e.ti.com and the right people 
can help you with this.

Did a posting there, yet to get a reply, so I am posting here as well.


My custom device-tree file was based on the LCD4 device tree files. Some 
excerpts:


         lcdc: lcdc@0x4830e000 {
             compatible = "ti,am33xx-tilcdc";
             reg = <0x4830e000 0x1000>;
             interrupt-parent = <&intc>;
             interrupts = <36>;
             clocks = <&lcd_gclk>;
             clock-names = "fck";
             ti,hwmods = "lcdc";
             status = "okay";
         };

/* fbdev entry */
&lcdc {
     pinctrl-names = "default";
     pinctrl-0 = <&bone_lcd4_cape_lcd_pins>;
     status = "okay";
     display-timings {
         480x272 {
             clock-frequency = <9000000>;
             hactive         = <480>;
             vactive         = <272>;
             hfront-porch    = <9>;
             hback-porch     = <44>;
             hsync-len       = <5>;
             vback-porch     = <13>;
             vfront-porch    = <4>;
             vsync-len       = <10>;
             hsync-active    = <0>;
             vsync-active    = <0>;
         };
     };
};

Any view on the correctness of this?

"omaplfb" loads with this. Is this because it (compatible = "ti") is true?
The "tilcdc" driver is not even compiled.

Is there any documentation on device tree bindings for the "omaplfb"?

Meanwhile, I am adding 'bpp = <16>;' based on other examples

         lcdc: lcdc@0x4830e000 {
             compatible = "ti,am33xx-tilcdc";
             reg = <0x4830e000 0x1000>;
             interrupt-parent = <&intc>;
             interrupts = <36>;
             bpp = <16>;
             clocks = <&lcd_gclk>;
             clock-names = "fck";
             ti,hwmods = "lcdc";
             status = "okay";
         };

BR
Ulf Samuelsson


[-- Attachment #2: Type: text/html, Size: 5285 bytes --]

BBB Problem: No USB host at boot

[Ulf Samuelsson]

Building for the Beaglebone Black, using 
meta-arago:dora/meta-ti:dora/linux-ti-staging_3.12

I boot with a mouse inserted in the USB host connector.   It is not 
detected.

$ lsusb gives an empty result

$ lsmod does not show anything but graphics

I need to start the USB host manually, for things to be working.

$ modprobe musb_am335x

Then the mouse is detected and lsusb gives the desired output

root@beaglebone:/# lsusb
Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button 
Wheel Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


BR
Ulf Samuelsson

Re: BBB Problem: No USB host at boot

[Denys Dmytriyenko]

On Thu, Jul 03, 2014 at 01:43:23PM +0200, Ulf Samuelsson wrote:
> Building for the Beaglebone Black, using
> meta-arago:dora/meta-ti:dora/linux-ti-staging_3.12
> 
> I boot with a mouse inserted in the USB host connector.   It is not
> detected.
> 
> $ lsusb gives an empty result
> 
> $ lsmod does not show anything but graphics
> 
> I need to start the USB host manually, for things to be working.
> 
> $ modprobe musb_am335x
> 
> Then the mouse is detected and lsusb gives the desired output
> 
> root@beaglebone:/# lsusb
> Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical
> 5-Button Wheel Mouse
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I got it fixed in OE-Core master, waiting for backport to Daisy...

-- 
Denys

Re: Color output

[Ulf Samuelsson]

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

2014-07-03 08:23, Ulf Samuelsson skrev:
> >> One issue which I need to investigate, is the colours.
> >> At boot, the Penguin appears with Blue feet, and not Yellow/Orange 
> and the
> >> customer splash screen and applications also have the wrong colour.
>
> > [Franklin] I believe that color issue has to-do with the am335x errata
> >    (http://www.ti.com/lit/er/sprz360f/sprz360f.pdf (page 8). )
> > The BBB is hooked up to display correctly in 16bpp mode but if you 
> use 24bpp then your colors will look messed up.
> > I recommend posting this question to e2e.ti.com and the right people 
> can help you with this.
>
> Did a posting there, yet to get a reply, so I am posting here as well.

I have found a workaround.

Before I run S00psplash,

I will do 'fbset -depth 16'

Then psplash looks OK, and omaplfb loads, and the applications look right.

Now I only need to figure out how to do 16 bpp in the Device Tree file 
for the da8xx-fb driver.

For the tilcdc there is the tilcdc-panel.c file.
Is there something similar for the da8xx-fb driver?

BR
Ulf Samuelsson

[-- Attachment #2: Type: text/html, Size: 1985 bytes --]

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Ulf Samuelsson]

2014-07-02 22:26, Ulf Samuelsson skrev:
> 2014-07-02 21:34, Cooper Jr., Franklin skrev:
>>
>>> -----Original Message-----
>>> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
>>> bounces@arago-project.org] On Behalf Of Ulf Samuelsson
>>> Sent: Wednesday, July 02, 2014 2:23 PM
>>> To: Dmytriyenko, Denys
>>> Cc: meta-arago@arago-project.org
>>> Subject: Re: [meta-arago] Fwd: Fwd: Re: [meta-ti] Build of qtbase 
>>> fails due to
>>> no OpenGL libraries, but completes after cleaning qtbase.
>>>
>>> 2014-07-02 21:18, Denys Dmytriyenko skrev:
>>>> On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
>>>>> 2014-07-02 20:13, Denys Dmytriyenko skrev:
>>>>>> On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
>>>>>>>> When I build an image with QT5 using meta-arago, qtbase fails with
>>>>>>>> a lot of error messages.
>>>>>>>> This is the wrong mailing list - meta-ti has nothing to do with 
>>>>>>>> qtbase.
>>>>>>>> Moreover, why are you still using 5.1.1? There were many fixes in
>>>>>>>> Qt5 5.2.x and 5.3.x. Also, it depends on your setup and what
>>>>>>>> layers and features you configure. Either way, it's a discussion
>>>>>>>> for a distro layer, you can use meta-arago mailing list for 
>>>>>>>> that...
>>>>>>> I looked through meta-arago and meta-qt5 about a month ago for
>>> compatability.
>>>>>>> I checked again today:
>>>>>>>
>>>>>>> meta-qt5/master    = 5.3.0
>>>>>>> meta-qt5/daisy    = 5.2.1
>>>>>>> meta-qt5/dora    = 5.1.1
>>>>>>>
>>>>>>> meta-arago/master = 5.2.0
>>>>>>> meta-arago/dora   = 5.2.0 (used to be 5.1.1)
>>>>>>> There is no meta-arago/daisy branch.
>>>>>>>
>>>>>>> The only revision I could find which was available in both was 
>>>>>>> 5.1.1.
>>>>>>> and that is why I used it.
>>>>>>>
>>>>>>> It would make sense if the qt5 related recipes in meta-arago 
>>>>>>> matched
>>> those in meta-qt5.
>>>>>>> Now meta-arago is using 5.2.0 which is not present in any branch of
>>>>>>> meta-qt5 (did not check old branches, only dora and daisy).
>>>>>>>
>>>>>>> I dont understand why the meta-arago:dora recipes for qt5 has been
>>>>>>> updated from 5.1.1 to 5.2.0, thus making it incompatible with meta-
>>> qt5:dora. Isn't this a mistake.
>>>>>> meta-qt5 for long time only had master, moreover, due to some
>>>>>> requirements, we needed latest 5.2 version of qt5, which was only
>>>>>> available from master and not from Dora, while meta-arago was
>>>>>> generally Dora based. Since then meta-qt5 was updated to 5.2.1, and
>>>>>> meta-arago has recently switched to Daisy - some cleanup is still 
>>>>>> going
>>> on...
>>>>> I think in order to clean up:
>>>>> 1) meta-arago:dora should switch back to 5.1.1
>>>>> 2) a daisy branch should be added to meta-arago (or daisy-devel)
>>>>> using 5.2.1
>>>>> 3) meta-arago:master should be 5.3.0
>>>>>
>>>>> 5.2.0 recipes should be deleted, or moved to an intermediate branch
>>>>> (daisy-rc1?)
>>>> No.
>>> So whats the plan?
>>> Does it make sense to have different version numbers in meta-arago, 
>>> than in
>>> meta-qt5?
>>>
>>> Is there a time schedule to have 5.2.1/5,3,0 support?
>> [Franklin] The way meta-qt5 and meta-arago works is indeed different 
>> compared to other layers. Meta-arago master tracks meta-qt5 master. 
>> Meta-arago dora tracks meta-arago daisy. I think we need to properly 
>> document this and even include it in the README file but of course 
>> work on daisy is still being done so it might just be on someone's 
>> short term todo list.
>>
>> Ulf,
>> Are you still having issues with Qt5 support when you use meta-qt5 
>> master?
> I have Beaglebone Black + LCD4 (from 4D systems) running
>
> meta-arago:dora (1 month old checkout using Qt-5.1.1)
> meta-qt5:dora
> linux_ti_staging-3.12.20
Think I was to quick here. Went back and rechecked.

According to Documentation, meta-arago is not yet compatible with daisy,
so I checked what support is available in meta-qt5:dora and this is 5.1.1.

I decided to use this version, and converted the existing 5.2.0 support 
in meta-arago:dora
to 5.1.1 and added to a "bugfix" layer which overrides meta-arago..

BR
Ulf

>
> Customer is currently developing on both AM335x and iMX6,
> and will make final selection later this year.
>
> Customer wants to be Yocto-1.6 compatible and is using QT 5.2.1 for 
> the iMX6 development.
> Would like to use the same or later for the Beaglebone Black.
>
> Mixing dora and daisy branches, if true is not intuitive.
>
> One issue which I need to investigate, is the colours.
> At boot, the Penguin appears with Blue feet, and not Yellow/Orange
> and the customer splash screen and applications also have the wrong 
> colour.
>
> I disabled the meta-arago psplash by
>
> BBMASK = "meta-arago-distro/recipes-core/psplash/"
>
> in 'local.conf' and there is no longer an '-arago' addition to the 
> version name.
>
> Have not had the time to study the issue further, but would appreciate 
> ideas.
>
>
>>> BR
>>> Ulf Samuelsson
>>>
>>> _______________________________________________
>>> meta-arago mailing list
>>> meta-arago@arago-project.org
>>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [meta-ti] Build of qtbase fails due to no OpenGL libraries, but completes after cleaning qtbase.

[Denys Dmytriyenko]

On Wed, Jul 02, 2014 at 09:22:50PM +0200, Ulf Samuelsson wrote:
> 2014-07-02 21:18, Denys Dmytriyenko skrev:
> >On Wed, Jul 02, 2014 at 09:13:16PM +0200, Ulf Samuelsson wrote:
> >>2014-07-02 20:13, Denys Dmytriyenko skrev:
> >>>On Wed, Jul 02, 2014 at 08:05:09PM +0200, Ulf Samuelsson wrote:
> >>>
> >>>
> >>>On Wed, Jul 02, 2014 at 07:21:24AM +0200, Ulf Samuelsson wrote:
> >>>>>When I build an image with QT5 using meta-arago, qtbase fails with a
> >>>>>lot of error messages.
> >>>>>This is the wrong mailing list - meta-ti has nothing to do with qtbase.
> >>>>>Moreover, why are you still using 5.1.1? There were many fixes in Qt5 5.2.x
> >>>>>and 5.3.x. Also, it depends on your setup and what layers and features you
> >>>>>configure. Either way, it's a discussion for a distro layer, you can use
> >>>>>meta-arago mailing list for that...
> >>>>I looked through meta-arago and meta-qt5 about a month ago for compatability.
> >>>>
> >>>>I checked again today:
> >>>>
> >>>>meta-qt5/master	= 5.3.0
> >>>>meta-qt5/daisy	= 5.2.1
> >>>>meta-qt5/dora	= 5.1.1
> >>>>
> >>>>meta-arago/master = 5.2.0
> >>>>meta-arago/dora   = 5.2.0 (used to be 5.1.1)
> >>>>There is no meta-arago/daisy branch.
> >>>>
> >>>>The only revision I could find which was available in both was 5.1.1.
> >>>>and that is why I used it.
> >>>>
> >>>>It would make sense if the qt5 related recipes in meta-arago matched those in meta-qt5.
> >>>>
> >>>>Now meta-arago is using 5.2.0 which is not present in any branch of meta-qt5
> >>>>(did not check old branches, only dora and daisy).
> >>>>
> >>>>I dont understand why the meta-arago:dora recipes for qt5 has been updated from 5.1.1 to 5.2.0,
> >>>>thus making it incompatible with meta-qt5:dora. Isn't this a mistake.
> >>>meta-qt5 for long time only had master, moreover, due to some requirements, we
> >>>needed latest 5.2 version of qt5, which was only available from master and
> >>>not from Dora, while meta-arago was generally Dora based. Since then meta-qt5
> >>>was updated to 5.2.1, and meta-arago has recently switched to Daisy - some
> >>>cleanup is still going on...
> >>>
> >>I think in order to clean up:
> >>1) meta-arago:dora should switch back to 5.1.1
> >>2) a daisy branch should be added to meta-arago (or daisy-devel) using 5.2.1
> >>3) meta-arago:master should be 5.3.0
> >>
> >>5.2.0 recipes should be deleted, or moved to an intermediate branch
> >>(daisy-rc1?)
> >No.
> So whats the plan?

meta-arago always tracks stable and is currently being updated for Daisy. This 
is not yet complete and once it is, I'll have the bbappends updated to 
whatever the current version is at the time in meta-qt5/daisy. It's 5.2.1 
right now, but those bbappends with patches no longer apply cleanly, so some 
additional work with graphics team will be needed...


> Does it make sense to have different version numbers in meta-arago,
> than in meta-qt5?

If they are used, then no, they shouldn't be different. But they are not 
currently used though, with qt4 still being the default in meta-arago. That's 
why those bbappends are not yet updated, but are next on my plate.


> Is there a time schedule to have 5.2.1/5,3,0 support?

As of 5.3.0 - not until it gets merged into Daisy or until the next stable 
release, so October/November or even later. Unless we need it now for some 
other reason, like we had with 5.2.x for some specific critical fixed that 
were not available in 5.1.x and we needed them in Dylan/Dora. But I'm not 
aware of any breakage in 5.2.x that would push us towards 5.3.x.

For 5.2.1 - see above. Hopefully in the coming weeks. The only problem is that 
those bbappends carry some SGX/GLES patches, which no longer apply - would 
need our graphics experts to look at.

-- 
Denys