mirror of
				https://github.com/torvalds/linux.git
				synced 2025-10-31 16:48:26 +02:00 
			
		
		
		
	kconfig: merge_config: use an empty file as initfile
The scripts/kconfig/merge_config.sh script requires an existing $INITFILE (or the $1 argument) as a base file for merging Kconfig fragments. However, an empty $INITFILE can serve as an initial starting point, later referenced by the KCONFIG_ALLCONFIG Makefile variable if -m is not used. This variable can point to any configuration file containing preset config symbols (the merged output) as stated in Documentation/kbuild/kconfig.rst. When -m is used $INITFILE will contain just the merge output requiring the user to run make (i.e. KCONFIG_ALLCONFIG=<$INITFILE> make <allnoconfig/alldefconfig> or make olddefconfig). Instead of failing when `$INITFILE` is missing, create an empty file and use it as the starting point for merges. Signed-off-by: Daniel Gomez <da.gomez@samsung.com> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
This commit is contained in:
		
							parent
							
								
									3b8241f64c
								
							
						
					
					
						commit
						a26fe287ee
					
				
					 1 changed files with 2 additions and 2 deletions
				
			
		|  | @ -112,8 +112,8 @@ INITFILE=$1 | |||
| shift; | ||||
| 
 | ||||
| if [ ! -r "$INITFILE" ]; then | ||||
| 	echo "The base file '$INITFILE' does not exist.  Exit." >&2 | ||||
| 	exit 1 | ||||
| 	echo "The base file '$INITFILE' does not exist. Creating one..." >&2 | ||||
| 	touch "$INITFILE" | ||||
| fi | ||||
| 
 | ||||
| MERGE_LIST=$* | ||||
|  |  | |||
		Loading…
	
		Reference in a new issue
	
	 Daniel Gomez
						Daniel Gomez