This is not true anymore (at least last 6 or more months). I have a
local working copy which allows conditional building of either "trunk"
or "arwinss" win32 subsystem DLLs and win32k.sys.
Changes are, of course, not committed. But building arwinss ISO is as
easy as typing "makex bootcd".
WBR,
Aleksey.
On 01.03.2012 22:19, Zachary Gorden wrote:
Last I heard there was no automated mechanism to build an arwinss
image. Aleksey has been copying arwinss binaries by hand into a
vanilla ROS build before making the image. Until someone with enough
motivation automates this, the rate of arwinss updates will remain at
the current pace.
On Thu, Mar 1, 2012 at 12:07 PM, Bernd Blaauw<bbla...@home.nl> wrote:
Op 1-3-2012 1:04, Sylvain Petreolle schreef:
The Arwinss builds are available on SourceForge:
http://sourceforge.net/projects/reactos/files/Arwinss/
Thanks for pointing those test releases out. I guess the rate of changes and
limited number of build machines might make an each-revision (just like
Cmake live and bootcds) out of the question. Same for MSVC builds and the
(highly?) experimental 64bit builds.
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
