Bug 29418 – [Qt] In a static build of Demo Browser, the Web Inspector does not load content

• Status: RESOLVED
• Resolution: WONTFIX
• Component: Web Inspector (Deprecated)

[Tor Arne Vestbø]

This bug report originated from issue QTBUG-4026
<http://bugreports.qt.nokia.com/browse/QTBUG-4026>

--- Description ---

In a static build of Demo Browser, the Web Inspector does not load any content

[Laszlo Gombos]

I'm not sure if this is related to the "static build of Demo Browser" 

Seen a similar problem using r50369 and QtLauncher. Build options for reference: "build-webkit --qt --no-svg -spec macx-g++ --no-video CONFIG+=QT_NO_UITOOLS CONFIG+=webkit_no_framework".

[Brian Ellis]

This bug has been present for over a year now.  It is preventing us from adding support for the Inspector to placemark balloons in Google Earth, which would be extremely helpful for content developers.  I'd like to propose raising the priority of this bug.

[Jędrzej Nowacki]

With Qt 4.7 we are unfortunately not going to support static linking of QtWebKit anymore.

[Jędrzej Nowacki]

(In reply to comment #2)
> This bug has been present for over a year now.  It is preventing us from adding support for the Inspector to placemark balloons in Google Earth, which would be extremely helpful for content developers.  I'd like to propose raising the priority of this bug.

Please, consider to use dynamic linking instead.

[Brian Ellis]

Linking QtWebKit dynamically would add a significant amount of size to our binary; this is a big enough problem for us that we may no longer be able to use upgraded versions of QtWebKit, which would mean we'd have to move off of QtWebKit entirely for security reasons.  Does this prohibition on static linking apply only to QtWebKit, or to all Qt libraries in 4.7?