>>Is there a work-around I could use in my Qt project file?

>Upgrade to 5.5.1. It's already fixed.

>The problem was not deemed important enough to affect the 5.5.0 release.


My Chicago based sales rep told me that ( somewhere buried in my license fine 
print ) I could not release software using unreleased versions of Qt Enterprise.


Lawyers frighten me much more than chief architects. :-)

-Ed





On Jul 1, 2015, at 10:19 AM, Thiago Macieira 
<thiago.macie...@intel.com<mailto:thiago.macie...@intel.com>> wrote:

On Wednesday 01 July 2015 15:15:19 Edward Sutton wrote:
Is there a work-around I could use in my Qt project file?

Upgrade to 5.5.1. It's already fixed.

The problem was not deemed important enough to affect the 5.5.0 release.
--
Thiago Macieira - thiago.macieira (AT) intel.com<http://intel.com>
 Software Architect - Intel Open Source Technology Center

_______________________________________________
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email in error 
please notify the sender. Our company accepts no liability for the contents of 
this email, or for the consequences of any actions taken on the basis of the 
information provided, unless that information is subsequently confirmed in 
writing. Please note that any views or opinions presented in this email are 
solely those of the author and do not necessarily represent those of the 
company. Finally, the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for any damage caused 
by any virus transmitted by this email.
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to