DevGuide/CodeEditors - Revision history

Coppolam: Removed empty section

2017-11-28T10:38:17Z

Removed empty section

← Older revision		Revision as of 04:38, 28 November 2017
Line 82:		Line 82:
	## Tick the ''Enable project specific settings'' tick box		## Tick the ''Enable project specific settings'' tick box
	## Import the Paparazzi profile from {root paparazzi directory}/paparazzi_code_profile_eclipse.xml		## Import the Paparazzi profile from {root paparazzi directory}/paparazzi_code_profile_eclipse.xml

	~~=== Qt ===~~

	== Debugging tools ==		== Debugging tools ==

Kirkscheper: Update Eclipse description and add how to set the Paparazzi code style

2017-11-28T09:36:25Z

Update Eclipse description and add how to set the Paparazzi code style

← Older revision		Revision as of 03:36, 28 November 2017
Line 57:		Line 57:
	Next are the IDE's for C development		Next are the IDE's for C development

	~~=== Netbeans ===~~
	=== Eclipse ===		=== Eclipse ===

Line 65:		Line 64:
	In case we want to work with a single aircraft and want Eclipse to also compile the autopilot code, we have to do the following:		In case we want to work with a single aircraft and want Eclipse to also compile the autopilot code, we have to do the following:
	# Import paparazzi into eclipse as normal		# Import paparazzi into eclipse as normal
	# in ~~project~~->~~properties~~->c/c++->~~environment~~ add three variables		# in Project->Properties->C/C++ Build->Environment, add three variables
	## Current_Airframe: set to the name of the airframe you want to build		## Current_Airframe: set to the name of the airframe you want to build
	## PAPARAZZI_HOME: set to the root paparazzi directory		## PAPARAZZI_HOME: set to the root paparazzi directory
	## PAPARAZZI_SRC: set to the root paparazzi directory		## PAPARAZZI_SRC: set to the root paparazzi directory
	# in ~~project~~->~~properties~~->c/c++		# in Project->Properties->C/C++ Build
	## in ''Builder Settings'' Tab		## in ''Builder Settings'' Tab
	### Uncheck ''Use default build command''		### Uncheck ''Use default build command''
Line 77:		Line 76:
	### set the Clean field to:clean_ac		### set the Clean field to:clean_ac

	That will compile ''Current_Aiframe'' with target ''ac''. ~~Obviously, if you need a different target, for example ''test_telemetry'',~~ you will have to ~~change~~ the ~~last two steps~~ to ''~~test_telemetry~~.~~compile~~'' ~~and so on~~.		That will compile ''Current_Aiframe'' with target ''ac''. For this to work however you will first have to set the conf/conf.xml symlink to the correct location. This can be done using ''./start'' in your terminal from the root paparazzi directory.

	=== ~~Code::Blocks~~ ===		We also recommend that you load the paparazzi code style into Eclipse, this can be done with the following:
			# Navigate to Project->Properties->C/C++ General->Formatter
			## Tick the ''Enable project specific settings'' tick box
			## Import the Paparazzi profile from {root paparazzi directory}/paparazzi_code_profile_eclipse.xml

			=== Qt ===

	== Debugging tools ==		== Debugging tools ==

Podhrmic at 19:41, 15 June 2016

2016-06-15T19:41:55Z

← Older revision		Revision as of 13:41, 15 June 2016
Line 61:		Line 61:

	* [http://eclipse.org/cdt/ Eclipse CDT]		* [http://eclipse.org/cdt/ Eclipse CDT]
			Typical process consists of compiling the autopilot code for given airframe in Paparazzi center, and then running the related debug configuration in Eclipse. The debugger will first recompile whole Paparazzi (e.g. running "make" in Paparazzi home directory), which is not really useful, but bearable.

			In case we want to work with a single aircraft and want Eclipse to also compile the autopilot code, we have to do the following:
			# Import paparazzi into eclipse as normal
			# in project->properties->c/c++->environment add three variables
			## Current_Airframe: set to the name of the airframe you want to build
			## PAPARAZZI_HOME: set to the root paparazzi directory
			## PAPARAZZI_SRC: set to the root paparazzi directory
			# in project->properties->c/c++
			## in ''Builder Settings'' Tab
			### Uncheck ''Use default build command''
			### in build command put: ''make -f Makefile.ac AIRCRAFT=${Current_Airframe}''
			## In Behavior Tab
			### set the Build field to: ap.compile
			### set the Clean field to:clean_ac

			That will compile ''Current_Aiframe'' with target ''ac''. Obviously, if you need a different target, for example ''test_telemetry'', you will have to change the last two steps to ''test_telemetry.compile'' and so on.

	=== Code::Blocks ===		=== Code::Blocks ===

IHaveADrone: spelling

2016-06-10T15:50:07Z

spelling

← Older revision		Revision as of 09:50, 10 June 2016
Line 37:		Line 37:
	# Click Install Then Next		# Click Install Then Next
	# If you see "Signed but not trusted, ignore the message just click "continue"		# If you see "Signed but not trusted, ignore the message just click "continue"
	# If it all worked, you will see "Install completed ~~sucessfully~~, just click "Finish"		# If it all worked, you will see "Install completed successfully, just click "Finish"

	==== Syntax Highlighting ====		==== Syntax Highlighting ====
Line 55:		Line 55:
	== IDE for C and CPP ==		== IDE for C and CPP ==

	Next are the IDE's for C ~~develpment~~		Next are the IDE's for C development

	=== Netbeans ===		=== Netbeans ===
Line 67:		Line 67:

	===GDB===		===GDB===
	GDB can be used for quite effective Paparazzi debugging. ~~Debuging~~ [[RT_Paparazzi#Debugging_with_an_Eclipse_IDE\|guide]] with Eclipse IDE was already described for [[RT_Paparazzi]], but the exact same steps can be used for classic Paparazzi. The guide is [[RT_Paparazzi#Debugging_with_an_Eclipse_IDE\|here]]:		GDB can be used for quite effective Paparazzi debugging. Debugging [[RT_Paparazzi#Debugging_with_an_Eclipse_IDE\|guide]] with Eclipse IDE was already described for [[RT_Paparazzi]], but the exact same steps can be used for classic Paparazzi. The guide is [[RT_Paparazzi#Debugging_with_an_Eclipse_IDE\|here]]:

	[[Category:Software]] [[Category:Developer_Documentation]]		[[Category:Software]] [[Category:Developer_Documentation]]

Podhrmic: info about GDB debug with Eclipse

2015-02-24T22:41:16Z

info about GDB debug with Eclipse

← Older revision		Revision as of 16:41, 24 February 2015
Line 66:		Line 66:
	== Debugging tools ==		== Debugging tools ==

	GDB		===GDB===
			GDB can be used for quite effective Paparazzi debugging. Debuging [[RT_Paparazzi#Debugging_with_an_Eclipse_IDE\|guide]] with Eclipse IDE was already described for [[RT_Paparazzi]], but the exact same steps can be used for classic Paparazzi. The guide is [[RT_Paparazzi#Debugging_with_an_Eclipse_IDE\|here]]:

	[[Category:Software]] [[Category:Developer_Documentation]]		[[Category:Software]] [[Category:Developer_Documentation]]

Cguerber: Added link to Eclipse CDT as C and CPP IDE

2015-02-15T21:36:11Z

Added link to Eclipse CDT as C and CPP IDE

← Older revision		Revision as of 15:36, 15 February 2015
Line 59:		Line 59:
	=== Netbeans ===		=== Netbeans ===
	=== Eclipse ===		=== Eclipse ===

			* [http://eclipse.org/cdt/ Eclipse CDT]

	=== Code::Blocks ===		=== Code::Blocks ===

Cguerber: Update on OCaml eclipse plugins OcaIDE and ODT

2015-02-15T21:28:06Z

Update on OCaml eclipse plugins OcaIDE and ODT

← Older revision		Revision as of 15:28, 15 February 2015
Line 46:		Line 46:
	* [http://ocamldt.free.fr/ ODT: OCaml Development Tools]		* [http://ocamldt.free.fr/ ODT: OCaml Development Tools]

	OcaIDE seems to be the best option for Eclipse		OcaIDE seems to be the best option for Eclipse. Note that OcaIDE requires eclipse to run under Java 7.
			No release of ODT since November 2013.

	== IDE for Python ==		== IDE for Python ==

Flixr: add link to PyCharm

2013-10-01T21:49:54Z

add link to PyCharm

← Older revision		Revision as of 15:49, 1 October 2013
Line 48:		Line 48:
	OcaIDE seems to be the best option for Eclipse		OcaIDE seems to be the best option for Eclipse

	=== ~~Code~~:~~:Blocks ===~~		== IDE for Python ==

			[http://www.jetbrains.com/pycharm/ PyCharm] is a great Python IDE with awesome completion, code assistance, debugger and git integration and much more...

	== IDE for C and CPP ==		== IDE for C and CPP ==

Flixr: /* Eclipse */

2013-01-04T10:55:09Z

Eclipse

← Older revision		Revision as of 04:55, 4 January 2013
Line 43:		Line 43:
	=== Eclipse ===		=== Eclipse ===

	http://www.~~cocan~~.~~org~~/~~ocaml_and_eclipse~~		* [http://www.algo-prog.info/ocaide/ OcaIDE]
			* [http://ocamldt.free.fr/ ODT: OCaml Development Tools]

			OcaIDE seems to be the best option for Eclipse

	=== Code::Blocks ===		=== Code::Blocks ===

Flixr: /* EMACS */

2012-09-19T09:56:20Z

EMACS

← Older revision		Revision as of 03:56, 19 September 2012
Line 10:		Line 10:

	=== EMACS ===		=== EMACS ===
			Tuareg is a really nice mode for Emacs. On Ubuntu/Debian just '''apt-get install tuareg-mode'''.

	http://www~~-rocq~~.~~inria~~.fr/~~~acohen~~/~~tuareg/index.html.en~~		http://www.emacswiki.org/emacs/TuaregMode

	=== Netbeans ===		=== Netbeans ===