Building .so on target - Revision history

Logmanoriginal: Add additional categories

2024-08-06T17:01:26Z

Add additional categories

← Older revision		Revision as of 17:01, 6 August 2024
Line 41:		Line 41:

	[[Category:LabVIEW for Linux]]		[[Category:LabVIEW for Linux]]
			[[Category:BeagleBoard]]
			[[Category:Raspberry Pi]]

Logmanoriginal: Mark as stub, mark for wikification, add to LabVIEW for Linux category

2024-08-06T16:59:25Z

Mark as stub, mark for wikification, add to LabVIEW for Linux category

← Older revision		Revision as of 16:59, 6 August 2024
Line 1:		Line 1:
			{{stub}}{{wikify}}
	== Build .so On Target ==		== Build .so On Target ==
	The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allows the LV run-time to be installed and run safely on many different Linux operating systems. Shared objects must be built to run inside the chroot to be accessible from LabVIEW. The easiest way to ensure the shared object is built correctly is to build it inside the chroot on the target.		The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allows the LV run-time to be installed and run safely on many different Linux operating systems. Shared objects must be built to run inside the chroot to be accessible from LabVIEW. The easiest way to ensure the shared object is built correctly is to build it inside the chroot on the target.
Line 38:		Line 39:
	=== Debugging ===		=== Debugging ===
	The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.		The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.

			[[Category:LabVIEW for Linux]]

NegentropicDev: Added additional dependencies for linx target library building

2021-05-25T14:13:12Z

Added additional dependencies for linx target library building

← Older revision		Revision as of 14:13, 25 May 2021
Line 9:		Line 9:
	''Note that all of the following commands until exiting the chroot must be run inside the chroot or they will fail.''		''Note that all of the following commands until exiting the chroot must be run inside the chroot or they will fail.''
	3. Install the build tools:		3. Install the build tools:
	* ~~sudo~~ opkg update		* opkg update
	* ~~sudo~~ opkg install packagegroup-core-buildessential		* opkg install packagegroup-core-buildessential

	4. Optionally install git and gdb:		4. Optionally install git and gdb:
	* ~~sudo~~ opkg install git		* opkg install git
	* ~~sudo~~ opkg install gdb		* opkg install gdb

	5. Build the .so		5. If building updated versions of the Linx target libraries, install the additional development dependencies:
			* opkg install --force-depends libc6-dev
			* opkg install --force-depends libgcc-s-dev
			* opkg install libstdc++-staticdev

			6. Build the .so

	The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.		The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.

NegentropicDev at 00:16, 8 July 2020

2020-07-08T00:16:43Z

← Older revision		Revision as of 00:16, 8 July 2020
Line 19:		Line 19:

	The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.		The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.
	Copy the .so to /usr/lib.
			6. Copy the .so to /usr/lib.<br>
	Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.		Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.

	6. Call the .so from LabVIEW using the Call Library Function Node<br>		7. Call the .so from LabVIEW using the Call Library Function Node<br>
	Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.<br>		Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.<br>
	Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.<br>		Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.<br>

	7. Exit the chroot		8. Exit the chroot
	* exit		* exit

NegentropicDev at 00:16, 8 July 2020

2020-07-08T00:16:13Z

← Older revision		Revision as of 00:16, 8 July 2020
Line 22:		Line 22:
	Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.		Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.

	6. Call the .so from LabVIEW using the Call Library Function Node		6. Call the .so from LabVIEW using the Call Library Function Node<br>
	Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.		Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.<br>
	Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.		Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.<br>
	Exit the chroot
	exit		7. Exit the chroot
	Debugging		* exit


			=== Debugging ===
	The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.		The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.

NegentropicDev: Created page with "== Build .so On Target == The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allow..."

2020-07-08T00:15:30Z

Created page with "== Build .so On Target == The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allow..."

New page

== Build .so On Target ==
The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allows the LV run-time to be installed and run safely on many different Linux operating systems. Shared objects must be built to run inside the chroot to be accessible from LabVIEW. The easiest way to ensure the shared object is built correctly is to build it inside the chroot on the target.

1. SSH into the target as a user with root privileges.

2. Run the following command to enter the chroot:
* sudo schroot --run-session -c lv

''Note that all of the following commands until exiting the chroot must be run inside the chroot or they will fail.''
3. Install the build tools:
* sudo opkg update
* sudo opkg install packagegroup-core-buildessential

4. Optionally install git and gdb:
* sudo opkg install git
* sudo opkg install gdb

5. Build the .so

The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.
Copy the .so to /usr/lib.
Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.

6. Call the .so from LabVIEW using the Call Library Function Node
Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.
Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.
Exit the chroot
exit
Debugging
The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.