Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 3 FirstFirst 123
Results 21 to 27 of 27
  1. #21
    jvromans@squirrel.nl
    Guest

    LMS for Windows using Strawberry Perl

    On Thu, 3 Feb 2022 12:24:44 +0000, ralphy
    <ralphy.af9sxb (AT) no-mx (DOT) forums.slimdevices.com> wrote:

    > I tried looking into ChordPro in the beginning but it appears to be a
    > dead project, or perhaps, they've just moved development.


    ChordPro is alive and kicking ever since its conception in 1991. But there
    have been many chordpro-like projects and, indeed, many of them stalled.

    I took over the original ChordPro (called 'chord') many years ago and
    kept it going under the name 'chordii'. See
    https://www.chordpro.org/chordpro/chordpro-history/ .

    A number of years ago we started a total rewrite, in Perl, and this is very
    alive. Rapid development and an active user group.

    > Please correct me if I'm mistaken.


    You're welcome.

    Sorry for the missing link. Apparently only part of the URL was correctly
    cut/pasted. Here is a new one:
    https://github.com/ChordPro/chordpro...-2-msw-x64.exe

    -- Johan

  2. #22
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,715

    LMS for Windows using Strawberry Perl

    > 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.


    Good plan.

    > 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.


    I'm not sure I understand. As you might know the buildme.pl is
    cross-platform. On Windows whomever started the work decided to base it
    on cygwin, maybe just for the availability of all the same tools needed.
    Are you using the same Strawberry Perl to run the script as you use for
    LMS? Unless we want to move the 32 bit build to the same architecture
    (getting rid of ActiveState tools), I'd like to keep the current
    pipeline, as otherwise we'd have to tweak it even more to cover the two
    different builds.

    But maybe I'm overthinking this, and it actually doesn't really matter
    much whether we use cygwin or the tools you're using. As long as there's
    Perl, rsync and all the other tools, it should probably run just fine in
    both environments? Or are the paths a problem?


  3. #23
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,715

    LMS for Windows using Strawberry Perl

    > All sources and required changes are available in
    > https://github.com/ralph-irving/slimserver-vendor-win64 and
    > https://github.com/ralph-irving/slimserver-win64


    Why didn't you fork the repositories?... this way it'll be much harder
    to merge them. The two repositories could easily get out of sync...

  4. #24
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,715

    LMS for Windows using Strawberry Perl

    >> All sources and required changes are available in
    >> https://github.com/ralph-irving/slimserver-vendor-win64 and
    >> https://github.com/ralph-irving/slimserver-win64

    >
    > Why didn't you fork the repositories?... this way it'll be much harder
    > to merge them. The two repositories could easily get out of sync...


    I wanted to see the differences in Slim::Utils::OS::Win32 you applied -
    but it's not easy with this setup to diff them. Would it make sense to
    have a Win64 module or similar?

  5. #25
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    3,011
    Quote Originally Posted by mherger View Post
    > 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.


    Good plan.
    Great that's settled. I can move forward now, no more compiled exes for windows.

    Quote Originally Posted by mherger View Post
    > 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.[/color]

    I'm not sure I understand. As you might know the buildme.pl is
    cross-platform. On Windows whomever started the work decided to base it
    on cygwin, maybe just for the availability of all the same tools needed.
    Are you using the same Strawberry Perl to run the script as you use for
    LMS? Unless we want to move the 32 bit build to the same architecture
    (getting rid of ActiveState tools), I'd like to keep the current
    pipeline, as otherwise we'd have to tweak it even more to cover the two
    different builds.
    Yes, I'm fully aware of the fact that buildme.pl is cross platform. I've added the win64 build type to it.

    I don't see any reason to move the 32bit build. I would think that at some point we would stop providing the AS 32bit builds, since the PDK is no longer supported.
    In my mind the win32 bit build would eventually be retired. How many 32bit windows 10+ installs are there. You've already stopped provide the windows 32bit spotty helper.

    Quote Originally Posted by mherger View Post
    But maybe I'm overthinking this, and it actually doesn't really matter
    much whether we use cygwin or the tools you're using. As long as there's
    Perl, rsync and all the other tools, it should probably run just fine in
    both environments? Or are the paths a problem?
    I agree that it shouldn't matter. But if I'm going to change to the cygwin tools, it should be as close as possible to the version on the current build system.
    I've been bitten too many times, by changes to newer versions of tools that break what had been works great for years. Trying to track down what's changed is often a PITA.

    Quote Originally Posted by mherger View Post
    > All sources and required changes are available in
    > https://github.com/ralph-irving/slimserver-vendor-win64 and
    > https://github.com/ralph-irving/slimserver-win64


    Why didn't you fork the repositories?... this way it'll be much harder
    to merge them. The two repositories could easily get out of sync...
    I did this because the main repo is huge and all I need right now is the windows specific binaries and modules.

    I merge the changes from the official repo about once a week, unless, you've applied a lot of changes, then I do it more often.
    It's easy to export my repository and merge it into a branch of the official repo, I've done it many times in the past for other projects.
    I will do this when we're close to a working solution so I can create the pull request.
    Last edited by ralphy; 2022-02-05 at 04:49.
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 2-UE Radio
    Squeezebox client builds donations always appreciated.

  6. #26
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,715

    LMS for Windows using Strawberry Perl

    > In my mind the win32 bit build would eventually be retired. How many
    > 32bit windows 10+ installs are there. You've already stopped provide
    > the windows 32bit spotty helper.


    Correct. I don't have reliable data, unfortunately. But when I look at
    LMS 8.x checking for updates it's about 20:1 for 64 bit vs. 32 bit.
    Unfortunately many of those running 32 bit _could_ use 64 bit, but don't
    for whatever reason.

    > I agree that it shouldn't matter. But if I'm going to change to the
    > cygwin tools, it should be as close as possible to the version on the
    > current build system.
    > I've been bitten too many times, by changes to newer versions of tools
    > that break what had been works great for years. Trying to track down
    > what's changed is often a PITA.


    Interesting. I think I've never encountered any issue with the little we
    use in buildme.pl. But I haven't been using cygwin on a daily basis for
    a long time. I'm not working in a MS world any more.


  7. #27
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    3,011
    Quote Originally Posted by mherger View Post
    Correct. I don't have reliable data, unfortunately. But when I look at
    LMS 8.x checking for updates it's about 20:1 for 64 bit vs. 32 bit.
    Unfortunately many of those running 32 bit _could_ use 64 bit, but don't
    for whatever reason.
    Once we have a working 64bit windows package, creating a 32bit strawberry perl variant should be easy.

    Quote Originally Posted by mherger View Post
    Interesting. I think I've never encountered any issue with the little we
    use in buildme.pl. But I haven't been using cygwin on a daily basis for
    a long time. I'm not working in a MS world any more.
    For me, this is a general rule, not windows specific.
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 2-UE Radio
    Squeezebox client builds donations always appreciated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •