Re: LMS for Windows using Strawberry Perl

I'd like to revisit providing separate par-packer compiled binaries for
each component.

Is it necessary?  What benefit does it provide over bundling a copy of
the portable strawberry perl within the lms installer and running from
the source?
You can move/rename the perl directory and it will still work, so perl
can be installed within the C:\program files\Squeezebox folder
structure.
Setting up lms as a windows service works using 'NSSM'
(https://nssm.cc/) running perl.exe, slimserver.pl and parameters
directly in the service definition.

Having perl and sources available on windows would bring the release in
line with the other release flavours and allow code changes for
troubleshooting issues.

So far, I've found the par-packer build process fragile and debugging
crashes extremely tedious.  A crash usually happens in a dll and only
reported with a name that a hex number.dll.  You then have to find it in
the par-cache temp folder, search the strings within the dll to
determine which perl module/component it's related.

I can continue with the compiled binary builds but I'm not sure it the
best option for the future.

I'd appreciate your thoughts on moving to a source based release.  The
lms sources would still be stripped down to only what's needed for
windows.

Thanks.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *2*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.
------------------------------------------------------------------------
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=115740