# Looking to Get Involved in the C++ Community!

**URL:** <https://discourse.bemanproject.org/t/looking-to-get-involved-in-the-c-community/346>\
**Category:** Beman Project Development\
**Tags:** community, cmake\
**Created:** [February 5, 2025, 11:00pm UTC](https://discourse.bemanproject.org/t/looking-to-get-involved-in-the-c-community/346 "2025-02-05T23:00:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Jeff-Garland](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/jeff-garland/32/23_2.png) [@Jeff-Garland](https://discourse.bemanproject.org/u/Jeff-Garland)\
**Post date:** [February 6, 2025, 1:10pm UTC](https://discourse.bemanproject.org/t/looking-to-get-involved-in-the-c-community/346/2 "2025-02-06T13:10:08Z")

</div>

Hi Chris and welcome!

There’s many ways to get involved, but cmake help is honestly perfectly timed. We’ve been having some long discussions about how best to deal with some issues. The big discussion is currently here, but there’s been discussions in our weekly tagup that I think didn’t get summarized here. Anyway, it’s very much an open topic at the moment.

> [@Make Beman Packageable](https://discourse.bemanproject.org/t/make-beman-packageable/331/3):
>
> If I had to choose, I would go with option 3 since find\_package(GTest) is the norm. Also, having a fallback to fetch and build from source isn’t a bad choice. However, if I am not mistaken the proposed way is to provide a toolchain file in the configuration step. This file is usually generated by the package manager, the concept is that you consume packages the way you want your package to be consumed! That way you create a consistent user experience. So, I think failing to find GTest if a toolc…

---

_[View the full topic](https://discourse.bemanproject.org/t/looking-to-get-involved-in-the-c-community/346)._