It seems it doesn't work right now
set ROS_INSTALL=z:\reactos make install
As far as I know, the install option was not included in the new build environment because of lack of interest in maintaining it. The alternative I use at the moment is to enable unattended installation of the bootcd.
On 13 December 2013 10:12, Marvin Zhang fanzi2009@gmail.com wrote:
It seems it doesn't work right now
set ROS_INSTALL=z:\reactos make install
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Hi David, Do you mean you have to generate bootcd and install it again once if you just modify some modules? Marvin
On Fri, Dec 13, 2013 at 5:18 PM, David Quintana (gigaherz) < gigaherz@gmail.com> wrote:
As far as I know, the install option was not included in the new build environment because of lack of interest in maintaining it. The alternative I use at the moment is to enable unattended installation of the bootcd.
On 13 December 2013 10:12, Marvin Zhang fanzi2009@gmail.com wrote:
It seems it doesn't work right now
set ROS_INSTALL=z:\reactos make install
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Yes, I just gave up on copying only the changed files. For convenience, I keep two HDDs in my ReactOS VM, one for the main installation, and another one for files I don't want to lose when installing a new build. This second HDD is also marked as persistent, so it doesn't get included in snapshots.
On 13 December 2013 10:25, Marvin Zhang fanzi2009@gmail.com wrote:
Hi David, Do you mean you have to generate bootcd and install it again once if you just modify some modules? Marvin
On Fri, Dec 13, 2013 at 5:18 PM, David Quintana (gigaherz) gigaherz@gmail.com wrote:
As far as I know, the install option was not included in the new build environment because of lack of interest in maintaining it. The alternative I use at the moment is to enable unattended installation of the bootcd.
On 13 December 2013 10:12, Marvin Zhang fanzi2009@gmail.com wrote:
It seems it doesn't work right now
set ROS_INSTALL=z:\reactos make install
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
I just use the update function on the bootcd ('R' then 'U').
It's not really supported and doesn't do the registry, but works 99% of the time.
On Fri, Dec 13, 2013 at 8:35 PM, David Quintana (gigaherz) < gigaherz@gmail.com> wrote:
Yes, I just gave up on copying only the changed files. For convenience, I keep two HDDs in my ReactOS VM, one for the main installation, and another one for files I don't want to lose when installing a new build. This second HDD is also marked as persistent, so it doesn't get included in snapshots.
On 13 December 2013 10:25, Marvin Zhang fanzi2009@gmail.com wrote:
Hi David, Do you mean you have to generate bootcd and install it again once if you just modify some modules? Marvin
On Fri, Dec 13, 2013 at 5:18 PM, David Quintana (gigaherz) gigaherz@gmail.com wrote:
As far as I know, the install option was not included in the new build environment because of lack of interest in maintaining it. The alternative I use at the moment is to enable unattended installation of the bootcd.
On 13 December 2013 10:12, Marvin Zhang fanzi2009@gmail.com wrote:
It seems it doesn't work right now
set ROS_INSTALL=z:\reactos make install
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
It doesn't work since the moment of RBuild -> CMake switch. I was quite worried about that, because mostly I used to use make ntoskrnl_install and it would copy the file automatically.
Nowadays I just copy it over to the virtual HDD myself using FAR, for example.
Regards, Aleksey Bragin
On 13.12.2013 13:12, Marvin Zhang wrote:
It seems it doesn't work right now
set ROS_INSTALL=z:\reactos make install
Hi Aleksey, What do you mean "using FAR"? Marvin
On Fri, Dec 13, 2013 at 5:35 PM, Aleksey Bragin aleksey@reactos.org wrote:
It doesn't work since the moment of RBuild -> CMake switch. I was quite worried about that, because mostly I used to use make ntoskrnl_install and it would copy the file automatically.
Nowadays I just copy it over to the virtual HDD myself using FAR, for example.
Regards, Aleksey Bragin
On 13.12.2013 13:12, Marvin Zhang wrote:
It seems it doesn't work right now
set ROS_INSTALL=z:\reactos make install
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
www.farmanager.com - it's more handy to use that tool for quickly copying files and watching debug log file in real time (its viewer automatically updates file's contents).
Regards, Aleksey
On 14.12.2013 12:02, Marvin Zhang wrote:
Hi Aleksey, What do you mean "using FAR"? Marvin
On Fri, Dec 13, 2013 at 5:35 PM, Aleksey Bragin <aleksey@reactos.org mailto:aleksey@reactos.org> wrote:
It doesn't work since the moment of RBuild -> CMake switch. I was quite worried about that, because mostly I used to use make ntoskrnl_install and it would copy the file automatically. Nowadays I just copy it over to the virtual HDD myself using FAR, for example. Regards, Aleksey Bragin On 13.12.2013 13:12, Marvin Zhang wrote:It seems it doesn't work right now set ROS_INSTALL=z:\reactos make install
-
Aleksey Bragin -
David Quintana (gigaherz) -
Huw Campbell -
Marvin Zhang