Re: [Flightgear-devel] MSVC compile fail with simgear commit45ae3978f6109d425e17f58eae543543f304ef93
All OK now. Many thanks to James, Christian and Frederic. Alan -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC compile fail with simgear commit45ae3978f6109d425e17f58eae543543f304ef93
On 8 Feb 2013, at 09:38, Alan Teeder ajtee...@v-twin.org.uk wrote:
Many thanks to James, Christian and Frederic.
With the update code, it would be a good time to think about what logging makes
sense on Windows; we now log to a file in FG_HOME, which I hope will make
getting feedback from testers easier ('just send me your log file' - might even
make a button in the about-diaog for this, although we have no portable way to
get an email created with an attachment, eugh).
On Windows, we can open up a console from the app (as we did forever), but
this looks kind of scary for people, so I think it should be optional, but I'm
not sure optional on what. There's also the possibility to use
OutputDebugMessage which goes to the MSVC console. Some people prefer that if
developing inside MSVC, but of course other people dislike it! Anyway since I'm
not on Windows I leave it to the people developing on that platform, to decide
what makes sense.
My next step is to make a custom PUI widget showing certain log types in the UI
- especially, terra sync progress (in that dialog), OSG output (especially
shader compile failures) somewhere, and Nasal output in the 'Nasal console'
dialog. I hope each of these will help usability in the respective areas, and
make it easier to get feedback from less technical users. (Again I'll probably
include a 'copy to clipboard' button in each case)
James
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FG Git compilation fail on Linux x86_64
Hello! I just pulled FG Git for compiling and testing it. At first I tried with SP_FDMS, yet the build fails at 61%, giving me this output: [ 61%] Building CXX object src/Main/CMakeFiles/fgfs.dir/__/FDM/groundcache.cxx.o [ 61%] Building CXX object src/Main/CMakeFiles/fgfs.dir/__/FDM/SP/ACMS.cxx.o [ 61%] Building CXX object src/Main/CMakeFiles/fgfs.dir/__/FDM/SP/ADA.cxx.o /home/orpheus/flightgear/flightgear/src/FDM/SP/ADA.cxx: In member function 'virtual void FGADA::init()': /home/orpheus/flightgear/flightgear/src/FDM/SP/ADA.cxx:190:42: error: 'printf' was not declared in this scope make[2]: *** [src/Main/CMakeFiles/fgfs.dir/__/FDM/SP/ADA.cxx.o] Error 1 make[1]: *** [src/Main/CMakeFiles/fgfs.dir/all] Error 2 make: *** [all] Error 2 $ I then tried without SP_FDMS and the compilation fails at 98%, output follows: [ 98%] Built target fgpanel [ 98%] Building CXX object utils/fgai/CMakeFiles/fgai.dir/fgai.cxx.o /home/orpheus/flightgear/flightgear/utils/fgai/fgai.cxx: In function 'int main(int, char**)': /home/orpheus/flightgear/flightgear/utils/fgai/fgai.cxx:532:59: error: 'EOF' was not declared in this scope /home/orpheus/flightgear/flightgear/utils/fgai/fgai.cxx:550:13: error: 'logbuf' has not been declared /home/orpheus/flightgear/flightgear/utils/fgai/fgai.cxx:551:13: error: 'logbuf' has not been declared make[2]: *** [utils/fgai/CMakeFiles/fgai.dir/fgai.cxx.o] Error 1 make[1]: *** [utils/fgai/CMakeFiles/fgai.dir/all] Error 2 make: *** [all] Error 2 $ System is a Gentoo Linux x86_64 system on an i7@2.8GHz, Nvidia GeForce GTX260, 12GB RAM. GCC ver. 4.5.4 Up to 3 weeks ago FG Git was compiling without errors, both with and without SP_FDMS. Let me know if you require more info! Thanks for the help and the amazing work you all do! FG has helped me a lot in my PPL course! :) Best Regards, Klearchos (muadib25), SE-MUA. Sweden -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Checklists enhancement
This seems a good idea. Is the intention to make tutorials easier to compose, or is it to replace them? At the moment, checklist.nas fails at line 6 – presumably because my aircraft doe not yet have a checklist. If my assumption is correct then the code should have a test to allow it as most aircraft are (and probably will remain) like this - or perhaps a low level warning should be issued to alert the aircraft maintainer. Alan From: Gijs de Rooy Sent: Thursday, February 07, 2013 10:28 PM To: FlightGear Development list Subject: Re: [Flightgear-devel] Checklists enhancement Hi Stuart, one request I would like to place is to automatically spread the checklist over multiple pages if it gets longer than, say 20 lines. Especially the complex birds tend to have long checklists ;-) Cheers, Gijs -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
