Hello, Coming back to this thread after a long pause. I have some updates on the system requirements and build requirements that were also sourced from our Chatroom.
Common requirements Conceptually remain unchanged, following primarily the Debian dependency graph. C/C++ runtime libraries are going to be MinGW ones for the time being as there are third-party dependencies that do not have support for MSVC, like libunbound. At the same time, Zash suggested to use MinGW by crosscompiling on Linux CI machines, which is possible. I need to make a Buildbot pipeline for that and submit likely here (or in a new thread) for review. MinGW on Linux allows to build NSIS installers at the same time, so it will be caught up there, too. Windows requirements - Target OS: Windows 11, version 25H2 (client), Windows Server 2025 (server) - Minimum supported OS: Windows 10 "November 2015 Update" (client), Windows Server 2016 (server) All listed operating systems must be x64. Native Windows on ARM theoretically could be supported through the same MinGW toolchains but not for now. x64 will work fine there. x86 versions remain unsupported. Such minimum required OS shift is caused by Windows supporting ANSI VT sequences for long time and *in normal conditions* nobody would want to host a server on an unsupported OS (I would be happy to continue using Windows 8.1 though...), so security considerations come first. Notices on ReactOS They seem to progress with shifting userspace towards NT 6.0 style. Despite that I'm a contributor there, I won't make ReactOS-specific builds. Windows x64 artifacts will serve as a debug suite for this operating system. On Wednesday, 6 September 2023 at 22:28:27 UTC+3 Vitaly Orekhov wrote: > I had made some tests on unpatched Windows Vista SP2 (by unpatched, I mean > *without* the extended kernel). The observations I made had shown that > this system is acceptable to be the bare minimum to run Prosody for > Windows, the current implementation of util.encodings (as in Prosody trunk) > allows to link against libicu (ICU4C) of any version starting with ICU > *58*. Given that, server administrators who want to run Prosody in Vista > or Server 2008 environment, will have to compile Prosody from sources to > fit these conditions. Other libraries do not seem to have strict Windows > specific system requirements (does not apply to LuaDBI plugins for > PostgreSQL, for example) and do not require any special treatment. > The general availability version of Prosody for Windows (the one can be > obtained on Downloads <https://prosody.im/download/> page) *must* follow > the dependency tree that *Debian* releases have. > As a result, I want to show you the system requirements for Windows > version I came up with after dependency review. > > Common requirements > > - Lua: >=5.4 > - OpenSSL: >= 3.0.0 > - libevent: >= 2.1.8 > - libexpat: >=2.4.1 > - libicu: >= 72.1 > - libunbound: >= 1.8.0 > - C/C++ runtime libraries: Visual C++ 2022 > > Windows requirements > > - Target OS: Windows 11, version 22H2 (client), Windows Server 2022 > (server) > - Minimum supported OS: Windows 7 SP1 (client), Windows Server 2008 R2 > SP1 (server) > > All listed operating systems must be x64. x86 versions are not supported. > In future, if volunteers will come, it may expand to ARM64, since Windows > 11 for ARM exists, too. > Information provided here is relevant at the moment of writing and is > subject to change in future, mostly towards newer versions and deprecating > older versions if blocker issues happen. > > Notices on Windows Vista and Server 2008 > > In order to run Prosody for Windows on Vista, Prosody must be built from > sources. Running Prosody on unpatched Vista SP2 is not advised due to > noticeably outdated ICU4C library (58 vs 72), thus extended kernel > installation is highly advised for consistent experience. I have no data > for Server 2008 SP2, so I cannot state clear requirements there. In case of > Vista SP2 *with* extended kernel, all issues happened in this > environment, are covered by warranty, as I maintain this. *Without* the > kernel — sorry, it's too outdated for me, please, use either the extended > kernel or upgrade to newer release of Windows. > > Notices on ReactOS > > Recent build artifacts of ReactOS 0.4.15 feature NT 6.0 subsystem. I > 'participate' in ReactOS development and all bugs that may happen when > running Prosody on ReactOS could be mostly the operating system bugs. It > does not mean that ReactOS with NT 6.0 subsystem is unsupported, it *will > be* supported, as we need our network stack to be as good as possible. OS > architecture requirements are different here: x86 is fine, but x64 is more > preferred — reports from both versions are accepted. *NT 5.2 version is > not supported and never will be.* You can volunteer yourself for NT 5.2, > but I won't join the party. > > ——— > Provide me your suggestions in replies. I will be happy for any response! > > > On Saturday, 4 March 2023 at 22:20:05 UTC+3 Vitaly Orekhov wrote: > > > - Target OS: Windows Vista SP2 *or* Windows 7 SP1, x64 *only* > - Toolchain: Visual Studio 17 2022 > - Lua: 5.4 > - OpenSSL: >=3.0.8 > - libexpat: >=2.5.0 > - libidn: >=1.41, *libICU replacement preferred* > - zlib: don't use > > Optional dependencies like LuaDBI are not shipped with the installer. > LuaEvent will be required and enabled by default because select backend is > deprecated. Prosody 0.9.8 did ship LuaEvent, but hadn't it enabled by > default. > > -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/prosody-dev/f3c3fd9b-fef6-4d00-b543-66624699a2c5n%40googlegroups.com.
