[webkit-dev] Ports not building as C++11?

Osztrogonác Csaba oszi at inf.u-szeged.hu
Tue Jul 30 09:23:00 PDT 2013


On 07/26/2013 06:04 PM, Anders Carlsson wrote:
 > Hi everyone,
 > when Oliver landed his “let’s break everything” patches in JSC the 
other day, I noticed that some of the follow-up build fixes by other 
ports were removing use of C++11 features (mainly nullptr).
 > Are there any ports that aren’t building as C++11? If so, why not?
 > - Anders

No, I don't have objections. :) I absolutely support switching to c++11,
and I'm happy to add back the removed nullptrs and scoped enum values
_after_ all ports switched to c++11.

- cmake port did the switch by http://trac.webkit.org/changeset/153315
- GTK did the switch by http://trac.webkit.org/changeset/150445
- Qt and Win confirmed that they are going to do the switch, but I'm
not sure if they already did it or not. Let the EWS bots notice us. :)

Patch is coming soon in https://bugs.webkit.org/show_bug.cgi?id=119266

But I suprised how c++11 became mandatory. If you had announced it
before pushing the FTL patches, we would have easily avoid the tons of
buildfixes removing c++11 features.


More information about the webkit-dev mailing list