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/blender/python/CMakeLists.txt

@@ -25,8 +25,6 @@
 
 ADD_SUBDIRECTORY(generic)
 
-FILE(GLOB SRC intern/*.c)
-
 SET(INC 
 	.
 	../blenlib
@@ -40,6 +38,21 @@ SET(INC
 	${PYTHON_INC}
 )
 
+SET(SRC
+	intern/bpy.c
+	intern/bpy_app.c
+	intern/bpy_array.c
+	intern/bpy_driver.c
+	intern/bpy_interface.c
+	intern/bpy_operator.c
+	intern/bpy_operator_wrap.c
+	intern/bpy_props.c
+	intern/bpy_rna.c
+	intern/bpy_rna_callback.c
+	intern/bpy_util.c
+	intern/stubs.c
+)
+
 # only to check if buildinfo is available
 IF(WITH_BUILDINFO)
 	ADD_DEFINITIONS(-DBUILD_DATE)

source/blender/python/generic/CMakeLists.txt

@@ -18,8 +18,6 @@
 #
 # ***** END GPL LICENSE BLOCK *****
 
-FILE(GLOB SRC *.c)
-
 SET(INC 
 	.
 	../../blenlib
@@ -31,4 +29,20 @@ SET(INC
 	${PYTHON_INC}
 )
 
+SET(SRC
+	IDProp.c
+	bgl.c
+	blf_api.c
+	bpy_internal_import.c
+	geometry.c
+	mathutils.c
+	mathutils_color.c
+	mathutils_euler.c
+	mathutils_matrix.c
+	mathutils_quat.c
+	mathutils_vector.c
+	noise.c
+	py_capi_utils.c
+)
+
 BLENDERLIB(bf_python_ext "${SRC}" "${INC}")