Richard Levitte

> > > `BUILDFILE=CMakeLists.txt perl Configure [options...]` > > > > > > I just looked at this option and failed. > > https://github.com/openssl/openssl/blob/d79bb5316e1318bd776d6b2d6723a36778e07f9d/Configure#L1440 > > > > Is this...

> > As for how to make a `Configurations/CMakeLists.txt.tmpl`, it should really not be very hard. Simply do this: > > > > * copy everything from the current `CMakeLists.txt`...

> @dg0yt Regarding [#20153 (comment)](https://github.com/openssl/openssl/pull/20153#discussion_r1090218853) > > I agree with you here, and for other selfish reasons I would like to retain this ability as well. I think everyone should...

> The `BUILDFILE` override you contributed will make a meson, premake, [insert build system here], etc port very convenient. It'll just require a new template. That's my intention, always was......

Thanks @eli. I was unaware of that one...

That's a tricky one, and this is one place where we don't treat cross compilation particularly well, unfortunately. To borrow the terminology from [GNU autoconf](https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Specifying-Target-Triplets.html), the specified paths are normally...

@t8m has a point, and that can be used creatively... however, it gets a little difficult with a deployment prefix like, say, `C:\Program Files\OpenSSL`, and the cross compilation being done...

Tests are a different matter... They will take a few more PRs to fix

The failed CI isn't relevant for this PR, so I'm merging

Merged ae08ed08e49b945d516294106fa185bb136669b2 Fix more VMS inclusions