Using Yocto/ELBE SDK for application development - Revision history

Pzimmermann: Reworked the structure of the SDK + minor error correction

2020-06-29T14:42:28Z

Reworked the structure of the SDK + minor error correction

← Older revision		Revision as of 16:42, 29 June 2020
Line 1:		Line 1:
	'''<big>This site is under construction!</big>'''		'''<big>This site is under construction!</big>'''

	Root filesystems made by Yocto and ELBE can come with a SDK to build applications for the rootFS.		Root filesystems made by Yocto and ELBE can each come with a SDK to build applications for the rootFS.

	__TOC__		__TOC__
Line 7:		Line 7:
	== Installation ==		== Installation ==

	~~To install~~ the SDK ~~the following packets have to be installed on the machine~~:		The following packages are required for the installation of the SDK:
	* xz-utils		* xz-utils
	* file		* file
Line 16:		Line 16:
	== Using the SDK ==		== Using the SDK ==

	The ~~SDK consists~~ of two parts:		The main structure between the SDKs of Yocto and ELBE is very similar, these consist of two parts:
	* A folder with two ~~sysroots~~		* A folder "sysroots" with two subfolders:
	** ~~"host":~~ In ~~this folder~~ are the programms for the development host for using the SDK (e.g. compiler, debugger, ...).		** In one of the folders are the programms for the development host for using the SDK (e.g. compiler, debugger, ...). In Yocto this folder has the name of the development host archictecture and "sdk" in it. In ELBE this folder is usually called "host".
	** ~~"target": This sysroot~~ contains headers and libraries needed by the linker to build applications for the rootFS.		** The second folder contains headers and libraries needed by the linker to build applications for the rootFS. In Yocto this folder has the name of the target archictecture in it. In ELBE this folder is usually called "target".
	* A file with environment variables to setup the build environment (sourcing this file sets variables like ${CC} or ${LD})		* A file with environment variables to setup the build environment (sourcing this file sets variables like ${CC} or ${LD}). The name of the file usually starts with "environment-setup-"
			The default installation folder varies between the two tools: Both do install into "/opt/" but Yocto uses two subfolders (one for the distribution name, the other for the version), while ELBE uses only one subfolder.

	~~Folowing~~ are instructions how to use the SDK with different build-systems and IDEs (All examples using an ELBE toolchain installed at "<~~nowiki~~>opt/elbe-sdk-arm-linux-gnueabihf-dhcom-buster-1.0</~~nowiki~~>"):		Following are instructions how to use the SDK with different build-systems and IDEs (All examples using an ELBE toolchain installed at "<tt>/opt/elbe-sdk-arm-linux-gnueabihf-dhcom-buster-1.0</tt>"):

	=== Makefiles ===		=== Makefiles ===
Line 87:		Line 88:
	=== Eclipse ===		=== Eclipse ===

	To use Eclipse with the SDK you have to start a shell and source the environment setup file and then open eclipse through that shell:		To use Eclipse with the SDK you have to start a shell and source the environment setup file and then open eclipse through that shell (note that Eclipse has to be in your PATH, when starting it like in the example):

	<~~nowiki~~>user@machine:~# source /opt/elbe-sdk-arm-linux-gnueabi-dhcom-buster-1.0/environment-setup-elbe-arm-linux-gnueabihf-dhcom-buster-1.0		<tt>user@machine:~# source /opt/elbe-sdk-arm-linux-gnueabi-dhcom-buster-1.0/environment-setup-elbe-arm-linux-gnueabihf-dhcom-buster-1.0
	user@machine:~# eclipse</~~nowiki~~>		user@machine:~# eclipse</tt>

	When creating a new Eclipse project, use "Linux GCC" as the toolchain, the ~~variables set by~~ the environment ~~setup are enough~~.		When creating a new Eclipse project, use "Linux GCC" as the toolchain, the additional settings when selecting "Cross GCC" are conflicting with the environment of the SDK.

	After creating the project open the project settings and go to the section "C/C++ Build -> Settings". Now go to "GCC C Compiler" and set the "Command" to "${CC}".		After creating the project open the project settings and go to the section "C/C++ Build -> Settings". Now go to "GCC C Compiler" and set the "Command" to "${CC}".
Line 106:		Line 107:
	[[File:EclipseAs.png]]		[[File:EclipseAs.png]]

	The toolchain of the SDK con now be used by Eclipse as long Eclipse is not closed. If you want to a toolchain of another SDK you have to close Eclipse and source the environment setup of the other SDK and start Eclipse from that shell.		The toolchain of the SDK con now be used by Eclipse as long Eclipse is not closed. If you want to use a toolchain of another SDK you have to close Eclipse and source the environment setup of the other SDK and start Eclipse from that shell.

	<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">		<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
Line 123:		Line 124:
	To use Visual Studio Code with the SDK you have to start a shell and source the environment setup file and then open Visual Studio Code through that shell:		To use Visual Studio Code with the SDK you have to start a shell and source the environment setup file and then open Visual Studio Code through that shell:

	<~~nowiki~~>user@machine:~# source /opt/elbe-sdk-arm-linux-gnueabi-dhcom-buster-1.0/environment-setup-elbe-arm-linux-gnueabihf-dhcom-buster-1.0		<tt>user@machine:~# source /opt/elbe-sdk-arm-linux-gnueabi-dhcom-buster-1.0/environment-setup-elbe-arm-linux-gnueabihf-dhcom-buster-1.0
	user@machine:~# code</~~nowiki~~>		user@machine:~# code</tt>

	Open a folder as workspace where you have your code.		Open a folder as workspace where you have your code.

Pzimmermann: /* Qt-Creator */

2020-06-26T05:42:26Z

Qt-Creator

← Older revision		Revision as of 07:42, 26 June 2020
Line 72:		Line 72:

	If you want to deploy built software directly onto the embedded device, then change to the section "Devices" and add a new device. Select "Generic Linux Device" and set the IP-address, username and password.		If you want to deploy built software directly onto the embedded device, then change to the section "Devices" and add a new device. Select "Generic Linux Device" and set the IP-address, username and password.

			[[File:QTCreatorDevice.png]]

	Now change back to the section "Build & Run". In the tab "Kits" you have to add a new Kit for the toolchain. Set the compilers, debuggers, Qt and the device to these, which you have defined at the preceding steps. If the SDK does not include Qt you have to set Qt to "None" (like in the example).		Now change back to the section "Build & Run". In the tab "Kits" you have to add a new Kit for the toolchain. Set the compilers, debuggers, Qt and the device to these, which you have defined at the preceding steps. If the SDK does not include Qt you have to set Qt to "None" (like in the example).

Pzimmermann: Added Section for VSCode

2020-06-24T11:42:53Z

Added Section for VSCode

← Older revision		Revision as of 13:42, 24 June 2020
Line 114:		Line 114:

	</div></div>		</div></div>

			===Visual Studio Code===

			If you want to develop in C/C++ you have to install the extension "C/C++" inside Visual Studio Code.

			To use Visual Studio Code with the SDK you have to start a shell and source the environment setup file and then open Visual Studio Code through that shell:

			<nowiki>user@machine:~# source /opt/elbe-sdk-arm-linux-gnueabi-dhcom-buster-1.0/environment-setup-elbe-arm-linux-gnueabihf-dhcom-buster-1.0
			user@machine:~# code</nowiki>

			Open a folder as workspace where you have your code.

			When you want to build your program select "Terminal -> Configure Default Build Task" and choose your appropiate action with gcc. The file "tasks.json" is now generated. After that change the command to the appropiate command (e.g. to "${CC}" if you want to directly use the compiler of the toolchain, or if you use a makefile change it to "make").

			[[File:VSCodeTasks.png]]

			To configure Intellisense for syntax highlighting and finding the headers of libraries, press CTRL + SHIFT + P and select "C/C++: Edit Configurations (JSON)". The file "c_cpp_properties.json" is now generated for this workspace. Here add "${SDKTARGETSYSROOT}/**" to the includePath, set the compilerPath to "${CC}" and set the intelliSenseMode to "gcc-arm". Now save the file and reload the workspace, then Intellisense should find the headers of the SDK.

			[[File:VSCodeIntellisense.png]]

			To run the build, you have to select "Terminal -> Run Build Task" from the menu.

	==External Links==		==External Links==

Pzimmermann: Added section about Eclipse

2020-06-22T10:31:01Z

Added section about Eclipse

@@ Line 80: / Line 80: @@
 [[File:QtCreatorEnv.png|1311px]]
 Now any project in Qt Creator can use the toolchain of the SDK if the kit is selected for the project. If you want to use another SDK-toolchain, you can switch the used kit for the project.
 === Eclipse ===
 ==External Links==

Pzimmermann: Added CMake and Qt Creator

2020-06-22T08:49:00Z

Added CMake and Qt Creator

@@ Line 12: / Line 12: @@
 * patchelf
-Run the setup-script (e.g. setup-elbe-sdk-arm-linux-gnueabihf-dhcom-buster-base-1.0.sh) as root to start the installation.
+Run the setup-script (e.g. setup-elbe-sdk-arm-linux-gnueabihf-dhcom-buster-1.0.sh) as root to start the installation.
 == Using the SDK ==
 The SDK consists of two parts:
-* A sysroot with the compiler, headers and libraries needed to build applications for the rootFS
+* A folder with two sysroots
 * A file with environment variables to setup the build environment (sourcing this file sets variables like ${CC} or ${LD})
-Folowing are instructions how to use the SDK with different build-systems and IDEs:
+Folowing are instructions how to use the SDK with different build-systems and IDEs (All examples using an ELBE toolchain installed at "<nowiki>opt/elbe-sdk-arm-linux-gnueabihf-dhcom-buster-1.0</nowiki>"):
 === Makefiles ===
-Open a shell and source the file with the environment variables.
+Open a shell and source the file with the environment variables:
 Now you can use make to build applications in this shell session.
 '''Important:''' Do not overwrite variables which were set by SDK in the makefile (or call make with '-e' to discard variables set in the makefile).
 === CMake ===
 === Qt-Creator ===
 === Eclipse ===

Pzimmermann: Created page with "'''This site is under construction!''' Root filesystems made by Yocto and ELBE can come with a SDK to build applications for the rootFS. TOC == Installation..."

2020-06-19T11:02:02Z

Created page with "'''<big>This site is under construction!</big>''' Root filesystems made by Yocto and ELBE can come with a SDK to build applications for the rootFS. __TOC__ == Installation..."

New page

'''<big>This site is under construction!</big>'''

Root filesystems made by Yocto and ELBE can come with a SDK to build applications for the rootFS.

__TOC__

== Installation ==

To install the SDK the following packets have to be installed on the machine:
* xz-utils
* file
* patchelf

Run the setup-script (e.g. setup-elbe-sdk-arm-linux-gnueabihf-dhcom-buster-base-1.0.sh) as root to start the installation.

== Using the SDK ==

The SDK consists of two parts:
* A sysroot with the compiler, headers and libraries needed to build applications for the rootFS
* A file with environment variables to setup the build environment (sourcing this file sets variables like ${CC} or ${LD})

Folowing are instructions how to use the SDK with different build-systems and IDEs:

=== Makefiles ===

Open a shell and source the file with the environment variables.

Now you can use make to build applications in this shell session.
'''Important:''' Do not overwrite variables which were set by SDK in the makefile (or call make with '-e' to discard variables set in the makefile).

=== CMake ===

=== Qt-Creator ===

=== Eclipse ===