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.
This commit is contained in:
@@ -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}")
|
||||
|
Reference in New Issue
Block a user