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

[James T. <ja...@fl...>]

> On 6 Mar 2019, at 08:27, Lars Toenning <de...@lt...> wrote:
> 
> as mentioned some time ago I have now finished the connection module to swift (WIP VATSIM client) and created merge requests:
> https://sourceforge.net/p/flightgear/flightgear/merge-requests/154/ <https://sourceforge.net/p/flightgear/flightgear/merge-requests/154/>
> https://sourceforge.net/p/flightgear/fgdata/merge-requests/136/ <https://sourceforge.net/p/flightgear/fgdata/merge-requests/136/>
>  
> To show the features I created a small video: https://www.youtube.com/watch?v=l5O3tRobYPY <https://www.youtube.com/watch?v=l5O3tRobYPY>
>  

Thanks Lars, this looks really good.

> One thing I’m unsure of are the dependencies needed. Currently dbus, libevent and libexpat are needed. Should I put this somewhere in thirdparty repo?

On Linux we wouldn’t want to bundle those since they are standard - we just need to add CMake checks for them.

Mac is a bit special, we tend to install dependencies like that via Homebrew, which again should have all of those. (Although, I’m surprised libevent is needed)

Windows is the awkward one, we need to get the built version of the libs into windows-3rd-party. But DBus may complicate this, since it needs some build-time tooling I think?

Where is the DBus requirement coming from? Is it something we could do in another way or a hard requirement?

Kind regards,
James