Posts by heitbaum

Mr.Tiptop - librespot has been added back to the x86 Generic repository - FYI

It should be there now

librespot 10.0.0 124

You will need to add the addon - but will be in the addons list.

For Jellyfin there is a Addon that is close to release - just tidy it up the user interface, icons, …. But is fully functional against current.

Jellyfin: add new addon package by heitbaum · Pull Request #5488 · LibreELEC/LibreELEC.tv · GitHub

_fdc_ the build issues have been fixed. The addon should be available for download in the next few days.

HWTest - I have raised a bug [BUG] libraw image decoder not working · Issue #5524 · LibreELEC/LibreELEC.tv · GitHub - missing library issue. Will look at it. Identified another issue with libraw in my dev tree, so will try and fix both at the same time.

Fix queued up: imagedecoder.raw: link against static lcms2 by heitbaum · Pull Request #5525 · LibreELEC/LibreELEC.tv · GitHub

_fdc_ there are build issues with it on Generic - Update rust resolving TARGET=HOST build issues by heitbaum · Pull Request #5446 · LibreELEC/LibreELEC.tv · GitHub.

Grab the zip from here - LibreELEC.tv/10.0.0-Generic-x86_64-service.librespot-10.0.0.128.zip at librespot-bin · heitbaum/LibreELEC.tv · GitHub

Or self build it: LibreELEC.tv/10-build.sh at librespot-bin · heitbaum/LibreELEC.tv · GitHub

Hi Anewmission you will find mpd in the addons: services.multimedia. Version 0.22.9 is there LibreELEC.tv/packages/addons/service/mpd at master · LibreELEC/LibreELEC.tv · GitHub let us know how you go.

Excellent. Glad you have got it working 👍

nvdias any reason not to use ffmpegx? The Jellyfin PR that is is using ffmpegx and essentially does the same (but more)?

Hi nickybee123 search for H616 in the forums. Search Results - LibreELEC Forum

There is work going on to support the H616 in mainline Linux and uboot (in fact I have a TX6s running Linux - one of my many projects …). Linux mainlining effort - linux-sunxi.org - still a wile off for LE though.

Quote from nuive

Hi again,

I'm having a new problem related to the addition of Speech Dispatcher.

When building it, it checks for additional Voice TTSs and if it finds them, it adds the respective modules.

I'm trying to generate the eSpeak Module, but it needs the espeak library for the process, so I added espeak:host as a dependency.

The eSpeak package wasn't able to generate host builds, so I edited it and could add the eSpeak libraries and include headers to the toolchain. However, when trying to build Speech Dispatcher with espeak support it says that file <espeak/speak_lib.h> does not exist, but the file speak_lib.h is inside $TOOLCHAIN/include/espeak.

It seems that the build process is ignoring the toolchain paths, even if toolchain is in the package.mk as a target dependency.

My current package.mk:

--------------------

Code

PKG_NAME="speech-dispatcher"
PKG_VERSION="0.10.2"
PKG_SHA256="b06319f201e15e56c6296653af5bcfc300cb348e972d517df8b06eac77eae2dc"
PKG_LICENSE="LGPL"
PKG_SITE="https://freebsoft.org/speechd"
PKG_URL="https://github.com/brailcom/speechd/releases/download/$PKG_VERSION/$PKG_NAME-$PKG_VERSION.tar.gz"
PKG_DEPENDS_TARGET="toolchain glib dotconf libsndfile libpthread-stubs libtool alsa-lib pulseaudio espeak:host"
PKG_LONGDESC="Common high-level interface to TTS"
PKG_TOOLCHAIN="autotools"


PKG_CONFIGURE_OPTS_TARGET="$PKG_CONFIGURE_OPTS_TARGET \
ac_cv_func_realloc_0_nonnull=yes \
ac_cv_func_malloc_0_nonnull=yes"

Display More

Can you share espeak/package.mk

Target depends on target generally.

…

Hypothetically…

Bob is a program that builds a file called bill.txt.

We want to use bill.txt as part of our build process for james.

E.g. cc -o james bill.txt James.c

Then bob:host makes sense… as “bob.exe” needs to run on you build host as a program to create bill.txt.

One of our examples would be cmake:host

cmake:target does not make sense - as when you are running LE10 on your RPi4 - you don’t want to run cmake. You only want to run cmake on the build host.

So if “espeak:host” is a program that generates abc.tts, bcd.tts - then espeak:host makes sense - on the build host.

If espeak:host builds a library called espeak.lib that is being used by speech-distpacher… e.g. cc -o speech-dispatcher speech-dispatcher.c -lespeak - this is INCORRECT using espeak:host … It should be espeak:target (which is the same as espeak.)

Ping me back on how you go.

--------------------

Display More

Glad you got it all going 👍

You will want to remove the manual TOOLCHAIN and the pre_make

Try with:

PKG_TOOLCHAIN="autotools"

The build system does most of the hard work (most of the time)

Suggest you start with the below.

git diff HEAD
diff --git a/packages/audio/speech-dispatcher/package.mk b/packages/audio/speech-dispatcher/package.mk
new file mode 100644
index 0000000000..b1f786ea96
--- /dev/null
+++ b/packages/audio/speech-dispatcher/package.mk
@@ -0,0 +1,8 @@
+PKG_NAME="speech-dispatcher"
+PKG_VERSION="0.10.2"
+PKG_SHA256="b06319f201e15e56c6296653af5bcfc300cb348e972d517df8b06eac77eae2dc"
+PKG_LICENSE="LGPL"
+PKG_SITE="https://freebsoft.org/speechd"
+PKG_URL="https://github.com/brailcom/speechd/releases/download/${PKG_VERSION}/${PKG_NAME}-${PKG_VERSION}.tar.gz"+PKG_DEPENDS_TARGET="toolchain libsndfile libpthread-stubs"
+PKG_LONGDESC="Common high-level interface to TTS"

docker@d0b5f6c68aed:/var/media/DATA/home-rudi/LibreELEC.tv$ scripts/build speech-dispatcher

which will error with the following. Only add dependancies to packages that you error on or you want the package compiled against. E.g. if you don’t want to use the h264 codec in a video app, then don’t include it … etc.

checking pkg-config is at least version 0.9.0... yes
checking for glib-2.0 >= 2.36... yes
checking for gthread-2.0... yes
checking for gmodule-2.0... yes
checking for dotconf >= 1.3... no
configure: error: Package requirements (dotconf >= 1.3) were not met:

No package 'dotconf' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables DOTCONF_CFLAGS
and DOTCONF_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
FAILURE: scripts/build speech-dispatcher during configure_target (default)
*********** FAILED COMMAND ***********
${PKG_CONFIGURE_SCRIPT} ${TARGET_CONFIGURE_OPTS} ${PKG_CONFIGURE_OPTS_TARGET}
**************************************

As you are not developing a package that you need during the build process, all of your packages should be targets. And that is the default. So no need to use :host or :target for your development.

If for example you needed to use the “mkimg” program to build a package “mkimg” because onnof the steps in building “mkimg” properly is to creat some images, and that uses the newly compiled “mkimg” program. You will need to compile both a host and target “mkimg”. Host to create you images, and target to run on your RPi.

If you don’t need the mkimg program on your RPi, then you would only build mkimg:host.

Hope that helps.

Examples are cmake is a host only build.

Hi nuive - probably not the best example to start with. glib is a package that builds for both the host that does the build and the target (your RPi3)

In the case of your xxxx:host question - python:host is built “for the host” to be able to build glib.

In your glib example - lib would be a dependency (on the RPi3 for your app)

What application are you trying to package, might be able to give you some pointers on a package.mk to start with.

Quote from bkuhls

Please test current media-driver: Rocket Lake (RKL) discussion

bkuhls - I have updated to 29d5f8f and no issues so far NUC11 i7 TGL

PR raised. mpd: update to 0.22.9 and addon (111) by heitbaum · Pull Request #5459 · LibreELEC/LibreELEC.tv · GitHub