> early February 2022
Should be read as 'early February 202*3*'. I made a typo here.
I also want to address one more question: I want to open a thread here
regarding how should the reworked Prosody for Windows look like, in terms
of target Windows versions, compiler sets, building tools, etc. I need to
collect all my thoughts (and suggestions from the chatroom) in one place,
especially for those Windows developers who do their stuff in Visual Studio
and compile everything with MSVC.
(Yes, I use a Vivaldi Mail e-mail address to submit patches because Mail.RU
decided to be a bummer and Mercurial froze when e-mail patch submission
attempt was made. Don't use their services, please.)
On Thursday, 2 March 2023 at 02:54:00 UTC+3 vkvo...@vivaldi.net wrote:
> A conversation from early February 2022 in the Prosody IM Chatroom
> resulted in
> determining Lua 5.4 as the target language version ('makes no sense to
> rely on
> CentOS 7 EOL if compiling for Windows').
>
> OpenSSL 3 works fine under Windows, but someone mentioned in the chat that
> OpenSSL 1.x is more widespread in common Linux distributions. I'm open to
> suggestions here, but if OpenSSL 3 looks good to maintainers, I will keep
> the
> patch like this.
>
> libidn 1.41 requires some patching if Prosody is going to be compiled with
> MSVC,
> like I do. The maintainers said that even Windows builds are compiled on
> Linux,
> so the build process has to be GCC-aware, I guess. Again, I'm open to
> all suggestions.
>
> Also, this Makefile is currently not aware of x64 configuration of
> dependencies.
> It must be revised to be able to provide both Win32 and x64 targets, in
> case of
> MSVC.
>
>
>
--
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 prosody-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/prosody-dev/cc6e98b7-b9c8-4400-aabb-955699ee3992n%40googlegroups.com.
