tree: 260bb401628ae5f17bd326c60623bd1f8f7f2a99 [path history] [tgz]
  1. .idea/
  2. api/
  3. build-utils/
  4. drivers/
  5. examples/
  6. generated-sources/
  7. integrations/
  8. spi/
  9. tools/
  10. transports/
  11. .clang-format
  12. .gitignore
  13. CMakeLists.txt
  14. CODE_CONVENTIONS.md
  15. design-guidelines.adoc
  16. fetch-dependencies.sh
  17. pom.xml
  18. README.md
  19. SonarcloudBuildWrapperHack.groovy
plc4c/README.md

Setting up in CLion

Per default CLion will not be able to run the tests. However, it's pretty simple to set up.

In order to make this happen, you should add another Profile to your CMake configuration.

You can do this by going to:

Preferences... / Build, Execution, Deployment / CMake

In the Profiles list, click on the + button to add a new profile.

I gave this profile the name Test.

In the settings select the Build type = Debug, Toolchain = Use Default. CMake options = -DUNITY_VERSION:STRING=2.5.2 -DBUILD_PHASE=test-compile.

Leave the rest unchanged (which is actually empty).

After saving you can select the Test profile in the Configurations Drop-Down. After that is selected, the tests should be available.