-
-
Notifications
You must be signed in to change notification settings - Fork 199
Description
Discussed in #1380
Originally posted by JanFellner September 18, 2025
I have an issue since longer and still have not found a solution to it.
Sentry native is checked out a subodule in another repository, thus i cannot really change the cmake files.
Thus i am configuring them through the cmake command line parameters
This is the current command line:
cmake -B buildwin32_142 -DSENTRY_BACKEND=crashpad -DCLIENT_STACKTRACES_ENABLED=ON -DSENTRY_INTEGRATION_NONE=OFF -DSENTRY_BUILD_TESTS=OFF -DSENTRY_BUILD_EXAMPLES=OFF -DSENTRY_INTEGRATION_QT=OFF -DSENTRY_BUILD_SHARED_LIBS=OFF -DSENTRY_BUILD_RUNTIMESTATIC=ON -DCMAKE_DEBUG_POSTFIX="d" -DCMAKE_INSTALL_PREFIX=. -DCMAKE_INSTALL_LIBDIR=../lib_142 -DCMAKE_INSTALL_BINDIR=../lib_142 -A Win32 -G "Visual Studio 17 2022" 1>cmake_sentry_native_win32_142.log 2>cmake_sentry_native_win32_142.err
Cmake version is 3.31.6-msvc6. Using sentry-native master head which i just updated
I get really wiered errors about crashpad_wer.rc beeing written multiple time (in total 15 times)
`CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Error in external/crashpad/handler/CMakeLists.txt:
Evaluation file to be written multiple times with different content. This
is generally caused by the content evaluating the configuration type,
language, or location of object files:
X:/dev/global/libs/sentry-native/buildwin32_vc143/crashpad_build/handler/crashpad_wer.rc
CMake Generate step failed. Build files cannot be regenerated correctly.`
Anybody else having seen this or has a hint how to solve it without patching the error logfile?