Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt WebKit
  4. Building QtTestBrowser standalone [SOLVED]
Forum Updated to NodeBB v4.3 + New Features

Building QtTestBrowser standalone [SOLVED]

Scheduled Pinned Locked Moved Qt WebKit
2 Posts 1 Posters 2.8k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    svenyonson
    wrote on last edited by
    #1

    I used to be able to build QtTestBrowser in the /Tools/QtTestBrowser directory using:

    qmake .
    make

    after having built QtWebKit with Scripts/build-webkit.

    But now having cloned the latest WebKit, trying the above I am getting lots of link errors, i.e.
    /Tools/QtTestBrowser/launcherwindow.cpp:150: undefined reference to `QWebPage::mainFrame() const'

    Is there some environment variable I am missing?

    [SOLVED 9/25]
    I was able to solve my real problem - moving the project out from under WebKit - by adding the following environment variable:
    export QMAKEPATH='/yourpath/WebKit/Tools/qmake'

    [Update 9/25]
    Well, I thought I had it fixed. I was still getting same link errors, until I specifically pulled in WebKit1:
    WEBKIT += wtf webcore webkit1

    1 Reply Last reply
    0
    • S Offline
      S Offline
      svenyonson
      wrote on last edited by
      #2

      OK, I have gotten past the first issue by adding the following to my .pro file:
      CONFIG -= production_build
      WEBKIT_CONFIG -= build_webkit2

      But now to the real problem. I made a copy of the project folder: QtTestBrowser2. If this folder lives ANYWHERE under the WebKit directory, it builds fine - qmake magically finds the Tools/qmake/mkspecs folder and all is good. If I move QtTestBrowser2 out from under WebKit, it no longer builds or finds Tools/qmake/mkspecs. There is nothing in the QtTestBrowser.pro that references Tools. Where is this magic occurring, and how can I make the project build without living under the WebKit folder?

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved