Hi Jocelyn,
Thanks for your inputs. and Sorry for the very late reply (was held up
with some other tasks) .
I finally could figure out what was the issue.
It was because the loading of the resources required for remote inspector
(WebKit.qrc and InspectorBackendStub.qrc) were failing which WebKit
should take by itself ( I have built WebKit as Windows shared library).
Now I am doing it explicitly in my application calling
Q_INIT_RESOURCE(WebKit) and Q_INIT_RESOURCE(InspectorBackendStub) and
also by adding these resources in my application pro file.
Correct me if I am wrong here. I know that this is not the proper solution
as WebKit had to do this implicitly but when I searched for Q_INIT_RESOURCE
macro in WebKit Source code I could not find any.
I just wanted to know when does the resource loading happen in case of both
when WebKit is built as static library and as a shared library. And without
Q_INIT_RESOURCE being called how does it load the resources, is there any
other way...
Thanks and Regards,
Amogh
On Tue, Aug 20, 2013 at 4:22 PM, Jocelyn Turcotte <
jocelyn.turco...@digia.com> wrote:
> Hello,
>
> On Tue, Aug 20, 2013 at 01:28:29PM +0530, Amogh Kudari wrote:
> > Debugging the issue further I am amble to see that its failing
> to
> > launch remote inspector because its unable to find the inspector.html
> file.
>
> You're on your own if you're using an outdated trunk revision, especially
> with an unsupported feature.
>
> p.s. http://trac.webkit.org/changeset/137436 might help.
>
> Cheers,
> Jocelyn
>
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
