Re: CMake builds :)

[Eli Zaretskii]

[Please use Reply All, to leave the list on CC'ed.]

> From: Kuba Ober <kuba@mareimbrium.org>
> Date: Fri, 15 Dec 2023 07:46:55 -0500
> 
> I’ve already done the work needed to have it compile with Visual Studio 2022. 
> Fairly minor tweaks were needed.
> 
> I’ll do the copyright assignment and then work on figuratively speaking 
> merging the cmake support you’ve done with what I’ve done. I went implemented 
> a lot of tests from autotools that were in configure. So assuming there is 
> cmake I could get it to work on most any platform.

I don't recommend that, really.  Going this way means the MinGW port
and the MSVC port will diverge, which is bad for maintenance, since it
will be impossible to compare them, both in the test suite and in the
real-life examples.

But if you intend to keep maintaining this "forever", I cannot tell
you how to go about this, only give you friendly advice.

> Regarding the pc directory: yes, that works, but it’s a hack of sorts and 
> really only for Mingw.

It isn't only for MinGW.  It used to work for other Windows
development environments, including Visual Studio (and for OS/2 as
well).  We removed that because no one was maintaining it.

> I’d like it to work out of the box with mingw-gcc, msvc, clang, and icc.

What are the differences, beyond having CC have a different value?

> I’ll be doing maintenance from GitHub and pushing upstream since I’d really 
> want a proper ci setup. Hey, maybe we can get it to build for msdos again :)

The MSDOS port was removed due to lack of maintenance, so to
reintroduce it we will need someone who'd volunteer to keep it up to
date.  Other than that, the same pc/ directory was used for the MSDOS
build as well, and it worked fine until the moment we removed MSDOS
support.