feature request for the new build system

[Hartmut Birr]

Hi,

for a simple make, the build process should not check if the path
%ROS_INSTALL% exists. On my system it points to a network drive, which
isn't a valid path if the test machine is switched off or is running ros.

- Hartmut

[Casper Hornstrup]

I see your point. The reason rbuild creates the directories is that rbuild can do it much
faster than make. Make spawns one process
per directory to be created whereas in rbuild it is all done within one process. Would a
switch to rbuild be enough (specified using
the ROS_RBUILDFLAGS environment variable)? E.g. "-mi" means make will handle the
creation of the install directories through
dependencies.

Casper

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On Behalf Of
> Hartmut Birr
>  Sent: 28. maj 2005 19:45
>  To: ReactOS Development List
>  Subject: [ros-dev] feature request for the new build system
>  
>  Hi,
>  
>  for a simple make, the build process should not check if the path
>  %ROS_INSTALL% exists. On my system it points to a network drive, which
>  isn't a valid path if the test machine is switched off or is running ros.
>  
>  - Hartmut
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev

[Gunnar Dalsnes]

+1. Compiling shouldnt touch the install location. It didnt before and 
thats how it should be.

Gunnar

Hartmut Birr wrote:
>   Hi,
>  
>  for a simple make, the build process should not check if the path
>  %ROS_INSTALL% exists. On my system it points to a network drive, which
>  isn't a valid path if the test machine is switched off or is running ros.
>  
>  - Hartmut
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>  
>  
>

[Casper Hornstrup]

set ROS_RBUILDFLAGS=-mi

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On Behalf Of
> Gunnar Dalsnes
>  Sent: 5. juni 2005 02:39
>  To: ReactOS Development List
>  Subject: Re: [ros-dev] feature request for the new build system
>  
>  +1. Compiling shouldnt touch the install location. It didnt before and
>  thats how it should be.
>  
>  Gunnar
>  
>  Hartmut Birr wrote:
>  > Hi,
>  >
>  > for a simple make, the build process should not check if the path
>  > %ROS_INSTALL% exists. On my system it points to a network drive, which
>  > isn't a valid path if the test machine is switched off or is running ros.
>  >
>  > - Hartmut

[Anich Gregor]

On Sunday 05 June 2005 07:04, Casper Hornstrup wrote:
>   set ROS_RBUILDFLAGS=-mi 
Thanks, I need that too (not only to install via network but also to not have 
to mount the vmware disk image while reactos is beeing built)

I found another (minor) problem - when i set ROS_INSTALL to install/ReactOS it 
won't create the ReactOS dir if it doesn't exist, IMO it should be created 
(with the old build system it was created iirc)

>   make: *** No rule to make target
> `install/ReactOS', needed by 
>  `install/ReactOS/system32'.  Stop.

[Casper Hornstrup]

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On Behalf Of Anich
> Gregor
>  Sent: 5. juni 2005 17:23
>  To: ros-dev(a)reactos.com
>  Subject: Re: [ros-dev] feature request for the new build system
>  
>  On Sunday 05 June 2005 07:04, Casper Hornstrup wrote:
> >   set ROS_RBUILDFLAGS=-mi 
>  
>  Thanks, I need that too (not only to install via network but also to not have
>  to mount the vmware disk image while reactos is beeing built)
>  
>  I found another (minor) problem - when i set ROS_INSTALL to install/ReactOS it
>  won't create the ReactOS dir if it doesn't exist, IMO it should be created
>  (with the old build system it was created iirc) 
Is this when you use the -mi flag? Then the native mkdir is used which may or may
not be able to create missing parent directories depending on your OS.

Casper

[Anich Gregor]

On Sunday 05 June 2005 15:37, Casper Hornstrup wrote:
> >   -----Original
> > Message-----
> >  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On
> >  Behalf Of Anich Gregor Sent: 5. juni 2005 17:23
> >  To: ros-dev(a)reactos.com
> >  Subject: Re: [ros-dev] feature request for the new build system
> >
> >  On Sunday 05 June 2005 07:04, Casper Hornstrup wrote:
> > >   set ROS_RBUILDFLAGS=-mi 
> >  Thanks, I need that too (not only to install via network but also to not
> >  have to mount the vmware disk image while reactos is beeing built)
> >
> >  I found another (minor) problem - when i set ROS_INSTALL to
> >  install/ReactOS it won't create the ReactOS dir if it doesn't exist, IMO
> >  it should be created (with the old build system it was created iirc) 
>  Is this when you use the -mi flag? Then the native mkdir is used which may
>  or may not be able to create missing parent directories depending on your
>  OS.
>
>  Casper 
Both, with and without the -mi flag, i get the same message when the directory 
doesnt exist.

 - blight

[Sylvain Petreolle]

--- Anich Gregor <blight$blight.eu.org> a écrit :
<cut>
> > >   I found another (minor) problem - when i set
> > > ROS_INSTALL to
> > >  install/ReactOS it won't create the ReactOS dir if it doesn't exist, IMO
> > >  it should be created (with the old build system it was created iirc) 
> >  Is this when you use the -mi flag? Then the native mkdir is used which may
> >  or may not be able to create missing parent directories depending on your
> >  OS.
> >
> >  Casper 
>  
>  Both, with and without the -mi flag, i get the same message when the directory 
>  doesnt exist.
>  
>   - blight 
Same here, without the -mi flag, make install says "Nothing to be
done for ..."' 
when the install directory doesnt exist.


Kind regards,

Usurp (aka Sylvain Petreolle)

humans are like computers,
yesterday the BIOS was all
- today its just a word