D-Bus interface

[Dan Williams]

On Tue, 2012-04-24 at 17:34 +0100, Andr? Prata wrote:
> Thanks for the reply Dan,
> 
> 
> Is there any project or examples you would you recommend as a
> reference on how to configure and control wpa_supplicant (much like
> networkmanager), other than wpa_supplicant itself and networkmanager?

There are some python examples in wpa_supplicant/examples, so if you're
able to translate python to what you need that would work, otherwise
you'll need to do code inspection.  I suppose we could actually make the
introspection data more verbose and generate docs off that, but that
would require running the built copy of the supplicant at build time
which isn't very compatible, especially with cross compiling.

Dan

> 
> Thank you very much,
> Andr?
> 
> On Tue, Apr 24, 2012 at 17:12, Dan Williams <dcbw at redhat.com> wrote:
>         On Tue, 2012-04-24 at 16:09 +0100, Andr? Prata wrote:
>         > Hi!
>         >
>         >
>         > Since I can't find it on my own, I'd like to ask if there's
>         a place
>         > where I can find a D-Bus interface documentation like this
>         for
>         > wpa_supplicant:
>         http://projects.gnome.org/NetworkManager/developers/api/09/spec.html
>         >
>         >
>         > If not, is the usual method of determining the interface to
>         just
>         > introspect the D-Bus objects?
>         
>         
>         At the moment, yeah.  Since wpa_supplicant uses raw D-Bus
>         instead of a
>         framework like gdbus or qtdbus (since the supplicant does not
>         depend on
>         a specific mainloop, but implements its own), documentation
>         can't be
>         autogenerated, which means somebody needs to manually write
>         it.  Would
>         be great to have autogenerated docs like the NM ones, but that
>         would
>         also mean a somewhat more complex build process which may not
>         be welcome
>         (ie, would require something like docbook or gtkdoc or
>         whatever).  That
>         said, we should try to figure out a way to get documentation
>         that
>         doesn't take a ton of effort to produce...
>         
>         Dan
>         
>         
> 
>