sodface wrote: > One follow on question for you, when you say "the last build I did" and > then provide the list of source tarballs, do you mean that you used the > slimserver-vendor buildme.sh script with those updated sources or did > you build them some other way that didn't rely on any lms related > scripts? > slimserver-vendor buildme.sh (patched for new versions)
> > Or asked another way, is there some difference between building a module > against the OS installed perl version using the LMS buildme.sh script > and just using the same module if it's available in the repos? > Yes there is. Take e.g. Image::Scale, which depends on libjpeg-turbo (and other pkgs). The buildme script will build a static version of libjpeg-turbo and then Image::Scale, which will link against this static library (and libjpeg-turbo never gets installed). A system package of Image::Scale will depend on libjpeg-turbo being installed, and Image::Scale will link against the shared library of libjpeg-turbo in /usr/lib. > > I'm fairly confident I can at least get a working LMS for myself to use, > I'd prefer it be built with newer perl and module versions (just > because). > There are definitely performance/stability/security improvements with certain upgrades (perl, SQLite, libjpeg, libpng). While we'are at this topic: Check if your CFLAGS include the optimizations for your platform (or at least -O2 -march=native (which may be suboptimal depending on your gcc version's support for your plarform)) For pi3 / aarch64 I use -march=armv8-a+crc -mtune=cortex-a53 -O2 > > I can probably also manually assemble a package for it just to make it > easier to install and share. Making an APKBUILD so that the build > system can build the package is probably not worth the effort if I could > even get it working. Seems a self contained LMS package with its' own > perl and modules bundled with it and installed outside of the normal > system perl path might be the right way to go. > Writing the APKBUILD to automate the steps to build/install LMS (d/l sources + support files (init scripts etc.), run buildme.sh, create user, install files etc) wouldn't be that much of an effort if you are exploring how to get it to build/run anyway (it's just a shell script after all). That way, you (or any user, really) could run the apk build locally for your perl/arch (provided they have installed the build env). This would make installing / upgrading / removing) rather simple. You could then make the APKBUILD file available for d/l if there's demand, but not the resulting binary package. That being said, I couldn't be bothered to do this for Gentoo myself, so there's that... 'Various SW' (https://www.nexus0.net/pub/sw/): Web Interface | Playlist Editor / Generator | Music Classification | Similar Music | Announce | EventTrigger | LMSlib2go | ... 'Various HowTos' (https://www.nexus0.net/pub/documents/LMS/): build a self-contained LMS | Bluetooth/ALSA | Control LMS with any device | ... ------------------------------------------------------------------------ Roland0's Profile: http://forums.slimdevices.com/member.php?userid=56808 View this thread: http://forums.slimdevices.com/showthread.php?t=111401 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
