James
The "this" fault is fixed. Thanks.
To cure the time and difftime under Windows all that is needed is to include
<time.h>
Alan
_____
From: Alan Teeder [mailto:ajtee...@v-twin.org.uk]
Sent: 06 October 2009 17:38
To: 'FlightGear developers discussions'
Subject: Re: [Flightgear-devel] GPS / route-manager landing
Also VC90 also does not "this" at line 70 of route_mgr.cxx. :-
Compiling...
route_mgr.cxx
..\..\..\src\Autopilot\route_mgr.cxx(70) : warning C4355: 'this' : used in
base member initializer list
..\..\..\src\Autopilot\route_mgr.cxx(229) : error C3861: 'time': identifier
not found
..\..\..\src\Autopilot\route_mgr.cxx(233) : error C3861: 'time': identifier
not found
..\..\..\src\Autopilot\route_mgr.cxx(234) : error C3861: 'difftime':
identifier not found
Build log was saved at
"file://d:\fg\source\projects\VC90\FlightGear\Win32\Release\BuildLog.htm"
Alan
_____
From: Nicolas Quijano [mailto:nquij...@gmail.com]
Sent: 06 October 2009 17:22
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] GPS / route-manager landing
Hi all, this doesn't build on windows, it can't find the time symbol
referenced at line 229 and 233 in route_mgr.cxx.
Missing header ?
Also, there is a reference to std::strncasecmp in positioned.cxx around line
820, which is also not available in windows (at least, not here).
Since it's dealing with c strings, I've added locally an #ifdef WIN32 check
which uses_stricmp instead in this case.
Don't know how you want to deal with this,
Cheers,
Nic
On Mon, Oct 5, 2009 at 3:59 AM, James Turner <zakal...@mac.com> wrote:
On 5 Oct 2009, at 08:33, Dave wrote:
> That all sounds like good stuff. I'll try and migrate the KLN89
> towards
> using it and depreciating the dclgps stuff - that should give it some
> testing.
Sounds good to me. I've been going through the KLN89 manual, and
there's definitely some more subtle options that will require extra
features / flags (off the top of my head, resuming LEG mode from OBS
mode, and the ability to DTO without recentering the d-bar).
Many things should be achievable with a bit of Nasal glue, obviously
I've tried to make simple building block functionality as much as I
can. If you think an API or design is poor, or missing a feature, let
me know and I'm happy to add it - I'd far rather get the core code
sensible, than have each GPS device work around the same bug!
In terms of API examples, I will be committing a new GPS dialog, which
shows off most of the new features, and will also allow the GPS to be
used in aircraft without real hardware, if we want that. I'm also
going to create a wiki page for the GPS, to document what it can (and
can't do).
Regards,
James
----------------------------------------------------------------------------
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Be Kind.
Remember, everyone is fighting a hard battle.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
