A superproject providing all the libraries Meddy has to offer. Each one is individually usable, although some may depend on others.
MeddySDK
- MeddySDKCLI (executable)
- MeddySDK_Meddyproject (library)
- MeddySDK_Meddydata (library)
- MeddySDK_DAM (library)
These projects are built together using FetchContent in CMake. This means they configure together (all from the same invocation of CMake), which makes debugging and development easier with the subprojects.
There is also a "superbuild" version of this project structure which uses ExternalProject in CMake to configure each project in isolation, before they get built together. See: MeddySDKSuperbuild.
Built with CMake - cross-platform, standardized, and IDE-friendly.
We provide CMake presets, which handle feeding arguments to CMake for you.
Most IDEs provide built-in CMake integration.
Has the "CMake Tools" and "C/C++" extensions, both developed by Microsoft.
Has very nice integration, but they seem behind when it comes to supporting the latest CMake features. I've had experiences where I have to switch to VS Code because of this.
This project is fully isolated from its dependencies, and therefore must be tied together by a superproject. See MeddySDKStandalone for a complete build setup.
Command line: cmake --preset="win-debug-default".
IDE: Choose the win-debug-default configure preset, and "configure" the CMake project.
Command line: cmake --build --preset="win-debug".
IDE: Choose the win-debug build preset, and "build" it.
Here's how to package the build into a distributable product.
See "Build Instructions" above.
Command line: cpack --preset="meddysdkcli-win-debug-nsis".
IDE: Choose the meddysdkcli-win-debug-nsis package preset, and "package" it.
Here's how to run automated tests, to verify that our code behaves as intended.
See "Build Instructions" above.
Command line: ctest --preset="meddysdk-win-debug".
IDE: Choose the meddysdk-win-debug test preset, and "run tests".