Re: saving configuration to version control
Baruch Burstein <[email protected]> Sun, 9 Feb 2025 23:57:48 +0200
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <CA+34VNJ5bbB2k=v47FKYLHOQoLFnnYfY6HuJxQwSX+xno_7D3Q@mail.gmail.com> |
Thank you On Sun, Feb 9, 2025 at 9:48 PM Adam Lackorzynski <[email protected]> wrote: > Hello, > > On Fri Feb 07, 2025 at 01:14:30 +0200, Baruch Burstein wrote: > > After running `make config`, I am trying to save my configuration to git > > and later restore it. This is for both fiasco and l4. I found that the > > command `make savedefconfig` works (just like for linux kernel) to > create a > > defconfig file for uploading to git, but the command `make defconfig` for > > restoring the configuration from this file doesn't work. What file > should I > > be saving/restoring, or what is the process to save/restore my > > configuration? Either a defconfig or a full configuration would be ok. > > Thank you > > The config can be given when creating the build directory for both the > L4Re kernel and L4Re user-level: > > User-level: > > $ B=builddir T=defconfig > Or: $ B=builddir DROPSCONF_DEFCONFIG=path/to/defconfig > > The default configs are in l4/mk/defconfig > > For an existing build dir, copy a defconfig to .kconfig and call > make olddefconfig. > > Kernel: > > $ make B=build T=defconfig > > The default configs are in src/templates > > For an existing build dir, copy a defconfig to globalconfig.out and call > make olddefconfig. > > > Having described this, unifying both via the known config_defconfig make > target is a good idea, and in progress. > > > > > Adam > _______________________________________________ l4-hackers mailing list -- [email protected] To unsubscribe send an email to [email protected]