Hello,
as Colin already mentioned, I have tried to compile libc++ for ReactOS.
I stopped the project for two reasons:
1. The current state of the CRT in ReactOS.
2. The ongoing discussion about MSVC 2010.
With MSVC 2010 it is of course impossible to compile a current version of
libc++. So why should I waste my time?
Without a clear commitment to using current C++ compilers, it simply makes
no sense.
As Colin described in detail, current technologies would increase the pace
of development and attract more interested developers.
Developers like me, who simply do something else without the project ever
knowing about them.
But don't get me wrong, this is not about me or libc++. Maybe libc++ cannot
be used for other reasons after all! But with MSVC 2010 you don't even have
to start.
All the best,
Dominik
I totally and vehemently agree with Hermes here: We should NOT ditch VS2010.
Arguments that were raised by others against VS2010 and my reply:
-"ditching it brings in new developers to ros magically" <- I do ask then, where are they? I don't see any.
-"we should not be limited to strict C89" <- No one did request for that. All we want is to remain compatible to VS2010. A subset.
-"syncing BTRFS is a bit harder" <- So what? Then let others do the job. Actually BTRFS is not even a mandatory feature of ros. Having it in the tree is just luxury.
-"libc++" <- I see no urgent need and nothing it would give in return that would outweight what we would sacrifice.
My arguments again for keeping VS2010:
-VS2010 creates the smallest binaries of all compilers we do support
-VS2010 CAN be installed in ros, when ros is installed as Server during 2nd stage, (yes this was not the case for a very short moment, unfortunately exactly when we discussed in https://github.com/reactos/reactos/pull/2658 but now it works again, even in 0.4.14-RC51)
-VS2010 can now even open the VS2010 cmd prompt see https://jira.reactos.org/secure/attachment/57140/57140_0.4.15-dev-203-g711f…
-no other VS>2010 can even complete its setup in ros, and that will remain like that for many years to come
-VS2010 is the last version that runs on XPSP3 (which is important for some of our devs including myself)
-VS2010 is the last version that runs on 2k3SP2 which is our current target
-VS2010 is reliable with industry-proven stability, and itself no moving target (unlike VS2019 which breaks our builds every few weeks when MS upgrades it)
-VS2010 DOES provide std::unique_ptr. Stating anything else is just a lie. It covers > 95% of CPP2011-standard. It is absolutely possible and not complicated to write leak-free-code with it.
Hello,
Please note that I would like to cast a vote in favor of restoring
compatibility for VS2010.
Thanks very much,
Doug Lyons
--
This email has been checked for viruses by AVG.
https://www.avg.com
Hi all,
With several people asking for a status meeting, let's have another one
before the year is over.
Let me invite you to the meeting on
Thursday, 26th November 2020
19:00 UTC
Mattermost private channel "Meeting"
So far, there is only one point on the agenda:
* Achievements and Future Outlook (everyone)
What have you been working on and what are your plans?
Please submit further agenda proposals by answering to this mail.
Looking forward to see you!
Colin
Would on August 31 be alright for you? I'm asking because I won't be available by September 5 or 7 from now on due to a temporary job that I'm going to have soon.
Regards,
George
Colin Finck <colin(a)reactos.org> wrote on Fri, August 14th, 2020, 5:24 PM:
> Hi all!
>
> Keeping the usual schedule, our next bi-monthly status meeting would be
> on 27th August.
> Due to vacation, I won't be available on that date though and therefore
> cannot serve as the meeting moderator.
>
> If you want the meeting to take place on the usual date, please find
> another moderator.
> Otherwise, we have to postpone it I guess.
>
> Suggestions are welcome! :)
>
>
> Cheers,
>
> Colin
Hi all!
Keeping the usual schedule, our next bi-monthly status meeting would be
on 27th August.
Due to vacation, I won't be available on that date though and therefore
cannot serve as the meeting moderator.
If you want the meeting to take place on the usual date, please find
another moderator.
Otherwise, we have to postpone it I guess.
Suggestions are welcome! :)
Cheers,
Colin
Hola que tal, estoy realizando mi tesis basándose en ReactOS y quisera
saber mas informacion sobre el SO, tengo curiosidad si ustedes también
trabajan con GNUPG o algun tipo de sistema de cifrado para los archivos y/o
particiones del disco duro y si me podrian explicar porque esa parte no
esta explicado en ninguna documentacion de ReactOS, se los agreadeceria si
me podrian brindar esa informacion y/o orientarme les agredeceria de
antemano.
Muchas gracias.
--
Saludos
--
Sthip Harrisson Russell Panduro.
Correo: sthiplife(a)gmail.com
Hi,
I'm Frédéric from QubesOS project. I wanted to try your latest release ReactOS 0.4.13 today and I've managed to install it on our latest QubesOS R4.1 in development within a HVM domain. First text installer for partitioning is fine and the graphical setup for languages and parameters too. At first OS boot while seeing the desktop for the first time, it popups a window pci device detection but then, just few seconds after the VM is freezing. Looking at Xen status, the stubdomain is not frozen at all, but the VM itself yes with 100% CPU usage. I've tried IDE driver for disk too but the same behavior appeared.
Any idea on how I can catch errors or having logs? Should I try your debug ISO?
Thank you in advance for your help.
Frédéric
PS: https://jira.reactos.org/browse/CORE-13358
