HOWTO configure Eclipse with ns-3 - Revision history

Rediet: /* Clearing Eclipse errors */ Add STD C++ configuration

2020-06-17T10:30:34Z

Clearing Eclipse errors: Add STD C++ configuration

← Older revision		Revision as of 10:30, 17 June 2020
Line 492:		Line 492:
	* Re-build the index of the project (by right-clicking your CDT project and selecting 'Index' then 'Rebuild').		* Re-build the index of the project (by right-clicking your CDT project and selecting 'Index' then 'Rebuild').
	If errors are still displayed in the project directory tree, open the concerned files to clear them.		If errors are still displayed in the project directory tree, open the concerned files to clear them.

			Another means of clearing errors is configuring the C++ standard GCC uses to C++14 (or C++11 at least), by following the steps in the screenshot.
			[[File:Preproc-include-std.png\|200px\|thumb\|right\|Builder Settings Screenshot]]

Rediet: /* Applying ns-3 formatting */ New section

2020-06-17T10:21:09Z

Applying ns-3 formatting: New section

Show changes

Rediet: /* Configure Mercurial */ Mark as obsolete

2020-06-17T09:44:57Z

Configure Mercurial: Mark as obsolete

← Older revision		Revision as of 09:44, 17 June 2020
Line 1:		Line 1:
	== Configure Mercurial ==		== Configure Mercurial ==

			This section is obsolete. The project has moved to GitLab so use git (through eGit plugin).

	* First download eclipse IDE for C++ developers from http://www.eclipse.org		* First download eclipse IDE for C++ developers from http://www.eclipse.org

Rediet: /* Configure Test-runner */

2020-06-17T09:42:35Z

Configure Test-runner

← Older revision		Revision as of 09:42, 17 June 2020
Line 70:		Line 70:
	* Go to the "Arguments" tab and add "'''--assert-on-failure --suite=${string_prompt}'''"		* Go to the "Arguments" tab and add "'''--assert-on-failure --suite=${string_prompt}'''"
	* Click on Apply and on Debug if you want to immediately debug the application		* Click on Apply and on Debug if you want to immediately debug the application

			<br clear="all"/>

	== Configure To Run From Eclipse ==		== Configure To Run From Eclipse ==

Rediet: /* Configure Test-runner */ Add new section

2020-06-17T09:41:33Z

Configure Test-runner: Add new section

← Older revision		Revision as of 09:41, 17 June 2020
Line 56:		Line 56:

	<br clear="all"/>		<br clear="all"/>


			== Configure Test-runner ==

			[[File:App-test-runner-duplicate.png\|200px\|thumb\|right\|Generate test-runner app from debug]]
			[[File:App-test-runner-arguments.png\|200px\|thumb\|right\|Test-runner app arguments]]

			Here are the steps to add and configure a test-runner application which prompts the test-suite to execute:

			* Click on the "Debug Configurations" option under the "Run" menu
			* Select the debug application defined in the previous section and duplicate it (so as to inherit from its configuration). Rename the new application
			* Click on the "Browse" button under the "Project" section and select the "'''[project name]-test-runner-debug'''" executable in "'''[project path]/build/utils'''"
			* Go to the "Arguments" tab and add "'''--assert-on-failure --suite=${string_prompt}'''"
			* Click on Apply and on Debug if you want to immediately debug the application

	== Configure To Run From Eclipse ==		== Configure To Run From Eclipse ==

Rediet: /* Configure Debugger */

2020-06-17T09:30:37Z

Configure Debugger

← Older revision		Revision as of 09:30, 17 June 2020
Line 36:		Line 36:
	[[File:Debug-main.png\|200px\|thumb\|right\|Debugger main tab]]		[[File:Debug-main.png\|200px\|thumb\|right\|Debugger main tab]]
	[[File:Debug-env.png\|200px\|thumb\|right\|Debugger environment tab]]		[[File:Debug-env.png\|200px\|thumb\|right\|Debugger environment tab]]
			[[File:App-debug-add-ns-log.png\|200px\|thumb\|right\|Debugger adding NS_LOG variable]]

	Suppose you want to debug a test application called "test" under the scratch folder. Here are the steps:		Suppose you want to debug a test application called "test" under the scratch folder. Here are the steps:
Line 48:		Line 49:
	** "'''${workspace_loc:ns-3-dev}/build'''" for ns-3.28 and former		** "'''${workspace_loc:ns-3-dev}/build'''" for ns-3.28 and former
	** "'''${workspace_loc:ns-3-dev}/build/lib'''" for ns-3.29 and later (i.e. all versions after April 13 2018)		** "'''${workspace_loc:ns-3-dev}/build/lib'''" for ns-3.29 and later (i.e. all versions after April 13 2018)
			* Add a new variable named "NS_LOG", used to activate logging (see manual)
	* Be sure the "Append environment to native environment" is selected		* Be sure the "Append environment to native environment" is selected
	* Click on Apply and on Debug if you want to immediately debug the application		* Click on Apply and on Debug if you want to immediately debug the application

Rediet: /* Configure Debugger */ Update LD_LIBRARY_PATH value due to changes in build lib locations (r13485 and r13488)

2018-11-19T08:41:06Z

Configure Debugger: Update LD_LIBRARY_PATH value due to changes in build lib locations (r13485 and r13488)

← Older revision		Revision as of 08:41, 19 November 2018
Line 45:		Line 45:
	* Go into the "Environment" tab and click on "New" to create a new variable		* Go into the "Environment" tab and click on "New" to create a new variable
	* Type under the Name field "LD_LIBRARY_PATH" (or "DYLD_LIBRARY_PATH" if you are on a MacOSX)		* Type under the Name field "LD_LIBRARY_PATH" (or "DYLD_LIBRARY_PATH" if you are on a MacOSX)
	* Type under the Value field "'''${workspace_loc:ns-3-dev}/build'''"		* Type under the Value field:
			** "'''${workspace_loc:ns-3-dev}/build'''" for ns-3.28 and former
			** "'''${workspace_loc:ns-3-dev}/build/lib'''" for ns-3.29 and later (i.e. all versions after April 13 2018)
	* Be sure the "Append environment to native environment" is selected		* Be sure the "Append environment to native environment" is selected
	* Click on Apply and on Debug if you want to immediately debug the application		* Click on Apply and on Debug if you want to immediately debug the application

Rediet: /* Miscellaneous tips */ Added subsection "Clearing Eclipse errors" following ns-3-users post entitled "configure eclipse for NS3.26"

2017-09-21T12:03:43Z

Miscellaneous tips: Added subsection "Clearing Eclipse errors" following ns-3-users post entitled "configure eclipse for NS3.26"

← Older revision		Revision as of 12:03, 21 September 2017
Line 95:		Line 95:
	This tip is for [[Ubuntu Linux]] distributions. The paths might be different		This tip is for [[Ubuntu Linux]] distributions. The paths might be different
	for other distributions.		for other distributions.
	In a terminal write the following:
	#* pkg-config --cflags libxml-2.0		* In a terminal write the following: '''pkg-config --cflags libxml-2.0'''
	#* Copy the output. (For example: * -I/usr/include/libxml2* )		* Copy the output. (For example: ''' -I/usr/include/libxml2''' )
	#* Right-click your CDT project and select Properties.		* Right-click your CDT project and select 'Properties'.
	#* Expand C/C++ General and select Paths and Symbols.		* Expand 'C/C++ General' and select 'Paths and Symbols'.
	#* Select GNU C++ under Languages		* Select 'GNU C++' under Languages
	#* Click Add to define new element		* Click 'Add' to define new element
	#* Write in the Directory field what was the output of the pkg-config command without the -I prefix i.e: /usr/include/libxml2		* Write in the Directory field what was the output of the pkg-config command without the -I prefix i.e: '''/usr/include/libxml2'''
	#* Re-build the ns-3 project.		* Re-build the ns-3 project.

	--[[User:Loulloudes.n\|Nicholas Loulloudes]] 03:16, 30 December 2011 (EST)		--[[User:Loulloudes.n\|Nicholas Loulloudes]] 03:16, 30 December 2011 (EST)

			=== Clearing Eclipse errors ===

			This tip has been suggested on the user forum. It aims at clearing errors reported by Eclipse even though the project builds and runs correctly (according to waf).
			* Right-click your CDT project and select 'Properties'.
			* Expand 'C/C++ General' and select 'Paths and Symbols'.
			* Select 'GNU C++' under Languages
			* Click 'Add' to define new element
			* Browse the 'Workspace...' and select the '''build''' directory of your CDT project (it should be recognized as a workspace path)
			* Re-build the ns-3 project
			* Re-build the index of the project (by right-clicking your CDT project and selecting 'Index' then 'Rebuild').
			If errors are still displayed in the project directory tree, open the concerned files to clear them.

Vedranm: moved HOWTO configure eclipse with ns-3 to HOWTO configure Eclipse with ns-3: Wrong capitalization

2012-10-04T11:00:19Z

moved HOWTO configure eclipse with ns-3 to HOWTO configure Eclipse with ns-3: Wrong capitalization

← Older revision	Revision as of 11:00, 4 October 2012
(No difference)

Tommaso: /* Configure Mercurial */

2012-02-22T02:02:40Z

Configure Mercurial

← Older revision		Revision as of 02:02, 22 February 2012
Line 8:		Line 8:
	** Click on add a site		** Click on add a site
	** Add http://cbes.javaforge.com/update (taken from http://javaforge.com/project/HGE) then click on mercurialeclipse and check the box and click on install		** Add http://cbes.javaforge.com/update (taken from http://javaforge.com/project/HGE) then click on mercurialeclipse and check the box and click on install
	* We suppose that you already have mercurial installed on your machine		* We suppose that you already have [http://http://mercurial.selenic.com/ mercurial] installed on your machine
	* start eclipse, it will create a workspace directory ~~NB:It~~ is advised to use a ~~different~~ directory for the ~~code say~~ ~/src		* start eclipse, it will create a workspace directory in your user's directory named "workspace". You can choose whatever you want but it is advised to use a directory just for the Eclipse projects. Eclipse will put invisible files there and moving the projects from one place to another might be a pain. Mine is in ~/Development/workspace, others prefer ~/src/workspace. You choose your.
	* clone the mercurial reppository: go to ~/src and execute hg clone http://code.nsnam.org/ns-3-dev ns-3-dev		* clone the mercurial reppository: go to ~/src and execute hg clone http://code.nsnam.org/ns-3-dev ns-3-dev
	* create a new empty C++ project with your preferred name and the path is ~/src/ns-3-dev on		* create a new empty C++ project with your preferred name and the path is ~/src/ns-3-dev on