Hi,
Due to continued lack of
interest in/inability to fix these issues, I have abandoned all work on a
standardized ReactOS Build/Test/Development environment.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design
Engineer, ReactOS
From: ros-dev-bounces@reactos.org
[mailto:ros-dev-bounces@reactos.org] On Behalf Of Alex Ionescu
Sent: March-25-07 6:20 PM
To: 'ReactOS Development List'
Subject: [ros-dev] Inability to work on RosDE/TE
Hi,
I promised a new testing/development environment but
unfortunately I cannot pursue my work because nobody has been able to fix
rbuild to my requirements. If anyone does want to see the standardized
environment I promised, please prod your local ReactOS developer for the
following features:
1)
*Working* ROS_INTERMEDIATE and ROS_OUTPUT
directories. They are broken in many ways:
a. Don’t
work with relative pats.
b. Don’t
work at all for .pch files and/or compilation units.
c. Create
other sorts of unpredictable errors due to hard-coded strings/directories in
makefiles or rbuild.
2)
ROS_TOOLS_DIRECTORY. The ability for the tools to be
outside the ROS_OUTPUT directory, such as in c:\rosde\tools. Someone committed
such a patch but it was reverted without a newer version/fix.
a. Also
requires making rbuild check if the binaries are present, and if so, NOT to
rebuild them.
b. Create
–forcetools switch to rbuild which would force it to bypass the check in 2a.
3)
Tools must be built and work with the –O3 optimization
setting.
Of course, I won’t go into the fact that my request for the
other rbuild features such as a graphical dependency map have gone unanswered.
Many thanks to those who _have_ worked on some of the MSVC
features/bugfixes I brought forward and do the small attempt at a depmap.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS