Hi,
some more work happened here
RC11:
– Fixed a Bug in rosbe.cmd.
– Updated svn to 1.7.2.
RC12:
– Added new flex 2.5.35 and bison 2.5.
– Fixed radr2line to work on RSYM executables again.
« USB!!!! Work, work… »
RosBE 2.0 RC12
ROS Images
ROS SVN Updates- [SHELL32] Refresh SHELLSTATE before writing it (#7516) 22. November 2024[SHELL32] Refresh SHELLSTATE before writing it (#7516) [DH] dll/win32/shell32/wine/shellord.cWhindmar Saksit
- [GITHUB] Fix MSVC ARM build 21. November 2024[GITHUB] Fix MSVC ARM build The latest GitHub Actions runner image 20241113.3.0 uses WDK 10.0.26100.0, which dropped support for 32-bit ARM platform: - https://github.com/golang/go/issues/68552#issuecomment-2290064500 - https://github.com/actions/runner-images/issues/10981 Fix the failing build by sticking to WDK 10.0.22621.0. CORE-17604 [DH] .github/workflows/build.ymlStanislav Motylkov
- [NTOS:KD64] Only use the UNIMPLEMENTED macro in the debugger's KdpSys* helpers. 21. November 2024[NTOS:KD64] Only use the UNIMPLEMENTED macro in the debugger's KdpSys* helpers. This basically avoids re-entering the debugger (via the embedded breakpoint) while we are already running within its context. In addition, this allows the tests for Kd/NtSystemDebugControl (see PRs #7424 and #7426) to run without having ReactOS to crash. [DH] ntoskrnl/kd64/amd64/kdx64.c [DH] ntoskrnl/kd64/arm/kdarm.cHermès Bélusca-Maïto
- [COMPBATT] Use BATTERY_TAG_INVALID instead 0 when applicable 20. November 2024[COMPBATT] Use BATTERY_TAG_INVALID instead 0 when applicable [DH] drivers/bus/acpi/compbatt/compbatt.c [DH] drivers/bus/acpi/compbatt/comppnp.cHervé Poussineau
- [COMPBATT] Free device-related memory only if we failed 20. November 2024[COMPBATT] Free device-related memory only if we failed Otherwise, we just inserted in the BatteryList this device, and we will probably crash later when accessing it. [DH] drivers/bus/acpi/compbatt/comppnp.cHervé Poussineau
- [SHELL32] Refresh SHELLSTATE before writing it (#7516) 22. November 2024
I suppose that the new version will published sooner or later on the official ReactOS Build Environment web page. Please, don’t forget to look over the reported issues on ReactOS Bugzilla about RosBE and update their state before it ends up official.