[wpe-webkit] Debugging options with wpewebkit

[Vanhauwaert Wouter]

> -----Original Message-----
> From: webkit-wpe [mailto:webkit-wpe-bounces at lists.webkit.org] On Behalf
> Of Adrian Perez de Castro
> Sent: donderdag 4 oktober 2018 14:21
> To: Aras Vaichas
> Cc: webkit-wpe at lists.webkit.org
> Subject: Re: [wpe-webkit] Debugging options with wpewebkit
> 
> Hello again Aras,
> 
> I noticed that you forgot to keep the mailing list in copy, so I have added
> it again — it is nice to have the reply with your solution also archived for
> future reference :)
> 
> On Thu, 4 Oct 2018 12:54:40 +0100, Aras Vaichas <aras.vaichas at gmail.com>
> wrote:
> 
> > Thank you for the help, everything is working now.  For the sake of
> > completeness, I'll put down the solution which worked for me.
> 
> Glad to know that it is working for you now. That's great.
> 
> > On Wed, 3 Oct 2018 at 16:13, Adrian Perez de Castro <aperez at igalia.com>
> > wrote:
> > > For console logs there are two possibilities. The simplest is to use
> > > “webkit_settings_set_enable_write_console_messages_to_stdout()” [0]
> in
> > > your application.
> > ...
> > > The remote inspector is well supported since version 2.20.0. You need to
> > > call “webkit_settings_set_enable_developer_extras()” [4] — otherwise
> the
> > > “WEBKIT_INSPECTOR_SERVER” environment variable is ignored.
> >
> > target:
> > # export WEBKIT_INSPECTOR_SERVER='127.0.0.1:8000'
> > # cat << EOF > cog.cfg
> > [websettings]
> > enable-write-console-messages-to-stdout=true
> > enable-developer-extras=true
> > EOF
> > # cog --version
> > 0.1.0
> > # cog -C cog.cfg index.html
> 
> Ah, somehow I did not notice that you were already using Cog. You are right,
> and using a configuration file is indeed much easier because then you don't
> need to edit any source code.
> 
> With Cog there's also command line options which have the same names, so
> this also works:
> 
>   # WEBKIT_INSPECTOR_SERVER='127.0.0.1:8000' cog \
>       --enable-write-console-messages-to-stdout=true \
> 	  --enable-developer-extras=true ${URL}
> 
> Of course the configuration file is more convenient if you are setting many
> options — I just want to make you know that the command line options are
> available as well :)

Just a heads up for later reference.
To be able to debug from everywhere towards a wpe target, you'll have to set
WEBKIT_INSPECTOR_SERVER to 0.0.0.0:1234 (or another port)
If you put it to 127.0.0.1, it'll not be accessible from outside

Grt