On Thu, Jun 18, 2015 at 11:48 PM, Simon Hausmann
wrote:
> On Thursday, June 11, 2015 02:21:22 AM Stottlemyer, Brett wrote:
>> Hi Alan. Hi Simon.
>>
>> On 6/10/15, 4:23 PM, "Alan Alpert" <4163654...@gmail.com> wrote:
>> >On Wed, Jun 10, 2015 at 6:52 AM, Simon Hausmann
>> >
>> > wrote:
>> >> On Tue
> 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
On 19/06/15 18:26,
"development-bounces+lars.knoll=theqtcompany@qt-project.org on behalf of
Gunnar Roth" wrote:
>
>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 B
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
Hi Gunnar,
sadly i have to agree. I finally had the time to setup a Visual Studio 2013
with the recent Platform Builder and sadly the generated SDK's still have
the Compiler Version 17.xx and says Visual Studio 2012. So the link indeed
gets us to wrong assumptions. It is a bit sad since there is
Hi,
I’m happy to announce that a work-in-progress port of Qt to the Chrome / Native
Client platform has now been pushed to the wip/nacl branch in QtBase. So far
development has been closed, but we are now ready to develop in the open and
also take contributions. My intention is to at some point
