- CMakeLists.txt: CMake will handle how to build this project
- Dockerfile.development: It creates a Docker container which contains everything which is necessary do develop for OpenMP. It will be updated as we use new technologies
- Makefile: It contains all the predefined commands that you'll need for development. If there is another target name after colon, that means it will also run that target. For example the
runtarget will alsobuildit before. To use it runmake target, instead of target write one of the followings:build: builds your code in release mode to release directory (you can turn off the warning here if some HPC idioms require "dirty" code)run: runs the code with some predefined parameters (feel free to change those)clean: removes all build directory, use it if something "strange" happens during buildtbuild: builds the code in debug mode and also build the test codes from the test directorytest: runs all tests in the test directorybbuild: build the code in release and also build the code in the benchmark directorybenchmark: run the benchmark binary, use the filter with any regex to run a subset of all benchmarksvalgrind: build the code in debug mode and runs it under valgrind. Valgrind can check for memory leaks and wrong memory access (like out of range access)testAll: runs both thetestand thevalgrindtarget
- include: contains the header file(s) of the simulation code
- src: contains the source files
- CMakeLists.txt: add the local source file(s) to the binary, and adds the include to the path (makes you able to import)
- benchmark: Contains the code for the benchmark
- CMakeLists.txt: downloads the benchmark library and links it to the benchmark binary
- test: Contains the code for testing
- CMakeLists.txt: downloads the Google test library and links it to the test binary
- .devcontainer: this describes who to setup the container environment
- .vscode: It can contain many settings for different extensions and the vanilla VSCode too, but at the moment the only settings are about how to use the CMake extension. The first part sets the cmake flags, by defult it will build all targets (normal, test and benchmark). The second part is something you might want to change. It describes what programs argument should it pass when you run it in debug mode (from the bottom blue bar)
forked from khbence/ppcuparprog
-
Notifications
You must be signed in to change notification settings - Fork 0
reguly/ppcuparprog
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published
Languages
- C++ 65.9%
- CMake 31.4%
- Makefile 2.7%