Re: [Flightgear-devel] Hard coded fg-root path in flightgear startup?

[Curtis O. <cur...@fl...>]

"git blame" points the responsibility of that #ifdef to a user named
<david> which I believe would be David Megginson.  Hi David. :-)  Much of
the work and inspiration for the property system and our integrated xml
support came from David's mind.

Initially I used the simgear property system in my own autopilot flight
control code.  However, I decided for embedded applications it wasn't worth
trying to compile and track *all* of simgear (which I believe has (or had)
some opengl dependencies and other things that would have been hard to
support and also I didn't need.)  So I forked a copy of what I needed from
simgear and maintained that separately in my own app.  Over time things
diverged.

For a long time I had an idea that an embedded autopilot for uav's  (for
education and research) would greatly benefit from embedded python if there
wasn't any performance issues.  I've never found anyone else who thought
that would be a good idea!  Despite that, I couldn't shake the idea out of
my brain so last year about this time I acted.  I started by rewriting the
property system in pure python.  The property tree now is an extensible
python class.  This allowed me (a) to clean up the property tree
implementation ... 98% of the simgear features I never used.  (b) A pure
python property tree can be shared between python and C++ modules (given a
little bit of C++ wrapper work.)  (c) I really like what I ended up with.
I think it works well.  I'm able to run my flight control computer onboard
the actual airplane at a solid 100hz.  The whole mission/task system is now
written in python and extensible.

So to answer your question, no, I have no recollection of being the one
responsible for #ifdef standalone. :-)

Curt.

On Tue, Jan 3, 2017 at 9:09 AM James Turner <zak...@ma...> wrote:

>
> > On 3 Jan 2017, at 14:59, Curtis Olson <cur...@fl...> wrote:
> >
> > So anyway, all that to say that the original reasons for keeping simgear
> as a separate package from FlightGear are largely non-existent.
> >
>
> Out of curiosity, was this also the reason for the ‘standalone props’
> #ifdefs in props.cxx ?
>
> Kind regards,
> James
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>