[modules] new module naming convention

rename $MODULE.{conf,build} to module.{conf,build}

1 files changed, 5 insertions, 5 deletions

diff --git a/remote/setup_target b/remote/setup_target
index f9e91f96..f11de86c 100755
--- a/remote/setup_target
+++ b/remote/setup_target
@@ -22,8 +22,8 @@
 #	can process any module, as long as following requirements are met:
 #
 #		- Modules need to have a build-script and a config file,
-#		  i.e. remote/module/kernel/kernel.build
-#		  and  remote/module/kernel/kernel.conf
+#		  i.e. remote/module/kernel/module.build
+#		  and  remote/module/kernel/module.conf
 #		  as these will be read by 'process_module'.
 #
 #		- Modules need to generate a 'build'-directory in their
@@ -73,7 +73,7 @@ read_config () {
 		unset $VARNAME
 	done
 
-	local MODULE_CONFIG="${MODULE_DIR}/${MODULE}.conf"
+	local MODULE_CONFIG="${MODULE_DIR}/module.conf"
 
 	# sanity checks
 	[ ! -e "${MODULE_CONFIG}" ] && perror "Config for '$MODULE' not found."
@@ -113,7 +113,7 @@ validate_config () {
 # generic function to read the build script of the current $MODULE
 #
 read_build () {
-	local BUILD_SCRIPT="${MODULE_DIR}/${MODULE}.build"
+	local BUILD_SCRIPT="${MODULE_DIR}/module.build"
 
 	[ ! -e "${BUILD_SCRIPT}" ] && perror "Build script for specified tool not found."
 
@@ -430,7 +430,7 @@ process_module() {
 	post_copy
 	# Write new md5 file if not existent yet
 	if [ ! -f "$MD5FILE" ]; then
-		md5sum "$MODULE_DIR/$MODULE".* > "$MD5FILE" || perror "Could not create $MD5FILE"
+		md5sum "$MODULE_DIR/module".* > "$MD5FILE" || perror "Could not create $MD5FILE"
 	fi
 	# Update size of target build dir
 	if [ -d "${TARGET_BUILD_DIR}" ]; then