Even though the `file(GLOB)` documentation specifically warns against using it to collect a list of source files, projects often do it anyway. Since it uses `readdir()`, the list of files will be unsorted. This list is often passed directly to add_executable / add_library. Linking binaries with an unsorted list will make it unreproducible, which means that the produced binary will differ depending on the unpredictable `readdir()` order. To solve those reproducibility issues in a lot of programs (which don't explicitly `list(SORT)` the list manually), sort the resulting list of the `file(GLOB)` command. A more detailed rationale about reproducible builds is available [here](https://reproducible-builds.org/).
21 lines
1.1 KiB
CMake
21 lines
1.1 KiB
CMake
file(MAKE_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/test/depth1/depth2/depth3")
|
|
execute_process(COMMAND ${CMAKE_COMMAND} -E create_symlink "${CMAKE_CURRENT_BINARY_DIR}/test" "${CMAKE_CURRENT_BINARY_DIR}/test/depth1/depth2/depth3/recursion")
|
|
|
|
file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/test/abc" "message to write")
|
|
execute_process(COMMAND ${CMAKE_COMMAND} -E create_symlink "${CMAKE_CURRENT_BINARY_DIR}/test/abc" "${CMAKE_CURRENT_BINARY_DIR}/test/depth1/depth2/depth3/file_symlink")
|
|
|
|
file(GLOB_RECURSE CONTENT_LIST FOLLOW_SYMLINKS "${CMAKE_CURRENT_BINARY_DIR}/test/*")
|
|
list(LENGTH CONTENT_LIST CONTENT_COUNT)
|
|
message("content: ${CONTENT_COUNT} ")
|
|
message("${CONTENT_LIST}")
|
|
|
|
file(GLOB_RECURSE CONTENT_LIST LIST_DIRECTORIES false FOLLOW_SYMLINKS "${CMAKE_CURRENT_BINARY_DIR}/test/*")
|
|
list(LENGTH CONTENT_LIST CONTENT_COUNT)
|
|
message("content: ${CONTENT_COUNT} ")
|
|
message("${CONTENT_LIST}")
|
|
|
|
file(GLOB_RECURSE CONTENT_LIST LIST_DIRECTORIES true FOLLOW_SYMLINKS "${CMAKE_CURRENT_BINARY_DIR}/test/*")
|
|
list(LENGTH CONTENT_LIST CONTENT_COUNT)
|
|
message("content: ${CONTENT_COUNT} ")
|
|
message("${CONTENT_LIST}")
|