FGPythonSys: Difference between revisions

Jump to navigation Jump to search
Line 64: Line 64:


== Getting involved ==
== Getting involved ==
Talking about building something awesome, do you have coding skills?  If so, what is your opinion of code implementation via test suites?  If you are interested in converting your dreams into any type of reality, then join in the thread at [https://forum.flightgear.org/viewtopic.php?f=6&amp;t=28378&amp;p=283183#p289080 viewtopic.php?f=6&amp;t=28378&amp;p=283183#p289080], git check out my FGPythonSys branches (into clones of the official repositories), and start implementing awesome new features <ref>{{cite web
  |url    =  https://forum.flightgear.org/viewtopic.php?p=296226#p296226
  |title  =  <nowiki> Re: Nasal must go </nowiki>
  |author =  <nowiki> bugman </nowiki>
  |date  =  Oct 7th, 2016
  |added  =  Oct 7th, 2016
  |script_version = 0.40
  }}</ref>
On Linux, you will want to make sure that the python3-dev and cppunit packages are installed (e.g. <code>sudo apt-get install python3-dev cppunit</code>, you can then set up remote tracking branches for the sg/fg and fgdata repositories, e.g.:
On Linux, you will want to make sure that the python3-dev and cppunit packages are installed (e.g. <code>sudo apt-get install python3-dev cppunit</code>, you can then set up remote tracking branches for the sg/fg and fgdata repositories, e.g.:


Navigation menu