Re: Status Meeting (November 2020)
Victor Perevertkin <[email protected]> Thu, 26 Nov 2020 22:46:59 +0300
| Newsgroups | gmane.os.reactos.kernel |
|---|---|
| Message-ID | <[email protected]> |
--===============1275876187== Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-NdZlgOrhAErJJRt7CC7+" --=-NdZlgOrhAErJJRt7CC7+ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey, > How much work needs to be done to get newer versions of MSVC > running=20 This needs our compatibility layer to be finished (it's progressing, but slowly) > How big is the danger to lose the capability to exchange ReactOS > and Win 2k3 system files? As far as I know, we don't have issues with that atm with the latest MSVC > There isn't a time plan to get at least the core system file=20 > structure, exports and structures at Win 6+ level yet, right? Nope. But a compatibility layer in usermode should be enough for now > How big is the danger that newer MSVC versions can't be used to=20 > compile ReactOS anymore? (E.g. loosing the capability to build Win > XP compatible files) We use a barebones compiler, without any SDK or something. The only danger I see - they may remove support for old architectures or SEH mechanism (CxxFrameHandler3). So far latest version work And we always have GCC and clang, the latter is going to have a full SEH support in some near future Victor On Thu, 2020-11-26 at 10:07 +0100, [email protected] wrote: > Moin, >=20 > a few questions: > * How much work needs to be done to get newer versions of MSVC > running=20 > by e.g. using the shims? (not GUI, only the toolchain, and possibly > hack=20 > around installer problems)? > * How big is the danger to lose the capability to exchange ReactOS > and=20 > Win 2k3 system files? > * There isn't a time plan to get at least the core system file=20 > structure, exports and structures at Win 6+ level yet, right? > * How big is the danger that newer MSVC versions can't be used to=20 > compile ReactOS anymore? (E.g. loosing the capability to build Win > XP=20 > compatible files) >=20 > I think the first question/solution could be a short time > compromise,=20 > the rest points at the "real" long time solution: targeting a newer=20 > Windows version.. >=20 > Best regards, > Michael Fritscher >=20 > _______________________________________________ > Ros-dev mailing list > [email protected] > http://reactos.org/mailman/listinfo/ros-dev --=-NdZlgOrhAErJJRt7CC7+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQJTBAABCgA9FiEEork8Iv3S4NyV9jphx1C3Ii6ceDAFAl/ABjMfHHZpY3Rvci5w ZXJldmVydGtpbkByZWFjdG9zLm9yZwAKCRDHULciLpx4MJVID/4rVptQiF6GgiIu INExfr9FFg7UX5ZLAiqA0RaOokZld4b3l6GGINaZVmO13ZgyHk7hSjinQkUGfOyf yYMGBjeU0ivsdNI8mmMFphcDD4kBp2hwip7MrGGc9A8JrtxiZ4EK/GAfoQysKzW1 tWmIdQJrfYTsP1gaiJQAcJwcmUpoaY7uuVkdemU35WjwMR/TbNmn0SzsTGXEXkrx 99cCIWedMdiSuSuEgmKEww9Iv4t7t/dTJjpJtJUmNMe5f5RoUvZtQc5y16BcK44Y gfRgWW7ESaGa8Vd1eEqwkzQW0bObiO6fNRIjQ2UcVNSxm5NygxeS/xAH67SlMlXi aiEFrCpl6r5u3RpLxnjukxg+giNF++9Z5i9qD1NwEUhi3GxEsW9Muyz4J0HANIzH Jpvm4WnhrSz5KNkA5IpFjSSCDrZEVwBitN5//VbRO/Nd6Nta6CN2WZxTZjhBeHcQ iIsthZMVGi3Ix3yk+mIvsCrdDbALfChryHjoE/X6cfYubg6YrzCw3SiFfcSytjY/ cWnadC3bzif8Np9+6EdwQzefnoudl75QjkZH6wNFaGpxygQSxQO5hwN1X1JX9Quz CVGyJ/Q/JpZouqCfvGoec1yHTcByXvgzfv4ns1MrPYndpy/4572+QqkPfgP6ou4u err+6Um1lDuRVOcW9/LZ72293xvQXQ== =JVQ1 -----END PGP SIGNATURE----- --=-NdZlgOrhAErJJRt7CC7+-- --===============1275876187== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ros-dev mailing list [email protected] http://reactos.org/mailman/listinfo/ros-dev --===============1275876187==--