Re: [Development] Using #pragma once

/show_bug.cgi?format=multiple&id=56549 3. #pragma once makes gcc much slower according to Bug 58770 - GCC very slow compiling with #pragma once https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58770 Regards, Gunnar Roth -- Original Message -- From: "Lars Knoll" To: &

Re: [Development] Qt 5.10.0 RC out

The wiki now says: Release Candidate 2 Week 48 /2017 1.12.2017 Release Candidate 2 4.12.2017    Why two dates for rc2? Regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo

Re: [Development] New repository for WebGL Streaming QPA plugin

When i klick on this I camoe to a login page of gitlab. When trying to register I get 1 error prohibited this user from being saved: Email domain is not authorized for sign-up   I tried that with gmx.de and siemens.com   Regards, Gunnar Roth Gesendet: Mittwoch, 05. April 2017 um

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

win32-msvc2008 24.01.2017 17:37 win32-msvc2010 24.01.2017 17:37 win32-msvc2012 24.01.2017 17:37 win32-msvc2013 24.01.2017 17:37 win32-msvc2015 24.01.2017 17:37 win32-msvc2017 So there is lot of unsupported msvc versions (2005,2008,2010,2012), but no win32-msvc mkspec. Regards, Gunnar Roth. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

nary compatibility bewegen cl19.00 and cl cl19.xx instead on making a win32-msvc2017? mkspec should be based on the cl major version , instead of the IDE year. QtCreator complains when you try to use a qt with 2017 mkspec and a 2015 compiler set. Regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Announce] Qt 5.8.0 and Qt Creator 4.2.1 released

>> > > No. There will be a 5.6.2, but not another 5.7.x. Well, there IS already a 5.6.2 version. Regals, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] invokeMethod() with function pointers

ng "QThread::currentThread() == this“ should make the method more dangerous, actually it makes it a bit more safe for the same thread case, the potential deadlock problem remains with or without. Regards, Gunnar Roth ___ Development mailing

Re: [Development] git 5.8.0 build failure with vs 2017 rc error C3615: constexpr function 'QAlgorithmsPrivate::qt_builtin_ctz' cannot result in a constant exp ression

keyboard -f i get it it, but also message that the other folder are removed. doing perl init-repository -f again. But how is it supposed to work? How do I get the code which will become the release candidate? Do I need to wait for a label? Regards, Gunnar Roth ___

Re: [Development] git 5.8.0 build failure with vs 2017 rc error C3615: constexpr function 'QAlgorithmsPrivate::qt_builtin_ctz' cannot result in a constant exp ression

> Am 05.12.2016 um 20:07 schrieb Thiago Macieira : > > Em segunda-feira, 5 de dezembro de 2016, às 15:42:25 PST, Gunnar Roth > escreveu: >> Hello, >> My try to build qt 5.8.0 from git using vs2017 rc (CL 19.10.24629) failed >> already wh

Re: [Development] git 5.8.0 build failure with vs 2017 rc error C3615: constexpr function 'QAlgorithmsPrivate::qt_builtin_ctz' cannot result in a constant exp ression

Ok thank you Friedeman, so  $ cd qt5 $ perl init-repository $ git checkout 5.8.0 $ git submodule update is not the correct way to get latest 5.8.0 from git?   But what is the correct way then?   Regards, Gunnar Roth     Gesendet: Montag, 05. Dezember 2016 um 16:35 Uhr Von

[Development] git 5.8.0 build failure with vs 2017 rc error C3615: constexpr function 'QAlgorithmsPrivate::qt_builtin_ctz' cannot result in a constant exp ression

relib/tools/qalgorithms.h(657): note: failure was caused by an illegal statement or _expression_ jom: C:\bldqt\5.8.0\WIN32-VS14-64\qtbase\tools\configure\Makefile [configure_pch.pch] Error 2   Regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] std::atomic

says it is missing main().   Btw using  19.10.24516 angle does no longer crash for me in qt 5.7.0   Regards, Gunnar Roth   Gesendet: Freitag, 21. Oktober 2016 um 00:37 Uhr Von: "Henry Skoglund" An: development@qt-project.org Cc: thiago.macie...@intel.com Betreff: Re: [Development]

Re: [Development] Which changes are suitable for 5.6?

Hi Thiago, thanks for you answers. > Am 13.08.2016 um 20:05 schrieb Thiago Macieira : > > On sábado, 13 de agosto de 2016 18:08:16 PDT Gunnar Roth wrote: >> 1. category is just adding code, which does not influence current >> code. >> a. adding qAsConst in qgolbal.h.

Re: [Development] Which changes are suitable for 5.6?

actually I don’t see a dragon but maybe a dwarf lizard there ;-) I can send the actual patches on request, they do not contain any code I wrote myself ( other than changing numbers) Regards, Gunnar Roth > Am 12.08.2016 um 18:26 schrieb Thiago Macieira : > > On sexta-feira, 12 de

Re: [Development] Which changes are suitable for 5.6?

Does a request of  having qtquickcontrols2 and qtvirtualkeyboard 2.1 backported to 5.6. x have chance? Actually I managed to do this myself, but an upstream solutuion is preferrable. The problem is that some important OS is no longer supported in 5.7.   Regards, Gunnar     Gesendet: Freita

Re: [Development] Dropping VS 2012 in Qt 5.7

n. there is choice between qt provided sqlite and system provided sqlite, but for wince and windows there is no such a thing like system provided sqlite. Regards, Gunnar roth Am 01.03.2016 um 14:50 schrieb Gunnar Roth: > > Well so be it, goodbye Qt from wec2013 Users. > But who takes

Re: [Development] debug symbols for official Qt releases

se, i have no real problem with the current state, but would still be glad if pdb for release are build and delivered with the enhanced pdb option. Regards, Gunnar Roth     ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Dropping VS 2012 in Qt 5.7

ry[ "SSE4_1" ] = "no"; -dictionary[ "SSE4_2" ] = "no"; -dictionary[ "AVX" ] = "no"; -dictionary[ "AVX2" ]= "no"; diction

Re: [Development] Supported platforms for Qt 5.8

Hi, I also like to add that Win10 IoT is NOT THE successor for wec2013. MS will offer some porting tools, but as you can see here http://embeddingwindowssuccess.blogspot.de/2015/03/the-future-of-windows-embedded-windows.html

Re: [Development] Supported platforms for Qt 5.8

webkit/engine support  and no multimedia support, no neon intrinsics support, no openssl support, no sse2 support.   Regards, Gunnar Roth   Gesendet: Montag, 22. Februar 2016 um 17:01 Uhr Von: "Andrew Knight" An: development@qt-project.org Betreff: Re: [Development] Supported platfo

Re: [Development] QStringLiteral vs QLatin1String , foreach vs for range

t neon for wec2013. Qt does not even support sse2 for wec because configureap.cpp does always reset sse2 to no, even if i pass it to configure. Same as the openssl problem, which was solved in dev branch. https://codereview.qt-project.org/#/c/122437/   Regards Gunnar Roth Gesendet: Montag,

Re: [Development] QStringLiteral vs QLatin1String , foreach vs for range

Hi, thanks for answering, but > Am 17.01.2016 um 20:36 schrieb Thiago Macieira : > > On Sunday 17 January 2016 19:13:44 Gunnar Roth wrote: >> Hi, >> I saw quite some changes like https://codereview.qt-project.org/#/c/145961/ >> <https://codereview.qt-pro

[Development] QStringLiteral vs QLatin1String , foreach vs for range

these changes ? There is also a lot of replacing foreach with range for loops? What is the idea behind this? Any links to read? Regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/li

Re: [Development] wec2013 build fails with qt 5.6 beta in dbus.

Sorry but 1. -no-dbus is sufficient for me. 2. i am on leave now and will return to work not before Epiphany <https://www.dict.cc/englisch-deutsch/Epiphany.html>. Regards, Gunnar > Am 22.12.2015 um 18:07 schrieb Bornemann Joerg > : > > On Monday 21 December 2015 21:58:46

[Development] Solution for Build errors in Qt Commercial Charts module 2.1 in qt 5.6 beta

moc tells me Error: Undefined interface and he is right.   Charts\2.1\Src\charts\axis\polarchartaxis_p.h Charts\2.1\Src\charts\axis\cartesianchartaxis_p.h need #include   Charts\2.1\Src\charts\linechart\linechartitem_p.h Charts\2.1\Src\charts\splinechart\splinechartitem_p.h need #include

Re: [Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

c.exe showing dialog qt5core.dll cannot be found.     On Tue, Dec 22, 2015 at 1:43 AM, Gunnar Roth <gunnar.r...@gmx.de> wrote: Hello,   when i used jom i get this dialog with qt5core not found. When using nmake i get this error:     For what it's worth, I created a bug report

Re: [Development] wec2013 build fails with qt 5.6 beta in dbus.

hiago Macieira" An: development@qt-project.org Betreff: Re: [Development] wec2013 build fails with qt 5.6 beta in dbus. On Monday 21 December 2015 21:58:46 Gunnar Roth wrote: > How am I supposed know? It worked without that since 5.2.1. How should > anybody know that now -no-dbus is

Re: [Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

I found this change: --- a/qtbase/mkspecs/features/qt_functions.prf +++ a/qtbase/mkspecs/features/qt_functions.prf   # variable, default, [suffix for variable for system() use], [prepare primary variable for system() use]  defineTest(qtPrepareTool) {      cmd = $$eval(QT_TOOL.$${2}.binary) @@ -

Re: [Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

s not the problem. wec2013 works > because there uic.exe and qlarl.exe are build statically. seems that i'm not hallucinating then: https://codereview.qt-project.org/#/c/144550/ > Regards, > Gunnar > > *Gesendet:* Dienstag, 22. Dezember 2015 um 10:43 Uhr > *Von:* "Gunna

Re: [Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

.exe are build statically.   Regards, Gunnar   Gesendet: Dienstag, 22. Dezember 2015 um 10:43 Uhr Von: "Gunnar Roth" An: "development@qt-project.org" Betreff: [Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

[Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

Hello,   when i used jom i get this dialog with qt5core not found. When using nmake i get this error:         (set QT_PLUGIN_PATH=D:\TFS\bld__GLOBAL\Qt5.6.0\WIN32-VS11-32\qtbase\plugins) & (set PATH=D:\TFS\bld__GLOBAL\Qt5.6.0\WIN32-VS11-32\qtbase\bin;%PATH:)=^)% ) & D:\TFS\bld__GLOBAL\Qt5.6.0\W

Re: [Development] wec2013 build fails with qt 5.6 beta in dbus.

d workaround is > a carefully placed #undef interface. Would you be able to tell us where the > conflict happened or maybe even make a patch? (see qtnetwork for a similar > #undef) > > > Simon > > From: Gunnar Roth > Sent: Monday, December 21, 2015 17:44 >

Re: [Development] wec2013 build fails with qt 5.6 beta in dbus.

Hi Thiago, > Am 21.12.2015 um 19:46 schrieb Thiago Macieira : > > On Monday 21 December 2015 17:44:19 Gunnar Roth wrote: >> Hi, >> the problem is that dbus is set to runtime instead of no for windows from >> configure when no dbus support is found. So it is being tried

[Development] wec2013 build fails with qt 5.6 beta in dbus.

Hi, the problem is that dbus is set to runtime instead of no for windows from configure when no dbus support is found. So it is being tried to build it, which fails, mostly due to using 'interface' as identifier, which seems to be a define somewhere in the wec2013 headers. I wil add -no-dbus to m

Re: [Development] QT_NO_DRAGANDDROP qt 5.6 git build fails

this mail.   Regards, Gunnar Roth Gesendet: Mittwoch, 02. September 2015 um 16:06 Uhr Von: "Samuel Gaist" An: "Giuseppe D'Angelo" Cc: development@qt-project.org Betreff: Re: [Development] QT_NO_DRAGANDDROP qt 5.6 git build fails On 2 sept. 2015, at 15:35, Giuseppe

[Development] gerrit https acess error

t.org/p/qt/qtbase/': The requested URL returned error: 403   I used the http passwort generated in the gerrit webinterface.     What can i do?   Regards, Gunnar Roth   ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QT_NO_DRAGANDDROP qt 5.6 git build fails

there because of #ifndef QT_NO_DRAGANDDROP  around the function not inside as in QGraphicsView same problem in  qtreewidget.h and qtableview.h   If you wonder why i need that, its because of wc2013 it has no DnD support ( as wec7 had).   Regards, Gunnar Roth     Gesendet: Mittwoch, 02. September 2015

[Development] QT_NO_DRAGANDDROP qt 5.6 git build fails

Hello, QT_NO_DRAGANDDROP qt defines to adapt qt at compile time is a nice feature. Q_DECL_OVERRIDE is also somwehat nice.   But together they lead to build errors. void QGraphicsView::dragEnterEvent(QDragEnterEvent *event) { #ifndef QT_NO_DRAGANDDROP       void dragEnterEvent(QDragEnterEven

Re: [Development] quickcontrols2 how to build?

Hi Thiago Yes i did checkout from git, but copied it to another location without the .git dir. Creating an empty .git dir helped to solve the problem. Thank you, Gunnar Roth   Gesendet: Dienstag, 25. August 2015 um 08:08 Uhr Von: "Thiago Macieira" An: development@qt-project.org B

[Development] quickcontrols2 how to build?

with syncqt not being run but i have no clue how to do this. So what is the right procedure to build this? Regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Found wince info in Gerrit ,which makes me panic

or all CE versions , wec2013 too. To differentiate between CE versions the _WIN32_WCE macro value is used also for wec2013, which happens to be 0x800, while for WEC7 is is 0x700 , so internally wec2013 is WEC8. Regards, Gunnar Roth ___ Development mailin

Re: [Development] status of exception handling on windows and mdvc compiler

Hi Jörg. > Am 07.08.2015 um 23:33 schrieb Joerg Bornemann > : > > On 07-Aug-15 15:30, Gunnar Roth wrote: > >> i accidentally stumbled over this: >> https://codereview.qt-project.org/#/c/122584/ >> >> MSVC2015: Disable warning C4577 ('noexcept' u

[Development] status of exception handling on windows and mdvc compiler

n-vs-2015-zc-throwingnew.aspx> and this arises the qustion how am i supposed to add my own option? making my own mkspec? Thanks in advance for your answers. Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Found wince info in Gerrit ,which makes me panic

And I read this thread.actually I wrote quite some messages in that. Seems not to be The case for qt company employees. Am 31.07.2015 20:21 schrieb Thiago Macieira : > > On Friday 31 July 2015 18:40:02 Gunnar Roth wrote: > > Hi. > > I found https://codereview.qt-proj

Re: [Development] Found wince info in Gerrit ,which makes me panic

I am not talking about winrt AS this RT does not mean realtime, fair enough. BUT i am talking about wince,thought I made that clear. Am 31.07.2015 20:21 schrieb Thiago Macieira : > > On Friday 31 July 2015 18:40:02 Gunnar Roth wrote: > > Hi. > > I found https://codereview.

[Development] Found wince info in Gerrit ,which makes me panic

around much longer. Iwould also like to know why qtserialbus is not supported in MS realtime system. Regards Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] wince and openssl

015 um 18:17 Uhr Von: "Andreas Holzammer" An: development@qt-project.org Betreff: Re: [Development] wince and openssl Am 29.07.2015 um 18:04 schrieb Andrew Knight: > Hi, > > On 07/29/2015 06:49 PM, Gunnar Roth wrote: >> Hi, >> i am trying to make a wec2013 build wi

Re: [Development] QtWebEngine and VS 2015

uot;"" 4. ifos.environ['GYP_MSVS_VERSION']=='2013': 5. return'120' 6. elifos.environ['GYP_MSVS_VERSION']=='2015': 7. return'140' 8. else: 9. raiseValueError('Unexpected GYP_MSVS_VERSION') Regards, Gunnar Am 30.07.2015 um

[Development] QtWebEngine and VS 2015

exe" -D gperf_exe="gper f.exe" --no-parallel -D qt_gl="opengl" -D disable_nacl=1 -D remoting=0 -D use_ash=0 -D disable_glibcxx_debug=1 -D remove _webcore_debug_symbols=1 -D win_release_extra_cflags=-Zi -D target_arch=x64... Project ERROR: --

Re: [Development] wince and openssl

think arm when thinking about wince. So you also disable -sse2 flag to configure when i compile for a intel or and wec2013 platform. At least i know about this this now. When compiling crossplatform you should trust the configure parameters. Regards Gunnar Roth > Am 29.07.2015 um 18:46 schr

[Development] wince and openssl

  dictionary["OPENSSL"] = checkAvailability("OPENSSL") ? "yes" : "no";             dictionary["SSL"] = dictionary["OPENSSL"];         }     }     and i found that the default is:   dictionary[ "SSL" ]             = "

Re: [Development] QVector now has rvalue push_back

ject.org Betreff: Re: [Development] QVector now has rvalue push_back On Wednesday 22 July 2015 09:09:50 Julien Blanc wrote: > Le mardi 21 juillet 2015 à 19:00 +0200, Gunnar Roth a écrit : > > Hello, > > Out of curiosity i just looked at the Xcode 6.4 headers for the > > implementatio

Re: [Development] QVector now has rvalue push_back (was: Re: HEADS UP: potential trouble from a recent QVector change)

> Am 21.07.2015 um 20:11 schrieb Bubke Marco : > > > Gunnar Roth >>> >>> void push_back(T &&t) { >>> ensureCapacity(size() + 1); >>> new (m_end) T(std::move(t));// move-construct from t >>>

Re: [Development] QVector now has rvalue push_back (was: Re: HEADS UP: potential trouble from a recent QVector change)

> Am 21.07.2015 um 19:58 schrieb Milian Wolff : > > On Tuesday 21 July 2015 19:49:13 Gunnar Roth wrote: >>> void push_back(T &&t) { >>> >>> ensureCapacity(size() + 1); >>> new (m_end) T(std::move(t));//

Re: [Development] xcode emplace_back (was: QVector now has rvalue push_back)

> Am 21.07.2015 um 19:14 schrieb Matthew Woehlke : > > Ergo, that implementation looks... suspicious, and *may* even be > non-conforming. (Unless push_back is doing something really funky, which > I somewhat doubt.) You may want to file a bug against that implementation. this is the push_back imp

Re: [Development] Qt LTS & C++11 plans (CopperSpice)

Hi Ansel. > Am 21.07.2015 um 19:06 schrieb Ansel Sermersheim : > > gives the Qt Project the freedom to take any and all submissions and > incorporate them into the closed source version Do not mix up commercial license with closed source, all code you contribute will be licensed under GPL,LGPL

Re: [Development] QVector now has rvalue push_back (was: Re: HEADS UP: potential trouble from a recent QVector change)

n r-value ref. Regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QVector now has rvalue push_back

Hello, Out of curiosity i just looked at the Xcode 6.4 headers for the implementation of std::vector::emplace_back, and i don’t think there is any difference between push_back(QPen(Qt::red,1.5f)) and emplace_back(Qt::red,1,5f)) The implementation is like this: template _LIBCPP_INLINE_VI

Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

Hi Julian > Am 16.07.2015 um 23:43 schrieb Julien Blanc : > > Le jeudi 16 juillet 2015 à 23:09 +0200, Gunnar Roth a écrit : > >> >> The vector classes are now very bad in this case. QHash is considerable >> better than any other. >> >> So I deduce f

Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

mentary beginnings of an open- > addressing hash container (a hash container using consecutive memory, not > nodes). > What was the idea behind it? Is so much slower than any other that I can just see why anyone should want to have this? What is the advantage? > > QHash is slowe

Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

Hi Thiago > Am 12.07.2015 um 19:42 schrieb Thiago Macieira : > > On Sunday 12 July 2015 16:57:39 Gunnar Roth wrote: >> "QMap_insert -- 1 ","WalltimeMilliseconds",0.625,80,128 > > Please run with -perf -minimumvalue 100. The CPU cy

Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

Hi Milian, hi Marc > Am 12.07.2015 um 16:06 schrieb Milian Wolff : > > On Sunday, July 12, 2015 04:58:01 PM Marc Mutz wrote: >> On Sunday 12 July 2015 15:05:51 Gunnar Roth wrote: >>> Hi Marc, >>> >>>> Better provide a benchmark into which users

Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

enchmark measure wrong? Because if you are right in saying QVector should be the default associative container, then my benchmark must be wrong. Best regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Move ctors for q_declare_shared types

Hi Marc Gesendet: Freitag, 26. Juni 2015 um 17:25 Uhr Von: "Marc Mutz" An: development@qt-project.org Betreff: Re: [Development] Move ctors for q_declare_shared types   Marc are you from the future ? Or is just your  clock wrong ?   >> According to the fundamental C++ > > principle "Don't p

Re: [Development] QtCS: Long Term Release discussion

Yes thats wrong, proved by practice and ms support finally. This arcticle will be changed as MS promised that to us, but until this task bubbles up inside MS  can take a while.   Regards, Gunnar     Gesendet: Montag, 22. Juni 2015 um 15:02 Uhr Von: "Al-Khanji Louai" An: &q

Re: [Development] QtCS: Long Term Release discussion

> Am 19.06.2015 um 18:38 schrieb Knoll Lars : > > > There was never an intention to remove it after 5.6. But I was hoping that we > could be using VC++ 2013 (and support wec2013 with it). Looks like that is > unfortunately not the case. That implies that our new compiler baseline will > stay

Re: [Development] QtCS: Long Term Release discussion

Hi Björn, i am really glad this discussion will come to an end ;-), it already took considerable time, internally and externally. > Am 19.06.2015 um 17:51 schrieb Björn Breitmeyer : > > Hi Gunnar, > > sadly i have to agree. I finally had the time to setup a Visual Studio 2013 > with the recent

Re: [Development] QtCS: Long Term Release discussion

sufficient c99 support. But that is not supported and c++ relies heavily on its stdc++ lib where we dont have a fitting version.   Regards, Gunnar       Gesendet: Donnerstag, 18. Juni 2015 um 11:48 Uhr Von: "Björn Breitmeyer" An: "Gunnar Roth" Cc: development@qt-project.o

Re: [Development] QtCS: Long Term Release discussion

on: "Björn Breitmeyer" An: development@qt-project.org Cc: "Gunnar Roth" , "Thiago Macieira" Betreff: Re: [Development] QtCS: Long Term Release discussion Hello Gunnar, i still hadn't time to verify this, but. There is a platform builder for WEC2013, if you gene

Re: [Development] QtCS: Long Term Release discussion

    Gesendet: Donnerstag, 18. Juni 2015 um 08:43 Uhr Von: "Thiago Macieira" An: development@qt-project.org Betreff: Re: [Development] QtCS: Long Term Release discussion On Thursday 18 June 2015 08:23:52 Gunnar Roth wrote: > > Am 17.06.2015 um 22:35 schrieb Thiago Macieira &

Re: [Development] QtCS: Long Term Release discussion

ect.org" Betreff: Re: [Development] QtCS: Long Term Release discussion > On Thursday 18 June 2015 08:23:52 Gunnar Roth wrote: > > > Am 17.06.2015 um 22:35 schrieb Thiago Macieira > > > : > > > > > > On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote: &g

Re: [Development] QtCS: Long Term Release discussion

> Am 17.06.2015 um 22:35 schrieb Thiago Macieira : > > On Wednesday 17 June 2015 19:30:25 Gunnar Roth wrote: >> Yes that would make us (as a commercial user using a self made port of qt >> 5.4.1 to wec2013 ) very unhappy. This means 5.6 will be the last version >> wec

Re: [Development] QtCS: Notes from Modern C++ session

> Am 16.06.2015 um 22:49 schrieb Ziller Eike : > > >> On Jun 16, 2015, at 16:52, Matthew Woehlke >> wrote: >> >> On 2015-06-12 17:45, Thiago Macieira wrote: >>> On Friday 12 June 2015 10:49:38 Matthew Woehlke wrote: > On Friday 12 June 2015 08:08:51 André Somers wrote: >> Not availabl

Re: [Development] QtCS: Long Term Release discussion

Hello Lars, > Am 17.06.2015 um 12:27 schrieb Knoll Lars : > > * We make Qt 5.6 an LTS release > * We could then have both WEC7 and WEC2013 (on VS2012) supported on 5.6. > This would solve all problems for Windows Embedded and we could make > VS2013 the compiler baseline for 5.7. > we’d keep peopl

Re: [Development] QtCS: Notes from Modern C++ session

> Not available for use are: * = default, * = deleted, >> >> Where are these not supported? I have code that (AFAIK) has been using >> these already, and IIRC our compiler requirements are lower. > > GCC requires 4.7 for this. I think we were discussing whether our minimum is >

Re: [Development] Problem with embedded fonts

> > > And why don't we hear about this problem more often? Strange. > Everytime i have a programming or computer problem, which nobody else has, where you can’t find next to nothing or really nothing on the internet, its because i did some very foolish thing ;-) Regards, Gunnar _

Re: [Development] Building Modules

Looks like you removed the directory AFTER configure. But you should remove it before. Regards, Gunnar > Am 22.04.2015 um 13:44 schrieb rpzrpz...@gmail.com: > > > Thiago: > > Unfortunately, your suggestion of removing the directory and/or its > contents did not yield a positive result. > > Ho

Re: [Development] git://code.qt.io availability

Hi >> + git config remote.origin.url https://code.qt.io/cgit/qt/qt3d.git >> >this definitely doesn't look right (the git repos are not served under >cgit/, at least not intentionally). fix the remote of qt5.git and retry.   Without cgit it does not work for https last time i tried. See my mail fr

Re: [Development] git://code.qt.io availability

Hi, i try to ge update from git but get this error. i dit git pull and after that id do: D:\git\qt5>perl init-repository -f + git submodule init qt3d qtactiveqt qtandroidextras qtbase qtcanvas3d qtconnectivity qtdeclarative qtdoc qtenginio qtgraphicaleffects qtimageformats qtlocation  qtmacextr

Re: [Development] "Add tests for detach on setDevicePixelRatio()" commits in qtbase

Sorry somehow i clicked on the wrong mail to answer.   Gesendet: Mittwoch, 08. April 2015 um 12:55 Uhr Von: "Gunnar Roth" An: "Oswald Buddenhagen" Cc: development@qt-project.org Betreff: Re: [Development] "Add tests for detach on setDevicePixelRatio()" commits

Re: [Development] "Add tests for detach on setDevicePixelRatio()" commits in qtbase

Hi, i try to ge update from git but get this error. i dit git pull and after that id do: D:\git\qt5>perl init-repository -f + git submodule init qt3d qtactiveqt qtandroidextras qtbase qtcanvas3d qtconnectivity qtdeclarative qtdoc qtenginio qtgraphicaleffects qtimageformats qtlocation  qtmacextr

Re: [Development] quickcontrols has now a hard dependancy on widgets.

+ //#include #ifndef UiaRootObjectId #define UiaRootObjectId-25 #endif  Regards, Gunnar Roth Gesendet: Mittwoch, 17. Dezember 2014 um 14:02 Uhr Von: "deDietrich Gabriel" An: "development@qt-project.org" Cc: "Gunnar Roth" , "gun...@sletta.org"

Re: [Development] Switching remote url for qt5 git clone

Now wiki says  git clone git://code.qt.io/qt/qt5.git But i am quite sure it must be  git clone git://code.qt.io/cgit/qt/qt5.git Because otherwise i got an error: fatal: repository 'https://code.qt.io/qt/qt5.git/' not found Regards, Gunnar Roth Gesendet: Dienstag, 31. März 2015 um

Re: [Development] msvc warning policy in qt

and all is well again. just to let you know... Regards, Gunnar Roth Gesendet: Montag, 09. März 2015 um 10:08 Uhr Von: "Gunnar Roth" An: "development@qt-project.org" Betreff: [Development] msvc warning policy in qt Hello, we have an in-house policy to use warning lev

[Development] msvc warning policy in qt

* C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc */   additionally i found  include\QtCore\qfunctions_wince.h(224):#pragma warning(disable: 4273)    which disables the warning 'function' : inconsistent DLL linkage'  Two definitions

Re: [Development] license question, bds 4 clause license text in qtbase\src\corelib\tools\qdatetime.cpp qt5.4.1 found

hoped for initially. Thanks for reading, Gunnar Roth. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] license question, bds 4 clause license text in qtbase\src\corelib\tools\qdatetime.cpp qt5.4.1 found

> Am 28.02.2015 um 08:10 schrieb Sune Vuorela : > >> Well https://www.gnu.org/licenses/license-list.en.html says >> Original BSD license (#OriginalBSD) >> This license is also sometimes called the “4-clause BSD license”. >> >> This is a lax, permissive non-copyleft free software license with a s

Re: [Development] license question, bds 4 clause license text in qtbase\src\corelib\tools\qdatetime.cpp qt5.4.1 found

rety. But does the week number code fall under the category BSD Unix files ? So who is right her? GNU.org, Thiago ? I am not a lawyer( thank god :-) ) or judge to decide this. Regards, Gunnar Roth > Yours, > >Tuukka > > _

Re: [Development] license question, bds 4 clause license text in qtbase\src\corelib\tools\qdatetime.cpp qt5.4.1 found

Hi Thiago > >> the requirement to document this is also more than qt company tells >> commercial customers. they they if you use modules which are under >> commrcial license as qtcore pretends to be, you can be silent about >> anything used in there. > > There's a page in the Qt documentation t

Re: [Development] license question, bds 4 clause license text in qtbase\src\corelib\tools\qdatetime.cpp qt5.4.1 found

ira : > > On Friday 27 February 2015 08:40:21 Gunnar Roth wrote: >> is the so called adevrtising clause which is know to not be kompatible with >> GPL or LPGL, so how can it be that i find this kind of license in qt source >> code? What are the obligations to follow when using c

Re: [Development] QtCore missing check for memory allocation

Hi, >  in fact both C++11 and C++14 have improved the ways in which the new/delete > operators can be overridden. can you give me some links describing these improvements? regards, Gunnar Roth   ___ Development mailing list Development@qt-proje

[Development] license question, bds 4 clause license text in qtbase\src\corelib\tools\qdatetime.cpp qt5.4.1 found

    by the University of California, Berkeley.  is the so called adevrtising clause which is know to not be kompatible with GPL or LPGL, so how can it be that i find this kind of license in qt source code? What are the obligations to follow when using commercial license?   Regards, G

Re: [Development] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.

    Gesendet: Dienstag, 24. Februar 2015 um 18:56 Uhr Von: "Thiago Macieira" An: development@qt-project.org Betreff: Re: [Development] trying to build qt 5.5 git branch. Missing qtbase\include dir and content. On Tuesday 24 February 2015 07:42:16 Gunnar Roth wrote: > Hello, > i am

Re: [Development] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.

base\include\QtXml  but does not exist.   i also see now that this is Qt5BootstrapRTIL which is being build.   but still got no clue whats wrong actually.   Regards, Gunnar       Gesendet: Dienstag, 24. Februar 2015 um 10:34 Uhr Von: "Gunnar Roth" An: "Konstantin Ritt"

Re: [Development] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.

-debug-and-release -rtti -force-debug-info -mp -ltcg -qtlibinfix RTIL -opensource -confirm-license -nomake examples -nomake tests -system-libjpeg -opengl dynamic -directwrite -direct2d     Regards, Gunnar Gesendet: Dienstag, 24. Februar 2015 um 09:56 Uhr Von: "Konstantin Ritt" A

[Development] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.

\include but this is completely missing in the git src code. what do i need to do to create the source code in a form like it is in released tar.gz files?   Thank you in advance, Gunnar Roth   ___ Development mailing list Development@qt-project.org http

Re: [Development] Item creation time in QML

in all it was a good start. we get involved with dig again with our results but … we will see. Best regards, Gunnar Roth > Am 12.02.2015 um 19:25 schrieb Gunnar Sletta : > > >> On 12 Feb 2015, at 18:03, Gunnar Roth wrote: >> >> Hi, >> after downloading i

Re: [Development] Item creation time in QML

rk! Best regards, Gunnar Roth Gesendet: Donnerstag, 12. Februar 2015 um 11:56 Uhr Von: "Robin Burchell" An: "Rutledge Shawn" Cc: "development@qt-project.org" Betreff: Re: [Development] Item creation time in QML On Wed, Feb 11, 2015 at 2:49 PM, Rutledge Shawn wrote:

Re: [Development] Deprecating modules with 5.5

> Am 08.02.2015 um 21:25 schrieb Olivier Goffart : > > On Sunday 08 February 2015 19:15:18 Giuseppe D'Angelo wrote: >> Il 08/02/2015 17:58, Thiago Macieira ha scritto: >>> So we come back to this question again and again: if you can't upgrade the >>> OS and upgrade the compiler, why do you want t

[Development] Qt 5.4 breaks binary compatibility on windows for builds using vs2010 and above

Hi, ms compiler uses access property of class methods for building the mangled name, so you should not change this between versions.   In Qt\5.4.0\qt-src\qtbase\src\corelib\kernel\qmetatype.h:643 you find   this code #ifndef Q_NO_TEMPLATE_FRIENDS #ifndef Q_QDOC     template     friend bool qRe

  1   2   >