-
CPM.cmake
📦 CMake's missing package manager. A small CMake script for setup-free, cross-platform, reproducible dependency management.
-
pataro
A generic and modular Roguelike game on top of libtcod - I'll be back soon, just need a break!
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
electionguard-cpp
A C++ implementation of ElectionGuard specification focused on encryption components.
-
electionguard-ui
ElectionGuard monorepo in React & Typescript consisting of an api client, components, and apps to demonstrate examples of user interface for both voters and election staff.
CPM.cmake I have used peripherally while working on ElectionGuard, and my professor flagged this issue as one I could work on, but again I'm having a hard time grasping the logic of how this program works to start working on it. As I understand it, it's a script that CMake runs to get dependencies, similar to vcpkg. It's essentially just one script that interacts with CMake so I guess it can't be that hard to figure out, I'm just having a hard time working out the interaction with CMake and where one starts and the other begins. The error message in question for instance, file DOWNLOAD error: cannot create directory '/cpm' - Specify file by full, isn't found anywhere in the script so I'm guessing that's something CMake outputs based on interaction with CPM.cmake.
I am once again working on Pataro today, and I've succeeded in clearing up some issues and creating new ones. I've been stuck on an issue where Visual Studio was raising errors in the portion of the code where I call the cereal archive on some types, but was able to clear up that issue by moving the save function definitions out of their respective headers and into the corresponding .cpp files. Examining this repo and its use of cereal again, I was able to get a bit clearer of an idea of how it's implemented, and I included just about every relevant cereal header I could find to try and avoid any issues like the previous one popping up again (with the intention of later removing whichever I can to avoid redundant inclusions).
I am once again working on Pataro today, and I've succeeded in clearing up some issues and creating new ones. I've been stuck on an issue where Visual Studio was raising errors in the portion of the code where I call the cereal archive on some types, but was able to clear up that issue by moving the save function definitions out of their respective headers and into the corresponding .cpp files. Examining this repo and its use of cereal again, I was able to get a bit clearer of an idea of how it's implemented, and I included just about every relevant cereal header I could find to try and avoid any issues like the previous one popping up again (with the intention of later removing whichever I can to avoid redundant inclusions).
I am once again working on Pataro today, and I've succeeded in clearing up some issues and creating new ones. I've been stuck on an issue where Visual Studio was raising errors in the portion of the code where I call the cereal archive on some types, but was able to clear up that issue by moving the save function definitions out of their respective headers and into the corresponding .cpp files. Examining this repo and its use of cereal again, I was able to get a bit clearer of an idea of how it's implemented, and I included just about every relevant cereal header I could find to try and avoid any issues like the previous one popping up again (with the intention of later removing whichever I can to avoid redundant inclusions).
Aside from Pataro, I've been poking at ElectionGuard and CPM.cmake as well. Both of them are pretty much at the same status, which is - built and ready to be worked on - but the logic of how to do so completely eludes me.
ElectionGuard I think compiles to a .dll? From what I can understand it's a SDK so I guess there are implementations with a UI but the C++ version isn't one of them? In any case I have the project built but can't compile in Visual Studio to actually see what's going on. So you can imagine working on it would be difficult.