On Wednesday 28 October 2015 21:41:12 James McDonnell wrote:
> I¹ve created a QNX JIRA for the atomic function pointer compile failure.
> No idea (yet) if 6.6.0 will be patched as a result.
Thanks James!
Can you provide the patch, so we can patch our xxatomic files?
> >Plus the tests at tests/au
On 2015-10-28, 12:02 PM, "Development on behalf of Thiago Macieira"
wrote:
>On Wednesday 28 October 2015 13:28:39 Rafael Roquetto wrote:
>> Hi James,
>>
>> On Wed, Oct 28, 2015 at 02:10:02PM +, James McDonnell wrote:
>> > Fixes to 6.6.0 are...unlikely. But if you let me know what I need t
Hi,
just guessing but if your /Volumes/Data is an external hard disk this
might be due to a permissions problem. If you try testing by
(temporarily!) move the platforms directory (containing the
libqcocoa.dylib file) from /Library/Application
Support/Waves/WavesQtLibs_5.5.1/plugins/ to
Volum
On Wednesday 28 October 2015 09:04:14 Thiago Macieira wrote:
> On Wednesday 28 October 2015 13:14:40 Heikkinen Jani wrote:
> > We have finally Qt 5.6.0 beta snapshot available:
> Should the beta further wait for C++11 becoming mandatory? I was hoping we'd
> have them in by now, but it hasn't happen
On Wednesday 28 October 2015 11:25:19 Knoll Lars wrote:
> Removing QNX support is not an option; we agreed at the contributor summit
> that QNX 6.6 is part of the baseline, just as much as VS 2012 is. So if
> that toolchain has some issues, we’ll need to work around them just as for
> some other pl
On Wednesday 28 October 2015 13:14:40 Heikkinen Jani wrote:
> We have finally Qt 5.6.0 beta snapshot available:
Should the beta further wait for C++11 becoming mandatory? I was hoping we'd
have them in by now, but it hasn't happened.
Or should we release a second beta after the changes get integ
On Wednesday 28 October 2015 13:28:39 Rafael Roquetto wrote:
> Hi James,
>
> On Wed, Oct 28, 2015 at 02:10:02PM +, James McDonnell wrote:
> > Fixes to 6.6.0 are...unlikely. But if you let me know what I need to
> > take/do to re-produce the problem I can try to help out. Is it just this
> >
On Wed, Oct 28, 2015 at 11:52:20AM +, Sergio Martins wrote:
> On Tuesday, October 27, 2015 04:40:07 PM Thiago Macieira wrote:
>
> >
> > From qcompilerdetection.h:
> >
> > # if defined(_HAS_DINKUM_CLIB) && !defined(_HAS_NULLPTR_T)
> > #undef Q_COMPILER_NULLPTR
> > # endif
>
> By the wa
Hi James,
On Wed, Oct 28, 2015 at 02:10:02PM +, James McDonnell wrote:
> Fixes to 6.6.0 are...unlikely. But if you let me know what I need to
> take/do to re-produce the problem I can try to help out. Is it just this
> particular change or do I need to take all the changes in the
> 5.7-c++11
Fixes to 6.6.0 are...unlikely. But if you let me know what I need to
take/do to re-produce the problem I can try to help out. Is it just this
particular change or do I need to take all the changes in the
5.7-c++11-atomics topic?
On 2015-10-28, 7:25 AM, "Development on behalf of Knoll Lars"
wrot
Hi,
I've built Mac universal binaries of v5.5.1 (built separately for i386 and
x86_64, then used lipo).
Built and ran my Qt app (Xcode 5, Mavericks), and got this error:
. could not find or load the Qt platform plugin "cocoa".
Further diagnosis using DYLD_PRINT_LIBRARIES and QT_DEBUG_PLUGINS pr
Thanks for the quick resolution!
Rich.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi all,
We have finally Qt 5.6.0 beta snapshot available:
Mac: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/186/
Linux: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/250/
Windows: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/198/
src: download.qt.io/snapshots/qt/5.6/5.6.0-bet
On Tuesday, October 27, 2015 04:40:07 PM Thiago Macieira wrote:
>
> From qcompilerdetection.h:
>
> # if defined(_HAS_DINKUM_CLIB) && !defined(_HAS_NULLPTR_T)
> #undef Q_COMPILER_NULLPTR
> # endif
By the way, _HAS_DINKUM_CLIB is about the C library, not C++.
Should be replaced with: !_GLIB
Hi Thiago,
Removing QNX support is not an option; we agreed at the contributor summit that
QNX 6.6 is part of the baseline, just as much as VS 2012 is. So if that
toolchain has some issues, we’ll need to work around them just as for some
other platforms.
In fact, we have always been and will a
15 matches
Mail list logo
