Howto:Submit patches: Difference between revisions

no edit summary
No edit summary
Line 6: Line 6:


* Try to make your patch optionally minimally invasive:
* Try to make your patch optionally minimally invasive:
** provide compile time switches to generally enable or disable your modifications (i.e. using #ifdefs, autoconf and automake macros) That way, you will ensure that your patch can  be easily disabled (excluded from compilation while remaining in the source tree) if it should cause trouble while any issues are addressed
** provide compile time switches to generally enable or disable your modifications (i.e. using #ifdefs, [http://sources.redhat.com/autobook/ autoconf and automake] macros) That way, you will ensure that your patch can  be easily disabled (excluded from compilation while remaining in the source tree) if it should cause trouble while any issues are addressed. This applies in particular if your patch introduces any extra dependencies (i.e. libraries).
** provide capabilities to enable or disable your code modifications at startup time or even at  runtime, using command line options or preferably the PropertyTree and some simple GUI dialog to enable developers and users to decide whether  they want to activate your code. That way, it can be ensured that your code doesn't interfere with any other FlightGear components. This will make potential bug tracking much easier.
** provide capabilities to enable or disable your code modifications at startup time or even at  runtime, using command line options or preferably the PropertyTree and some simple GUI dialog to enable developers and users to decide whether  they want to activate your code. That way, it can be ensured that your code doesn't interfere with any other FlightGear components. This will make potential bug tracking much easier.


Anonymous user