Information for Developers - Revision history

40H3X: /* Create your own build */

2026-09-08T11:52:57Z

‎Create your own build

2026-08-09T14:34:06Z

2026-08-09T14:33:34Z

2026-08-09T14:30:38Z

2026-06-10T16:20:29Z

‎OOM killer kicks in

2026-06-10T16:19:08Z

‎OOM killer kicks in

2026-06-10T16:15:51Z

‎OOM killer kicks in

2026-06-10T16:13:29Z

2026-06-10T16:12:49Z

2026-06-10T14:06:39Z

‎Setup the OpenPli environment

@@ Line 55: / Line 55: @@
     coreutils unzip texi2html texinfo docbook-utils \
     gawk python3-distutils diffstat help2man make gcc build-essential g++ \
-    desktop-file-utils chrpath default-jre gettext zip libssl-dev lz4 libproc-processtable-perl
+    desktop-file-utils chrpath default-jre gettext zip libssl-dev lz4 libproc-processtable-perl rpcsvc-proto
 You may need to create a symlink makeinfo->texi2any (in the bin folder) and a symlink makeinfo->/bin/texi2any in the hosttools folder.

← Older revision		Revision as of 14:34, 9 August 2026
Line 1:		Line 1:
−	==''''I'm a developer, is there any technical info available from the PLi® team?'''==	+	=='''I'm a developer, is there any technical info available from the PLi® team?'''==
	Yes and welcome aboard!		Yes and welcome aboard!

@@ Line 6: / Line 6: @@
 This page is about software development using OpenEmbedded-core. If you're looking for the text that used to be on the this page, it's now called developer-information-old.
 =='''Create your own build'''==
 See also this forum post on setting up a development environment: [http://openpli.org/forums/topic/18806-openpli-quick-setup-ubuntudebian/<span style="color:SteelBlue">http://openpli.org/forums/topic/18806-openpli-quick-setup-ubuntudebian/</span>]

@@ Line 1: / Line 1: @@
 ==''''I'm a developer, is there any technical info available from the PLi® team?'''==
-Welcome and tell your developer friends about us
+Yes and welcome aboard!
-Yes and welcome aboard! If you have specific question, you can use our PLi® Third Party Development forum to ask it. You will find we are most accommodating.
+If you have specific question, you can use our PLi® Third Party Development forum to ask it. You will find we are most accommodating.
 This page is about software development using OpenEmbedded-core. If you're looking for the text that used to be on the this page, it's now called developer-information-old.

@@ Line 140: / Line 140: @@
 ===OOM killer kicks in===
-If your OOM killer kicks in during the build process, you can limit the memory use by editing ./openpli-oe-core/build/conf/openpli.conf. The build process takes as much processes as you have cores, say you'll habe 16GB, and when a process takes 2GB and you have 8 cores you will run out.
+If your OOM killer kicks in during the build process, you can limit the memory use by editing ./openpli-oe-core/build/conf/openpli.conf. The build process takes as much processes as you have cores, say you'll have 16GB, and when a process takes 2GB and you have 8 cores you will run out.
    # by default limit based on number of CPU threads

@@ Line 140: / Line 140: @@
 ===OOM killer kicks in===
-If you OOM killer kicks in during the build process, you can limit the memory use by editing ./build/conf/openpli.conf. The build process takes as much processes as you have cores, so if a process takes 2GB and you have 8 cores you needs 16GB
+If your OOM killer kicks in during the build process, you can limit the memory use by editing ./openp[li-oe-core/build/conf/openpli.conf. The build process takes as much processes as you have cores, say you'll habe 16GB, and when a process takes 2GB and you have 8 cores you will run out.
    # by default limit based on number of CPU threads
@@ Line 150: / Line 150: @@
    PARALLEL_MAKE:pn-qtwebengine = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
    PARALLEL_MAKE:pn-nodejs = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
    PARALLEL_MAKE:pn-chromium = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
 =='''Your own feed server'''==

@@ Line 138: / Line 138: @@
 Note that if your cache is old, this may take a long time, as on our buildserver (which does build all images!) the result after a second build run is "1385449 out of 1682374 files will be removed!"
 =='''Your own feed server'''==
@@ Line 158: / Line 174: @@
 After this, if you run a new image build, it will make the /etc/opkg/ files on the box point to your feed. After installing the built image on your box, you should be able to upgrade with opkg commands or the enigma2 GUI.

← Older revision		Revision as of 16:12, 10 June 2026
Line 158:		Line 158:

	After this, if you run a new image build, it will make the /etc/opkg/ files on the box point to your feed. After installing the built image on your box, you should be able to upgrade with opkg commands or the enigma2 GUI.		After this, if you run a new image build, it will make the /etc/opkg/ files on the box point to your feed. After installing the built image on your box, you should be able to upgrade with opkg commands or the enigma2 GUI.
		+
		+	===OOM killer kicks in===
		+	If you OOM killer kicks in during the build process, you can limit the memory use by editing ./build/conf/openpli.conf. The build process takes as much processes as you have cores, so if a process takes 2GB and you have 8 cores you needs 16GB
		+
		+	# by default limit based on number of CPU threads
		+	BB_NUMBER_THREADS = "${@min(len(os.sched_getaffinity(0))-2,18)}"
		+	PARALLEL_MAKE = "-j ${@min(len(os.sched_getaffinity(0))-4,10)}"
		+
		+	# limit parallel make for these packages to prevent OOM issues
		+	PARALLEL_MAKE:pn-kodi = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
		+	PARALLEL_MAKE:pn-qtwebengine = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
		+	PARALLEL_MAKE:pn-nodejs = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
		+	PARALLEL_MAKE:pn-chromium = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
		+
		+

	==='''No real webserver handy?'''===		==='''No real webserver handy?'''===

@@ Line 74: / Line 74: @@
    make update
-Also you can try the new scarthgap branch
+The make init creates the conf files (maybe you want to edit them). Also you can try the new scarthgap branch
 - go to openpli-oe-core dir.