Testing Revised Plugin on PicorePlayer - how best to proceed

I have been playing around with the old Inguz DSP plugin and re-wrote
the UI a couple of years ago. I have now rebuilt the executables using
.Net 5 which means I can build as a standalone exe for pretty much any
platform.

I managed to get it all running on picoreplayer this weekend, but it has
all disappeared now I have done a reboot, I understand the reasons for
that, but really looking for some advice as to the best strategy for
installing on a pi

The exe is quite chunky at about 20 MB as it contains all the .Net
libraries required.
and currently installs here
/usr/local/slimserver/Bin/armhf-linux

The plugin, with all the perl and web pages currently installs to a
Plugins directory here
/usr/local/slimserver/Plugins.

logging/settings and temp folder are here
/usr/share/InguzEQ

1) I could package the whole lot up as a fresh plugin - would that
persist beyond a reboot and can you point me in the direction of the
current docs.
2) I could just create symlinks for the folders and the additional
couple of files - is that advisable.

Ultimately I want to re-name the plugin and maybe replace the core
engine as Pi performance is a bit limiting (dropouts at 96 K and higher
and gaps between tracks)


------------------------------------------------------------------------
foxesden's Profile: http://forums.slimdevices.com/member.php?userid=56286
View this thread: http://forums.slimdevices.com/showthread.php?t=116054