[Releasing] OpenGL ES2.0 functionality check for Qt5 Git sources

Ramakanthreddy_Kesireddy Ramakanthreddy_Kesireddy at mahindrasatyam.com
Tue Aug 28 16:37:02 CEST 2012

Thanks a lot for pointing out..Will take care avoiding the word or images.

If I take prebuilt binaries like qt5_desktop_bin_linux32_1110.7z from http://origin.releases.qt-project.org/qt5.0-beta-snapshots/linux_32_release/qt5-beta-bin-ubuntu1110-32/2012-08-27_19-39-40/
,I neednot worry about the dependencies in the platforms I suppose and neednot built the Qt sources?.

Please confirm in this regard.


-----Original Message-----
From: releasing-bounces+ramakanthreddy_kesireddy=mahindrasatyam.com at qt-project.org [mailto:releasing-bounces+ramakanthreddy_kesireddy=mahindrasatyam.com at qt-project.org] On Behalf Of Thiago Macieira
Sent: Tuesday, August 28, 2012 7:54 PM
To: releasing at qt-project.org
Subject: Re: [Releasing] OpenGL ES2.0 functionality check for Qt5 Git sources

On terça-feira, 28 de agosto de 2012 14.02.47, Ramakanthreddy_Kesireddy wrote:
> Hi Sean,
> Please find the Open GL ES 2.0 error as attached.
> I think it got to do with
> and QMAKE_LIBS_OPENGL_ES2 as seen from the error.

> In which file and the paths do I need to modify?

Please avoid:

1) attaching Word files. Period. Don't send Word files to the mailing list.

2) attaching images for stuff that is text. Simply copy & paste the text into the email or attach a text file (.txt) containing the data.

It seems that the functionality test failed. Can you run the configure script with -v so we can see why it failed?

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden


This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.

More information about the Releasing mailing list