Re: [Flightgear-devel] Flightgear-Swift (VATSIM) connection

[Lars T. <de...@lt...>]

I’ve now created an additional merge request to Windows 3rd Party Deps which should include all dependencies. 

 

I have also tested it again and it and it seems that expat isn’t needed anymore. So only libevent and dbus for now.

 

Best regards

Lars

 

Von: James Turner <ja...@fl...> 
Gesendet: Mittwoch, 6. März 2019 13:34
An: FlightGear developers discussions <fli...@li...>
Betreff: Re: [Flightgear-devel] Flightgear-Swift (VATSIM) connection

 

 





On 6 Mar 2019, at 12:23, Lars Toenning < <mailto:de...@lt...> de...@lt...> wrote:

 

And regarding the libs needed one of the swift developer wrote:

 

- “libevent is needed to drive the low level dbus library. Generally dbus suggests to use high level bindings like Qt or Glib. But pulling those into the XPlane process was too much. If FG is already using Qt in the sim process you could easily use QtDBus instead.

- dbus is not a hard requirement. The connection can be implemented in many different ways.”

“

 

My idea was to have a basic working connection available first and do some more improvements and possibly a change from dbus to something else later on.

 

Qt in FG is optional so let’s not couple Swift support to that. I’m fine with using DBus directly so long as the deployment works out easily, let’s give it a go and find out. I would in general prefer to use a lower-level protocol (which FG already has several of) rather than DBus, but I totally understand DBus is probably much faster to get running if already supported on the Swift side.

 

Kind regards,

James