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.

source/gameengine/Physics/Bullet/CMakeLists.txt

@@ -24,8 +24,6 @@
 #
 # ***** END GPL LICENSE BLOCK *****
 
-SET(SRC CcdPhysicsEnvironment.cpp CcdPhysicsController.cpp CcdGraphicController.cpp)
-
 SET(INC
 	.
 	../common
@@ -46,6 +44,12 @@ SET(INC
 	${PYTHON_INC}
 )
 
+SET(SRC
+	CcdPhysicsEnvironment.cpp
+	CcdPhysicsController.cpp
+	CcdGraphicController.cpp
+)
+
 IF(WITH_BULLET)
 	ADD_DEFINITIONS(-DUSE_BULLET)
 ENDIF(WITH_BULLET)

source/gameengine/Physics/Dummy/CMakeLists.txt

@@ -24,11 +24,13 @@
 #
 # ***** END GPL LICENSE BLOCK *****
 
-SET(SRC DummyPhysicsEnvironment.cpp)
-
 SET(INC
 	.
 	../common
 )
 
+SET(SRC
+	DummyPhysicsEnvironment.cpp
+)
+
 BLENDERLIB(bf_dummy "${SRC}" "${INC}")

source/gameengine/Physics/common/CMakeLists.txt

@@ -24,12 +24,19 @@
 #
 # ***** END GPL LICENSE BLOCK *****
 
-SET(SRC PHY_IMotionState.cpp PHY_IController.cpp PHY_IPhysicsController.cpp PHY_IGraphicController.cpp PHY_IPhysicsEnvironment.cpp PHY_IVehicle.cpp)
-
 SET(INC
 	.
 	../Dummy
 	../../../intern/moto/include
 )
 
+SET(SRC
+	PHY_IMotionState.cpp
+	PHY_IController.cpp
+	PHY_IPhysicsController.cpp
+	PHY_IGraphicController.cpp
+	PHY_IPhysicsEnvironment.cpp
+	PHY_IVehicle.cpp
+)
+
 BLENDERLIB(bf_common "${SRC}" "${INC}")