Skip to main content
SimilarExport ZIP
100%

CMakeLists.txt enable GTest

✓ Published0🌍 Public
IIoTeacher
Last edited Apr 8, 2020
Created on May 18, 2020

This example shows a CMake build configuration that conditionally enables Google Test (GTest) support for a C++ project named "modio". The code defines a build-time option triggered by the `test` variable set to "on", which activates testing features. When enabled, it compiles all source files from the `src` directory into a test executable called `runUnitTests` and links it against the `gtest` and `gtest_main` libraries. The configuration also registers the executable as a CTest test named `UnitTests` using `add_test`, and it sets up the necessary include paths for GTest's headers and source directory from the `ext/googletest` subdirectory.

AI-generated description

Similar vizzes

Loading thumbnail…

Tema 3.1 Compilación CMake y corrida GEF (gdb) del programas

This example documents a terminal session that guides a user through compiling a C program with CMake and debugging it with the GNU debugger (GDB). The material is presented as a markdown file containing step-by-step commands and notes, culminating in the use of `script` and `scriptreplay` utilities to record, claim, and share the interactive terminal session. The text demonstrates the compilation and debugging workflow for a specific project, named LDI-31, while explaining how to finalize the recording, access the playback URL, and distribute the session link to others.

IIoTeacher
52% match
Loading thumbnail…

Support CMAKE_CXX_STANDARD in older cmake versions

This example shows how to set the C++ standard in CMake while maintaining compatibility with older versions of the tool. It checks `CMAKE_VERSION` against version 3.1 and, for older versions, appends the `-std=c++11` flag to `CMAKE_CXX_FLAGS`. For newer versions, it uses the more modern `CMAKE_CXX_STANDARD` variable set to 11. The code references a Stack Overflow answer as its source, illustrating a common conditional pattern for cross-version build configuration.

CChristosT
50% match
Loading thumbnail…

Raspberry Pi Pico C/C++ SDK Example CMake File

This example shows a minimal CMake build configuration for compiling and linking a Raspberry Pi Pico C/C++ SDK project, specifically an executable named `blink`. The file sets required C and C++ standards, initializes the SDK with `pico_sdk_init()`, and defines the executable with `add_executable(blink blink.c)`. It links the `pico_stdlib` library to provide core Pico APIs, and includes `pico_add_extra_outputs` to generate additional build artifacts. Optional commented lines demonstrate enabling USB stdio via `pico_enable_stdio_usb` and adding wireless support with `pico_cyw43_arch_none`.

IIoTeacher
48% match
Loading thumbnail…

Gist 134c3254e89206cd8c069069456c9720

This example shows an Android application build configuration that relies on the Apache Cordova framework and the Gradle build system. It demonstrates how the build.gradle file dynamically applies plugins and dependencies based on settings from cdvHelpers, such as enabling Kotlin or Google Services support. The code uses the com.android.tools.build:gradle API and conditional classpath declarations to manage plugin versions and build reproducibility.

66ewis
48% match
Loading thumbnail…

Gist 578871

This example shows a Gist titled "Gist 578871" that integrates RSpec mocking and Authlogic into a Cucumber testing environment. It demonstrates how to configure RSpec's mock framework within Cucumber steps by explicitly setting up and tearing down mocks around each scenario. The code loads supporting files like `support.rb`, which requires `cucumber/rspec/doubles` and `rspec/core`, and uses `RSpec::Mocks::setup`, `verify`, and `teardown` in `Before` and `After` hooks. It also activates Authlogic’s test mode and resets `Sham` data. The rendering approach is code-based, not visual, focusing on test configuration.

DDylanFM
46% match
Loading thumbnail…

C++ Doxygen Detailed Example

This example shows how Doxygen configuration and header files document a C++ numerical computing project called MathUtils. The code defines a namespace structure with mathematical function types, error codes, and solver declarations, using Doxygen 1.8.14 with tags like `@brief`, `@param`, `@return`, and `@code` blocks. It demonstrates documentation of templated functions, class methods, and nested namespaces, with the Doxyfile setting the project name, brief description, and output directory to `./docs`. The visualization highlights how structured comments generate API reference pages for the Newton solver and XYChart plotting class.

IIoTeacher
45% match
Loading thumbnail…

module app

This example shows the Gradle build configuration for an Android application, highlighting the setup of project-level and module-level build scripts. It demonstrates how the code configures Android plugin versions, Kotlin support, and Google Services integration through conditional logic based on preferences. The build.gradle files use the Gradle build system with the Android Gradle plugin, Kotlin Gradle plugin, and dependency management via repositories like Google and JCenter. The configuration includes version checks for Kotlin and Google Services plugins, along with SDK version settings.

66ewis
45% match
Loading thumbnail…

Gist 578885

This example shows the results of running a Cucumber feature file twice: once with the `require` statement left as-is, and once after replacing it with the file’s contents. The terminal output displays a failing scenario with two skipped steps in the first run, followed by a passing scenario with two passing steps in the second. The visualization highlights the difference in outcome by pairing the two command-line outputs, each labeled with the cucumber command and profile. It demonstrates how a simple code substitution—in this case, inlining a required file—affects test execution, using the Ruby testing framework and its command-line interface.

DDylanFM
44% match