[ros-dev] [ros-diffs] [hbelusca] 74741: [MKHIVE][CMAKE]: Make mkhive a bit more flexible, so that it can generate only specific hives on-demand (and not all of them always at once). I need this for building a single boo...

[Thomas Faber]

I understand not making the change to how 1st stage deals with the
registry in trunk.
Why not the tool change though? Can't you have the new mkhive do the
exact same thing it does now, and do it in trunk? The smaller your
branch merge commit the easier it will be to avoid/pinpoint/fix
regressions.


On 2017-06-02 02:34, hbelusca at svn.reactos.org wrote:
> Author: hbelusca
> Date: Fri Jun  2 00:34:10 2017
> New Revision: 74741
> 
> URL: http://svn.reactos.org/svn/reactos?rev=74741&view=rev
> Log:
> [MKHIVE][CMAKE]: Make mkhive a bit more flexible, so that it can generate only specific hives on-demand (and not all of them always at once). I need this for building a single bootcd registry hive.
> I commit these changes in my branch because it's too much über-advanced code for our trunk, yet... (and it will uncover deep "setup" hacks in NTOS' iomgr & pnpmgr as soon as I'll enable 1-st stage setup to have a proper registry present as done on windows).
> CORE-13347 #comment Committed in r74741 but just in the setup_improvements branch for the moment.