Re: [Development] CI problems

2015-07-03 Thread Simon Hausmann
On Thursday, July 02, 2015 10:46:15 AM Marc Mutz wrote: On Wednesday 01 July 2015 11:59:58 Simon Hausmann wrote: Hi, We are currently experiencing severe connectivity issues in our CI infrastructure. As a result integrations staged in Gerrit are likely to fail, hang or - in the worst

Re: [Development] CI problems

2015-07-03 Thread Simon Hausmann
On Friday, July 03, 2015 03:51:28 PM Simon Hausmann wrote: [...] Brief update: The network connectivity issues seem to be resolved and we're also a little closer to resolving the issue with crashing ESX servers. We're doing some more testing now about that. Regarding the Jenkins based CI

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

2015-07-03 Thread charleyb123 .
snip, shared pointers Bo Thorsen sayeth: This answer is going to be one big IMHO. Anything that stops people from throwing shared pointers all over the code is A Good Thing. As someone once said: Shared pointers are a solution in search of a problem. Scoped pointers are fine, but

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

2015-07-03 Thread Thiago Macieira
On Friday 03 July 2015 09:42:54 Milian Wolff wrote: The above statement is far to broad to leave it uncommented. First, and foremost, the only place where Qt does not play nicely with smart pointers are QObject-inherited classes. This is true, but at the same time not a big deal as its

[Development] MSVC2015 and Qt5.5 -- dot release plans?

2015-07-03 Thread charleyb123 .
Microsoft announced MSVS2015 will be released on July 20: http://www.zdnet.com/article/microsoft-sets-release-date-for-visual-studio-2015/ Those of us that have been following the MS compiler know that the MSVC2015 is a particularly strong compiler, making up for lots of lost-ground in

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

2015-07-03 Thread Simon Hausmann
On Monday, June 29, 2015 10:51:25 PM Ansel Sermersheim wrote: There is always CopperSpice the Qt fork which uses C++11. They've got rid of moc and plan to replace Qt containers with std ones. Afterwards maybe they will add support for namespaces to their peppermill source convertor

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

2015-07-03 Thread Bo Thorsen
Den 03-07-2015 kl. 07:09 skrev Ansel Sermersheim: On 7/2/15 2:23 PM, Milian Wolff wrote: On Thursday 02 July 2015 23:00:43 Bernhard wrote: Unfortunately adding signals of the template’s type is exactly what I would have needed several times. In that case there is no clean solution. I once

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

2015-07-03 Thread Thiago Macieira
On Thursday 02 July 2015 22:09:13 Ansel Sermersheim wrote: Yes, you can use C++11 in your application. Our viewpoint is that Qt developers should be able to use C++11 internally in the project. They are slated to allow most of C++11 like decltype, rvalue references, and lambdas in 2016.

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

2015-07-03 Thread Milian Wolff
On Thursday, July 02, 2015 10:09:13 PM Ansel Sermersheim wrote: On 7/2/15 2:23 PM, Milian Wolff wrote: On Thursday 02 July 2015 23:00:43 Bernhard wrote: Unfortunately adding signals of the template’s type is exactly what I would have needed several times. In that case there is no clean

[Development] Relevant industrial buses

2015-07-03 Thread Turunen Tuukka
Hi, As you are probably aware, we are developing a new Qt SerialBus module. Target is to have a technology preview in Qt 5.6 with support to CANBus. You can look how it is shaping up at: http://code.qt.io/cgit/qt/qtserialbus.git/ The architecture of the new Qt SerialBus is modular, and we