On Wed, Sep 20, 2017 at 06:56:17PM +0900, Masahiro Yamada wrote: > Some targets can choose the save path of the .config file. > > For example, run "make gconfig" > then choose "File -> Save as" > from the menu. > > But, silentoldconfig does not have a way to save .config > out out the build tree. Yes, I noticed this feature when writing the patch and I tried not to break it. However, running make without target will call silentconfig before building and it is not possible to use a file outside the build folder. The reason I did this patch is because I am keeping my kernel configuration files in an external git repository and I am using KCONFIG_CONFIG to select the reference this config. It was working well before 4.13. But maybe my workflow is wrong. > > conf_write() may be called with a directory path, > in this case, the KCONFIG_OVERWRITECONFIG is appended > as the base name. > > If we support an absolute path in KCONFIG_OVERWRITECONFIG, > I think it is strange. > According to the documentation, KCONFIG_OVERWRITECONFIG is a boolean that should be set if the .config file is a symlink. In the code, it conf_write will directly write the config file unstead of creating a temporary file and renaming it to .config. So it allows me to use any file on the machine by symlinking it to the .config file of the build folder so that I can keep my current workflow. Unfortunately, I didn't know about it before writing the patch. The strange part is that KCONFIG_CONFIG supports absolute path in most of the build process. It only breaks when referencing a file on a different file-system than the build folder, and only because of the silentconfig call. Best regards, -- Nicolas Porcel -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
