Eclipse CDT projects with bitbake - Revision history

Andrey.filippov: /* Additional manual setup for linux-elphel.project */

2019-04-04T21:25:58Z

‎Additional manual setup for linux-elphel.project

Andrey.filippov: /* Additional manual setup for linux-elphel.project */

2019-04-04T21:25:31Z

‎Additional manual setup for linux-elphel.project

Andrey.filippov: /* Additional manual setup for linux-elphel.project */

2019-04-04T21:22:00Z

‎Additional manual setup for linux-elphel.project

Andrey.filippov: /* Initializing Eclipse Workspace for Existing (Cloned) Projects */

2019-04-04T21:11:13Z

‎Initializing Eclipse Workspace for Existing (Cloned) Projects

Andrey.filippov: /* Project Files and Directories */

2019-01-23T17:56:58Z

‎Project Files and Directories

Andrey.filippov: /* Initializing Eclipse Workspace for Existing (Cloned) Verilog Projects */

2017-11-29T17:27:48Z

‎Initializing Eclipse Workspace for Existing (Cloned) Verilog Projects

Andrey.filippov: /* Initializing Eclipse Workspace for Existing (Cloned) Projects */

2017-11-29T16:46:49Z

‎Initializing Eclipse Workspace for Existing (Cloned) Projects

Andrey.filippov: /* Setting up New Project */

2017-11-22T18:00:28Z

‎Setting up New Project

Andrey.filippov: /* Setting up New Project */

2017-11-22T17:42:59Z

‎Setting up New Project

Andrey.filippov: /* Setting up New Project */

2017-11-22T17:42:08Z

‎Setting up New Project

@@ Line 76: / Line 76: @@
 After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.
 === Additional manual setup for linux-elphel.project===
-[[File:Eclipse_cdt.png|right|400px|frame|Adding ''linux/include/generated/autoconf.h'' entry to ''linux-elphel'' project properties]]
+[[File:Eclipse_cdt.png|right|300px|frame|Adding ''linux/include/generated/autoconf.h'' entry to ''linux-elphel'' project properties]]
 Until we found a way how to set it automatically, the linux/include/generated/autoconf.h file has to be added to the project properties, as shown in the screenshot.

@@ Line 76: / Line 76: @@
 After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.
 === Additional manual setup for linux-elphel.project===
-[[File:Eclipse_cdt.png|right|500px}caption]]
+[[File:Eclipse_cdt.png|right|400px|frame|Adding ''linux/include/generated/autoconf.h'' entry to ''linux-elphel'' project properties]]
 Until we found a way how to set it automatically, the linux/include/generated/autoconf.h file has to be added to the project properties, as shown in the screenshot.

@@ Line 76: / Line 76: @@
 After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.
 === Additional manual setup for linux-elphel.project===
-Until we found a way how to set it automatically, the /${ProjName}/linux/include/generated/autoconf.h file has to be added to the project properties, as shown in the screenshot
+[[File:Eclipse_cdt.png|right|500px}caption]]
-[[Eclipse_cdt.png]]
+Until we found a way how to set it automatically, the linux/include/generated/autoconf.h file has to be added to the project properties, as shown in the screenshot.
 ==Initializing Eclipse Workspace for Existing (Cloned) Verilog Projects==

← Older revision		Revision as of 21:11, 4 April 2019
Line 75:		Line 75:

	After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.		After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.
		+	=== Additional manual setup for linux-elphel.project===
		+	Until we found a way how to set it automatically, the /${ProjName}/linux/include/generated/autoconf.h file has to be added to the project properties, as shown in the screenshot
		+	[[Eclipse_cdt.png]]

	==Initializing Eclipse Workspace for Existing (Cloned) Verilog Projects==		==Initializing Eclipse Workspace for Existing (Cloned) Verilog Projects==

@@ Line 53: / Line 53: @@
 *'''scripts''' - a link to a collection of scripts needed for all projects. It contains the following files:
 **'''run_bitbake.sh''' - script to create an environment and execute bitbake recipe. Used every time Eclipse builds the project.
-**'''used_files.py''' - script to create a list of header files/directories used by bitbake to build the project. It is not needed to run to configure existing projects - all of them are provided with preconfigured '''.cproject''' files. ''TODO: add link to description''
+**'''used_files.py''' - script to create a list of header files/directories used by bitbake to build the project. It is not needed to run to configure existing projects - all of them are provided with preconfigured '''.cproject''' files. ''TODO: add link to description'' [[Used_files]]
 *'''.settings''' - project settings maintained by Eclipse IDE
 *'''src''' - a hard-coded (in '''used_files.py''') directory name for C/C++ source files. Source files should not be in the project root directory for convenience of filter generation for additional source (headers) directories
@@ Line 63: / Line 63: @@
 *'''.project''' - Eclipse general project configuration. This file is copied from version-controlled '''eclipse_project_setup''' during setup or manually.
 *'''README.md''' - README file presented by the Git repository web interface
 *'''VERSION''' - project version, used by bitbake build process to determine which dependent recipes have to be re-ran.
 ==Initializing Eclipse Workspace for Existing (Cloned) Projects==
 After running '''setup.py''' for the first time you may create the brand new workspace for Eclipse, that should have all necessary plugins (such as CDT and EGit at least) already installed. Workspace is created with '''setup_eclipse.py''' script, list of projects that it sets up is saved in '''setup_eclipse_paths.xml''' file. '''setup_eclipse.py''' provides usage information when launched without parameters, for normal run it requires full path to Eclipse installation - directory that contains '''eclipse''' executable and '''eclipse.ini''' configuration. Before running '''setup_eclipse.py''' Eclipse should have all the required plugins installed (at least CDT and EGit) using temporary workspace.

@@ Line 83: / Line 83: @@
 ** CMV300 - development for the high-speed CMOSIS sensor, will be used for other sensors with compatible interface
 *x393_sata - AHCI/SATA subsystem. The code is included in x393, this repository is for faster troubleshooting and may be used for other applications
-*x359 - FPGA code for [[10359|10359 sesnor multiplexer]]
+*x359 - FPGA code for [[10359|10359 sensor multiplexer]]
 These projects are now opened from the second instance of Eclipse IDE. [https://git.elphel.com/Elphel/vdt-plugin|VDT plugin] has to be installed first (imported to the workspace and set up). The Eclipse FPGA workspace is created with the following command issued from the elphel393 project directory:

@@ Line 66: / Line 66: @@
 ==Initializing Eclipse Workspace for Existing (Cloned) Projects==
 After running '''setup.py''' for the first time you may create the brand new workspace for Eclipse, that should have all necessary plugins (such as CDT and EGit at least) already installed. Workspace is created with '''setup_eclipse.py''' script, list of projects that it sets up is saved in '''setup_eclipse_paths.xml''' file. '''setup_eclipse.py''' provides usage information when launched without parameters, for normal run it requires full path to Eclipse installation - directory that contains '''eclipse''' executable and '''eclipse.ini''' configuration. Before running '''setup_eclipse.py''' Eclipse should have all the required plugins installed (at least CDT and EGit) using temporary workspace.
 '''setup_eclipse.py''' performs 2 actions:
@@ Line 72: / Line 74: @@
 After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.
 ==Setting up New Project==

@@ Line 91: / Line 91: @@
   File:Eclipse ccpp build behavior.png| Figure 2b. C/C++ Build ⇒ Behavior<br/>uncheck '''Clean''' and for '''Build (Incremental build)''' enter '''-c compile -f'''
   File:Eclipse ccpp build refresh.png| Figure 2c. C/C++ Build ⇒ Refresh Policy<br/>Keep fields in default state
-  File:Eclipse source location.png| Figure 2d. C/C++ General ⇒ Paths and Symbols ⇒ Source Location<br/>Initially just the project root path will appear there. You will need to add path to '''src''' subdirectory, then remove initial one (project root).<br/>The second entry will appear after you close Eclipse, run '''scripts/used_files.py sysroots''' and then re-open Eclipse. Some projects require different parameters instead of '''sysroots''': linux kernel development need '''linux''', PHP extension requires 'php'.
+  File:Eclipse source location.png| Figure 2d. C/C++ General ⇒ Paths and Symbols ⇒ Source Location<br/>Initially just the project root path will appear there. You will need to add path to '''src''' subdirectory, then remove initial one (project root).<br/>The second entry will appear after you close Eclipse, run '''scripts/used_files.py sysroots''' and then re-open Eclipse. Some projects require different parameters instead of '''"sysroots"''': linux kernel development needs '''"linux"''', PHP extension requires '''"php"'''.
 </gallery>