I couldn’t agree more with Roland's concerns here.

I am stuck on Qt 5.5 because of the QWebKit debacle....

I am finally moving on to VS 2017 + a newer GCC, that I can consistently build 
QWebKit with only minor mods to the build-webkit script.  But we build all our 
code with Wall and warnings as errors.

It’s a 4-6 week project to move code to a different compiler... Some of the 
warnings are valid, and surprising.. Some are overly pedantic, and a pain.. But 
we have to verify code changes don’t introduce new issues...

While I understand the "want" to move to a new compiler.. and I do love many of 
the modern c++ advantages.  For a core library such as Qt to FORCE a new 
compiler, leaves many stuck on older versions

Scott

-----Original Message-----
From: Interest <[email protected]> On Behalf Of 
[email protected]
Sent: Tuesday, November 27, 2018 14:59
To: Filip Piechocki <[email protected]>
Cc: [email protected]
Subject: Re: [Interest] Interest Digest, Vol 86, Issue 14


Quoting Filip Piechocki <[email protected]>:

> I don't understand it. This new compiler is needed to build QtC on 
> Ubuntu 14.04. You said, that you can have whatever editor you want, 
> but cannot use anything that changes the product. But wait, this new 
> GCC will be used to build the QtC, not the product. Or maybe Ubuntu 
> 14.04 system image is your product? Or am I missing something here...
>
> Filip
Quoting Filip Piechocki <[email protected]>:
>>>
>> Yes, that would increase your personal effort to get this Creator 
>> from 2018 on Ubuntu 14.04 working, but that effort is dwarfed by the 
>> effort you spent on your messages here, so that hardly can be the 
>> limiting factor in the game.
>>
>> Andre'

Andre',

This is not about effort or great need. I'm shocked so many people cannot 
fathom working in an environment where you are not allowed to change out the 
C/C++ compiler willy-nilly. Gospel truth, I completed what I needed to do on 
14.04 for the next weeks. I used Sublime Text 3 like I said I would. Other than 
when I'm at home working on my own stuff, over the course of my 30+ years in 
IT, I do not recall being in a work environment where I was allowed to change 
the C/C++ compiler out at will. Even if it is/was/might be allowed here, 
changing the compiler out just to get an editor would be an extreme risk. It 
could potentially undo tons of work which has already went into 
creating/testing the Debian and ISO construction worlds as well as the 
multi-platform deployment testing.

Filip,

Unknown. If that PPA was/is a backport which installs a new compiler over the 
top of the existing system compiler, then yeah, the wheels are off the cart. If 
that PPA installs off in some obscure corner where QtCreator wouldn't 
automagically find it while configuring kits and projects, __maybe__ it's okay. 
Assuming nothing got put into a standard search path where it accidentally got 
picked up.

Be off-line for a bit. Other team has release going live tomorrow morning then 
my stuff starts churning through the system.
--
Roland Hughes, President
Logikal Solutions
(630) 205-1593

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
http://lesedi.us

_______________________________________________
Interest mailing list
[email protected]
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
[email protected]
https://lists.qt-project.org/listinfo/interest

Reply via email to