Re: LMS for Windows using Strawberry Perl

mherger wrote: 
> No. I'm even open to dropping all the helpers.
Thanks.  I'll keep that in mind going forward.

mherger wrote: 
> "you have to install Perl" might scare people away. I think that really
> 
> is it.
> 
> So I was wondering whether we could have two installers: the "full" 
> version bundling Strawberry Perl with LMS. And the LMS only installer 
> (used in updates), only installing the LMS code. I haven't looked into 
> Strawberry Perl's licensing and what not. Just an idea.

I'd been thinking along those lines as well.

But if we have 2 installers, why not just install the official
strawberry perl msi once as MrC has identified from experience?

The LMS installer should be able to be changed to handle the dependency
and install perl if it's not there, keeping in mind that we will be tied
to a specific version of SB Perl, just like Linux.

mherger wrote: 
> > 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.[/color]
> 
> What's the licensing model there?

Yes, I am aware of possible licensing issues, not specifically with the
NSSM, but in general.  It's always a concern, but I've not investigated
any of that yet.


mherger wrote: 
> If I may say so... I'd prefer you to work on a simple, stable 
> installation procedure leveraging raw Strawberry Perl, than wasting time
> 
> trying to figure out the issues with building binaries.

Yes of course.   I'd appreciate your direction as we move along.

mherger wrote: 
> Great! An they would only be include once, not once per binary!
> 
> I know that you don't use Cygwin. But how are the chances that the build
> 
> process would still work with Cygwin? It would be great if I didn't have
> 
> to maintain another build host...

Currently, I just add the unix util folder location to the PATH before
running buildme.  I only have the commands needed for buildme to
success, it's only 9MB, no installer, no extra cruft.

However, I have no issues with moving to as close as possible to the
current win32 build system.  In which case it would be helpful to have
the version details for all the tools, sans the PDK of course.

mherger wrote: 
> Oh, one more thing: do you have your WIP code somewhere in a git
> repository?
I've added a link in the first post to the platform wip sources.



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