Hi Cheimarios Nikolaos, Vissarion Fysikopoulos and the Apothesis community, I've been exploring the Apothesis repository and attempted a build on Windows using MSYS2/MinGW, where I ran into a few issues — CMake compatibility errors, missing toolchain configuration (CMake defaulting to NMake/MSVC), and compilation failures due to C++17 features like <any> not being supported on older GCC versions. I worked through these and opened a PR(link <https://github.com/nixeimar/Apothesis/pull/52>) addressing all three: - Bumped cmake_minimum_required to 3.10 - Enforced C++17 standard explicitly - Added compiler guards and Windows/MinGW build guidance Beyond the fix, I've been going through the codebase trying to understand how Apothesis works internally — the simulation model, how the C++ core is laid out, and where a Python interface would naturally fit. Still working through it, but I'd rather do that homework before touching any binding code. The Python bindings project is what drew me here. I think a pybind11-based interface that feels natural to Python users while keeping the underlying performance intact would make Apothesis a lot more accessible to the research and ML community. I'd love to know if this aligns with what the mentors have in mind, and if there are specific parts of the codebase I should focus on understanding first. Thanks for your time. Best regards, Abhigyan
---- Λαμβάνετε αυτό το μήνυμα απο την λίστα: Λίστα αλληλογραφίας και συζητήσεων που απευθύνεται σε φοιτητές developers \& mentors έργων του Google Summer of Code - A discussion list for student developers and mentors of Google Summer of Code projects., https://lists.ellak.gr/gsoc-developers/listinfo.html Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. ταχυδρομείου στη διεύθυνση <gsoc-developers+unsubscribe [ at ] ellak [ dot ] gr>.