Re: [Flightgear-devel] CMake, tomorrow (Sunday 23rd)

[Erik H. <er...@eh...>]

On Sun, 2011-10-23 at 09:44 +0100, James Turner wrote:
> The special purpose FDMs are disabled by default, it's one line to make them enabled by default of course!
> 
> Actually, one of my post CMake build plans, is to make all the FDMs switchable at build-time, partly because I'm sick of all the compiler warnings from the UIUC / larcsim code, but also because at some point in the future we want the FDMs to be more 'modular' to the rest of FG - eg in their own thread or HLA-process, potentially. Knowing that the code builds cleanly with, for example, *just* the Null/UFO FDM selected would be interesting.

We had been thinking about that in the past but with the lack of a build
server we decided that leaving them all in was the safest option.
> 
> So we will have ENABLE_YASIM, ENABLE_LARCSIM, ENABLE_JSBSIM and so on. Obviously I will keep the defaults for those to match the current expectations (well, maybe Larcsim could be off by default? Does anyone ever use it?)

I believe UIUC uses LaRCsim. I agree the UIUC code is becoming a problem
since they used to develop in in house and dump a bunch of code in the
FlightGear tree when there was still development in that area. I must
admit I don't have a clue if we even are allowed to change or fix the
UIUC code, and if there is a chance changes get overwritten when they
decide to push another round of updates...

> But you've convinced it's a good idea to have a Jenkins build, which has all the FDMs enabled, to avoid bit-rot in the special ones!

Ah great.

Erik