Static - dynamic generation of reactos.dff

[Jérôme Gardou]

Hi reactos developers.

As many of you know, the cmake branch development is going along and is 
the occasion of many innovations in the way reactos is built.

One of this way is the reactos.dff file. Currently, it is a static file, 
meaning that each time you want to add a module to reactos, you have to 
edit this file. What I propose is to create this file dynamically, when 
parsing the build system file. Adding a reactos module twould then be as 
simple as (!) creating a new build file for this module.

For those who are concerned about slipstreaming or optional files like 
wallpapers or whatever hacking they do with the current reactos.dff, it 
will be as easy as before. There will be a file to edit, which will be 
the "static" part of it. Whatever you'll write in this file will be 
written back to reactos.dff, so there is no need to worry about that.

What do you think?

Regards.
Jérôme.

PS : The patch is there. It waits for your approval :-)

[Ged Murphy]

how does this work for rosapps and other such optional inclusions?

2010/10/30 Jérôme Gardou <jerome.gardou(a)laposte.net>

>   Hi reactos developers.
>
>  As many of you know, the cmake branch development is going along and is the
>  occasion of many innovations in the way reactos is built.
>
>  One of this way is the reactos.dff file. Currently, it is a static file,
>  meaning that each time you want to add a module to reactos, you have to edit
>  this file. What I propose is to create this file dynamically, when parsing
>  the build system file. Adding a reactos module twould then be as simple as
>  (!) creating a new build file for this module.
>
>  For those who are concerned about slipstreaming or optional files like
>  wallpapers or whatever hacking they do with the current reactos.dff, it will
>  be as easy as before. There will be a file to edit, which will be the
>  "static" part of it. Whatever you'll write in this file will be written
> back
>  to reactos.dff, so there is no need to worry about that.
>
>  What do you think?
>
>  Regards.
>  Jérôme.
>
>  PS : The patch is there. It waits for your approval :-)
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Jérôme Gardou]

As long as they are included in the build system, they will be added to 
reactos.dff. If they're not, they won't ever be mentioned.

Ged Murphy wrote:
>   how does this work for rosapps and other such optional
> inclusions?
>
>  2010/10/30 Jérôme Gardou <jerome.gardou(a)laposte.net 
>  <mailto:[e-mail]>>
>
>      Hi reactos developers.
>
>      As many of you know, the cmake branch development is going along
>      and is the occasion of many innovations in the way reactos is built.
>
>      One of this way is the reactos.dff file. Currently, it is a static
>      file, meaning that each time you want to add a module to reactos,
>      you have to edit this file. What I propose is to create this file
>      dynamically, when parsing the build system file. Adding a reactos
>      module twould then be as simple as (!) creating a new build file
>      for this module.
>
>      For those who are concerned about slipstreaming or optional files
>      like wallpapers or whatever hacking they do with the current
>      reactos.dff, it will be as easy as before. There will be a file to
>      edit, which will be the "static" part of it. Whatever you'll write
>      in this file will be written back to reactos.dff, so there is no
>      need to worry about that.
>
>      What do you think?
>
>      Regards.
>      Jérôme.
>
>      PS : The patch is there. It waits for your approval :-)
>
>      _______________________________________________
>      Ros-dev mailing list
>      Ros-dev(a)reactos.org <mailto:[e-mail]>
>      http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[Olaf Siejka]

I`m ok as long as there will be the a way to add files statically, it is
vital atm for driver slipstreaming

Regards

2010/10/30 Jérôme Gardou <jerome.gardou(a)laposte.net>

>   As long as they are included in the build system, they
> will be added to
>  reactos.dff. If they're not, they won't ever be mentioned.
>
>  Ged Murphy wrote:
>
> >   how does this work for rosapps and other such
> > optional inclusions?
> >
> >  2010/10/30 Jérôme Gardou &lt;jerome.gardou(a)laposte.net <mailto:
> >  jerome.gardou(a)laposte.net&gt;&gt;
> >
> >
> >     Hi reactos developers.
> >
> >     As many of you know, the cmake branch development is going along
> >     and is the occasion of many innovations in the way reactos is built.
> >
> >     One of this way is the reactos.dff file. Currently, it is a static
> >     file, meaning that each time you want to add a module to reactos,
> >     you have to edit this file. What I propose is to create this file
> >     dynamically, when parsing the build system file. Adding a reactos
> >     module twould then be as simple as (!) creating a new build file
> >     for this module.
> >
> >     For those who are concerned about slipstreaming or optional files
> >     like wallpapers or whatever hacking they do with the current
> >     reactos.dff, it will be as easy as before. There will be a file to
> >     edit, which will be the "static" part of it. Whatever you'll write
> >     in this file will be written back to reactos.dff, so there is no
> >     need to worry about that.
> >
> >     What do you think?
> >
> >     Regards.
> >     Jérôme.
> >
> >     PS : The patch is there. It waits for your approval :-)
> >
> >     _______________________________________________
> >     Ros-dev mailing list
> >     Ros-dev(a)reactos.org <mailto:[e-mail]>
> >
> >     http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> >
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >  
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Ged Murphy]

I like the idea. It sounds much better than manually maintaining a huge text
file

On 30 October 2010 10:27, Olaf Siejka <caemyr(a)gmail.com> wrote:

>   I`m ok as long as there will be the a way to add files
> statically, it is
>  vital atm for driver slipstreaming
>
>  Regards
>
>  2010/10/30 Jérôme Gardou <jerome.gardou(a)laposte.net>
>
> >   As long as they are included in the build system,
> > they will be added to
> >  reactos.dff. If they're not, they won't ever be mentioned.
> >
> >  Ged Murphy wrote:
> >
> > >   how does this work for rosapps and other such
> > > optional inclusions?
> > >
> > >  2010/10/30 Jérôme Gardou &lt;jerome.gardou(a)laposte.net <mailto:
> > >  jerome.gardou(a)laposte.net&gt;&gt;
> > >
> > >
> > >     Hi reactos developers.
> > >
> > >     As many of you know, the cmake branch development is going along
> > >     and is the occasion of many innovations in the way reactos is built.
> > >
> > >     One of this way is the reactos.dff file. Currently, it is a static
> > >     file, meaning that each time you want to add a module to reactos,
> > >     you have to edit this file. What I propose is to create this file
> > >     dynamically, when parsing the build system file. Adding a reactos
> > >     module twould then be as simple as (!) creating a new build file
> > >     for this module.
> > >
> > >     For those who are concerned about slipstreaming or optional files
> > >     like wallpapers or whatever hacking they do with the current
> > >     reactos.dff, it will be as easy as before. There will be a file to
> > >     edit, which will be the "static" part of it. Whatever you'll write
> > >     in this file will be written back to reactos.dff, so there is no
> > >     need to worry about that.
> > >
> > >     What do you think?
> > >
> > >     Regards.
> > >     Jérôme.
> > >
> > >     PS : The patch is there. It waits for your approval :-)
> > >
> > >     _______________________________________________
> > >     Ros-dev mailing list
> > >     Ros-dev(a)reactos.org <mailto:[e-mail]>
> > >
> > >     http://www.reactos.org/mailman/listinfo/ros-dev
> > >
> > >
> > >
> > >  _______________________________________________
> > >  Ros-dev mailing list
> > >  Ros-dev(a)reactos.org
> > >  http://www.reactos.org/mailman/listinfo/ros-dev
> > >  
> >
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >  
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Adam Kachwalla]

I love it. Definitely better than maintaining a text file that is longer  
than Bill Gates' stretch limo.

On Sat, 30 Oct 2010 22:09:53 +1100, Ged Murphy <gedmurphy(a)gmail.com> wrote:

>   I like the idea. It sounds much better than manually
> maintaining a huge  
>  text
>  file
>
>  On 30 October 2010 10:27, Olaf Siejka <caemyr(a)gmail.com> wrote:
>
> > I`m ok as long as there will be the a way to add files statically, it is
> > vital atm for driver slipstreaming
> >
> > Regards
> >
> > 2010/10/30 Jérôme Gardou <jerome.gardou(a)laposte.net>
> >
> >> As long as they are included in the build system, they will be added to
> >> reactos.dff. If they're not, they won't ever be mentioned.
> >>
> >> Ged Murphy wrote:
> >>
> >>> how does this work for rosapps and other such optional inclusions?
> >>>
> >>> 2010/10/30 Jérôme Gardou &lt;jerome.gardou(a)laposte.net <mailto:
> >>> jerome.gardou(a)laposte.net&gt;&gt;
> >>>
> >>>
> >>>    Hi reactos developers.
> >>>
> >>>    As many of you know, the cmake branch development is going along
> >>>    and is the occasion of many innovations in the way reactos is  
> >>> built.
> >>>
> >>>    One of this way is the reactos.dff file. Currently, it is a static
> >>>    file, meaning that each time you want to add a module to reactos,
> >>>    you have to edit this file. What I propose is to create this file
> >>>    dynamically, when parsing the build system file. Adding a reactos
> >>>    module twould then be as simple as (!) creating a new build file
> >>>    for this module.
> >>>
> >>>    For those who are concerned about slipstreaming or optional files
> >>>    like wallpapers or whatever hacking they do with the current
> >>>    reactos.dff, it will be as easy as before. There will be a file to
> >>>    edit, which will be the "static" part of it. Whatever you'll
> write
> >>>    in this file will be written back to reactos.dff, so there is no
> >>>    need to worry about that.
> >>>
> >>>    What do you think?
> >>>
> >>>    Regards.
> >>>    Jérôme.
> >>>
> >>>    PS : The patch is there. It waits for your approval :-)
> >>>
> >>>    _______________________________________________
> >>>    Ros-dev mailing list
> >>>    Ros-dev(a)reactos.org <mailto:[e-mail]>
> >>>
> >>>    http://www.reactos.org/mailman/listinfo/ros-dev
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Ros-dev mailing list
> >>> Ros-dev(a)reactos.org
> >>> http://www.reactos.org/mailman/listinfo/ros-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> Ros-dev mailing list
> >> Ros-dev(a)reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >>
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> > 

-- 
Give a man a fish and he will eat for a day.
Teach a man to fish and he will eat for a lifetime.
Give a man religion and he will die praying for a fish.

[Aleksey Bragin]

I like the solution which involves a static file for modules which I  
want to hardcode (e.g. drivers, some dlls), and everything else built  
automatically. Good idea!

WBR,
Aleksey.

On Oct 30, 2010, at 3:09 PM, Ged Murphy wrote:

>   I like the idea. It sounds much better than manually
> maintaining a  
>  huge text file
>
>  On 30 October 2010 10:27, Olaf Siejka <caemyr(a)gmail.com> wrote:
>  I`m ok as long as there will be the a way to add files statically,  
>  it is vital atm for driver slipstreaming
>
>  Regards
>
>  2010/10/30 Jérôme Gardou <jerome.gardou(a)laposte.net>
>  As long as they are included in the build system, they will be  
>  added to reactos.dff. If they're not, they won't ever be mentioned.
>
>  Ged Murphy wrote:
>  how does this work for rosapps and other such optional inclusions?
>
>  2010/10/30 Jérôme Gardou <jerome.gardou(a)laposte.net  
>  <mailto:[e-mail]>>
>
>
>     Hi reactos developers.
>
>     As many of you know, the cmake branch development is going along
>     and is the occasion of many innovations in the way reactos is  
>  built.
>
>     One of this way is the reactos.dff file. Currently, it is a static
>     file, meaning that each time you want to add a module to reactos,
>     you have to edit this file. What I propose is to create this file
>     dynamically, when parsing the build system file. Adding a reactos
>     module twould then be as simple as (!) creating a new build file
>     for this module.
>
>     For those who are concerned about slipstreaming or optional files
>     like wallpapers or whatever hacking they do with the current
>     reactos.dff, it will be as easy as before. There will be a file to
>     edit, which will be the "static" part of it. Whatever you'll write
>     in this file will be written back to reactos.dff, so there is no
>     need to worry about that.
>
>     What do you think?
>
>     Regards.
>     Jérôme.
>
>     PS : The patch is there. It waits for your approval :-)
>
>     _______________________________________________
>     Ros-dev mailing list
>     Ros-dev(a)reactos.org <mailto:[e-mail]>
>
>     http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev