Changeset 88006 in webkit


Ignore:
Timestamp:
Jun 3, 2011 5:04:22 AM (13 years ago)
Author:
alexis.menard@openbossa.org
Message:

2011-06-03 Alexis Menard <alexis.menard@openbossa.org>

Reviewed by Benjamin Poulain.

[Qt] Build fix of QtWebKit 2.2 when inside Qt tree with GCC 4.6.
https://bugs.webkit.org/show_bug.cgi?id=61957

When building inside the Qt source tree, qmake always append the mkspecs
defines after ours. We have to workaround and make sure that we append
our flags after the qmake variable used inside Qt. This workaround was provided
by our qmake folks. We need to append in both case because qmake behave differently
when called with -spec or via SUBDIR+=.

  • Source/WebKit.pri:

2011-06-03 Alexis Menard <alexis.menard@openbossa.org>

Reviewed by Benjamin Poulain.

[Qt] Build fix of QtWebKit 2.2 when inside Qt tree with GCC 4.6.
https://bugs.webkit.org/show_bug.cgi?id=61957

When building inside the Qt source tree, qmake always append the mkspecs
defines after ours. We have to workaround and make sure that we append
our flags after the qmake variable used inside Qt. This workaround was provided
by our qmake folks. We need to append in both case because qmake behave differently
when called with -spec or via SUBDIR+=. This patch unbreak r87950 on Mac for Qt port.

Location:
trunk
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • trunk/ChangeLog

    r87950 r88006  
     12011-06-03  Alexis Menard  <alexis.menard@openbossa.org>
     2
     3        Reviewed by Benjamin Poulain.
     4
     5        [Qt] Build fix of QtWebKit 2.2 when inside Qt tree with GCC 4.6.
     6        https://bugs.webkit.org/show_bug.cgi?id=61957
     7
     8        When building inside the Qt source tree, qmake always append the mkspecs
     9        defines after ours. We have to workaround and make sure that we append
     10        our flags after the qmake variable used inside Qt. This workaround was provided
     11        by our qmake folks. We need to append in both case because qmake behave differently
     12        when called with -spec or via SUBDIR+=.
     13
     14        * Source/WebKit.pri:
     15
    1162011-06-02  Alexis Menard  <alexis.menard@openbossa.org>
    217
  • trunk/Source/JavaScriptCore/ChangeLog

    r87958 r88006  
     12011-06-03  Alexis Menard  <alexis.menard@openbossa.org>
     2
     3        Reviewed by Benjamin Poulain.
     4
     5        [Qt] Build fix of QtWebKit 2.2 when inside Qt tree with GCC 4.6.
     6        https://bugs.webkit.org/show_bug.cgi?id=61957
     7
     8        When building inside the Qt source tree, qmake always append the mkspecs
     9        defines after ours. We have to workaround and make sure that we append
     10        our flags after the qmake variable used inside Qt. This workaround was provided
     11        by our qmake folks. We need to append in both case because qmake behave differently
     12        when called with -spec or via SUBDIR+=. This patch unbreak r87950 on Mac for Qt port.
     13
     14        * JavaScriptCore.pro:
     15
    1162011-06-02  Jay Civelli  <jcivelli@chromium.org>
    217
  • trunk/Source/JavaScriptCore/JavaScriptCore.pro

    r87950 r88006  
    214214}
    215215
    216 lessThan(QT_GCC_MAJOR_VERSION, 5):lessThan(QT_GCC_MINOR_VERSION, 6) {
    217     # Disable C++0x mode in JSC for those who enabled it in their Qt's mkspec.
    218     *-g++* {
    219         CONFIG(QTDIR_build) {
    220             QMAKE_CFLAGS_WARN_ON = -Wno-c++0x-compat
    221             QMAKE_CXXFLAGS_WARN_ON = -Wno-c++0x-compat
    222         } else {
     216lessThan(QT_GCC_MAJOR_VERSION, 5) {
     217    # GCC 4.5 and before
     218    lessThan(QT_GCC_MINOR_VERSION, 6) {
     219        # Disable C++0x mode in JSC for those who enabled it in their Qt's mkspec.
     220        *-g++*:QMAKE_CXXFLAGS -= -std=c++0x -std=gnu++0x
     221    }
     222
     223    # GCC 4.6 and after.
     224    greaterThan(QT_GCC_MINOR_VERSION, 5) {
     225        if (!contains(QMAKE_CXXFLAGS, -std=c++0x) && !contains(QMAKE_CXXFLAGS, -std=gnu++0x)) {
     226            # We need to deactivate those warnings because some names conflicts with upcoming c++0x types (e.g.nullptr).
     227            QMAKE_CFLAGS_WARN_ON += -Wno-c++0x-compat
     228            QMAKE_CXXFLAGS_WARN_ON += -Wno-c++0x-compat
    223229            QMAKE_CFLAGS += -Wno-c++0x-compat
    224230            QMAKE_CXXFLAGS += -Wno-c++0x-compat
     
    226232    }
    227233}
    228 
  • trunk/Source/WebKit.pri

    r87950 r88006  
    9898        if (!contains(QMAKE_CXXFLAGS, -std=c++0x) && !contains(QMAKE_CXXFLAGS, -std=gnu++0x)) {
    9999            # We need to deactivate those warnings because some names conflicts with upcoming c++0x types (e.g.nullptr).
    100             CONFIG(QTDIR_build) {
    101                 QMAKE_CFLAGS_WARN_ON = -Wno-c++0x-compat
    102                 QMAKE_CXXFLAGS_WARN_ON = -Wno-c++0x-compat
    103             } else {
    104                 QMAKE_CFLAGS += -Wno-c++0x-compat
    105                 QMAKE_CXXFLAGS += -Wno-c++0x-compat
    106             }
     100            QMAKE_CFLAGS_WARN_ON += -Wno-c++0x-compat
     101            QMAKE_CXXFLAGS_WARN_ON += -Wno-c++0x-compat
     102            QMAKE_CFLAGS += -Wno-c++0x-compat
     103            QMAKE_CXXFLAGS += -Wno-c++0x-compat
    107104        }
    108105    }
Note: See TracChangeset for help on using the changeset viewer.