Changeset View
Changeset View
Standalone View
Standalone View
tests/gtests/CMakeLists.txt
| # GTest | |||||
| if(WITH_GTESTS) | if(WITH_GTESTS) | ||||
| include(GTestTesting) | |||||
| add_definitions(${GFLAGS_DEFINES}) | |||||
| add_definitions(${GLOG_DEFINES}) | |||||
| add_definitions(-DBLENDER_GFLAGS_NAMESPACE=${GFLAGS_NAMESPACE}) | |||||
| # Otherwise we get warnings here that we cant fix in external projects | # Otherwise we get warnings here that we cant fix in external projects | ||||
sergey: `# This runner takes care of ...` | |||||
| remove_strict_flags() | remove_strict_flags() | ||||
| # Build common test runner | |||||
| add_subdirectory(runner) | |||||
| # Build tests not yet ported to the common runner | |||||
| add_subdirectory(testing) | add_subdirectory(testing) | ||||
| add_subdirectory(blenkernel) | |||||
| add_subdirectory(blenlib) | add_subdirectory(blenlib) | ||||
| add_subdirectory(blenloader) | add_subdirectory(blenloader) | ||||
Done Inline ActionsDoing all this setup for blender_test and then going into all the subdirectories is causing problems here with duplicate build flags, that then give build errors. We can split building the test runner into another folder, at least as long as we need subdirectories here for non-ported tests. brecht: Doing all this setup for `blender_test` and then going into all the subdirectories is causing… | |||||
| add_subdirectory(guardedalloc) | add_subdirectory(guardedalloc) | ||||
| add_subdirectory(bmesh) | add_subdirectory(bmesh) | ||||
| add_subdirectory(functions) | add_subdirectory(functions) | ||||
Done Inline ActionsThe logic here should be changed like we did in: rB59b523c3c98e: Fix build with USD, Clang and Linux. brecht: The logic here should be changed like we did in: {rB59b523c}. | |||||
| if(WITH_CODEC_FFMPEG) | if(WITH_CODEC_FFMPEG) | ||||
| add_subdirectory(ffmpeg) | add_subdirectory(ffmpeg) | ||||
| endif() | endif() | ||||
Done Inline ActionsMaybe a good name for this executable is just blender_test rather than bf_gtest_runner_test? I guess running it will work like any other test executable, the difference would be that for ctest it's called with specific arguments to run a subset of the tests. brecht: Maybe a good name for this executable is just `blender_test` rather than… | |||||
| if(WITH_ALEMBIC) | if(WITH_ALEMBIC) | ||||
| add_subdirectory(alembic) | add_subdirectory(alembic) | ||||
| endif() | endif() | ||||
| if(WITH_USD) | if(WITH_USD) | ||||
| add_subdirectory(usd) | add_subdirectory(usd) | ||||
| endif() | endif() | ||||
| endif() | endif() | ||||
# This runner takes care of ...