use explicit file paths for CMake rather then globing, This is recommended by cmake devs.

globbing vs explicit is discussed here.
http://www.cmake.org/pipermail/cmake/2008-December/025694.html

Practical implications are:
- developers need to keep CMakeLists.txt files up to date.
- Users wont get strange linking errors if they build after a file is added, since CMake detects CMakeLists.txt is modified and automatically reconfigure.

1 files changed, 22 insertions, 2 deletions

diff --git a/source/gameengine/Expressions/CMakeLists.txt b/source/gameengine/Expressions/CMakeLists.txt
index 126192d2188..828afa7ae92 100644
--- a/source/gameengine/Expressions/CMakeLists.txt
+++ b/source/gameengine/Expressions/CMakeLists.txt
@@ -24,8 +24,6 @@
 #
 # ***** END GPL LICENSE BLOCK *****
 
-FILE(GLOB SRC *.cpp)
-
 SET(INC
 	.
 	../../../source/kernel/gen_system
@@ -36,6 +34,28 @@ SET(INC
 	../../../source/blender/blenloader
 )
 
+SET(SRC
+	BoolValue.cpp
+	ConstExpr.cpp
+	EXP_C-Api.cpp
+	EmptyValue.cpp
+	ErrorValue.cpp
+	Expression.cpp
+	FloatValue.cpp
+	IdentifierExpr.cpp
+	IfExpr.cpp
+	InputParser.cpp
+	IntValue.cpp
+	KX_HashedPtr.cpp
+	ListValue.cpp
+	Operator1Expr.cpp
+	Operator2Expr.cpp
+	PyObjectPlus.cpp
+	StringValue.cpp
+	Value.cpp
+	VectorValue.cpp
+)
+
 IF(WITH_PYTHON)
 	LIST(APPEND INC ${PYTHON_INC})
 ELSE(WITH_PYTHON)