Re: Let's get a new release out in the next week
Geoff Westcott via xmltv-devel <[email protected]> Wed, 22 Feb 2023 15:33:54 +0000
| Newsgroups | gmane.comp.tv.xmltv.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 22 Feb 2023 15:05:26 +0000, Nick Morrott wrote: > On Wed, 22 Feb 2023 at 13:17, Geoff Westcott via xmltv-devel > <[email protected]> wrote: [...] > > I think I've fixed the build failures now. (Something else I forgot!) > > That explains why I couldn't push earlier. I'll rebase my other changes on top. > > Is there a reason for the lowercase readme.win32 versus its previous > name README.win32? Just to make it stand out less. > In terms of which README content is displayed on the Github docs/ > page, I think that Github is doing a case-insensitive search in the > docs directory for README files, and the win32 variant searches first. > If it was removed, (I thtink) the win64 README would be displayed by > default. Perhaps the 32-bit info could be added to the README.win64 > file to simplify things? Could the README be given a more neutral > Windows extension? README.win? Yep that works. And solves the which-one-displayed issue. Nothing in my research suggests there's a way to select from multiple versions, so combining them into a single README.win is probably best. (I just tested this on my fork and a single README.win displays fine.) > I think Robert's suggestion of automating 32-bit builds is worth > exploring, if there is a need. It is clearly beneficial for end-users > to provide up-to-date versions on as many platforms as possible. My > only question is whether there are users out there in 2023 still > running 32 bit Windows? [FX: waves] Hello! (although to be fair it's mostly just a VBox host nowadays) GH Actions only have W64 runners - can the 32-bit Win exe be built on a 64-bit machine? Cheers, Geoff