# Different packages for Debug and Release versions ?

**URL:** <https://discourse.cmake.org/t/different-packages-for-debug-and-release-versions/10151>\
**Category:** Code\
**Created:** [February 21, 2024, 4:27pm UTC](https://discourse.cmake.org/t/different-packages-for-debug-and-release-versions/10151 "2024-02-21T16:27:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oodini](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/o/db5fbb/32.png) [@Oodini](https://discourse.cmake.org/u/Oodini)\
**Post date:** [February 21, 2024, 4:27pm UTC](https://discourse.cmake.org/t/different-packages-for-debug-and-release-versions/10151/1 "2024-02-21T16:27:46Z")

</div>

Hello,

Should I group the Debug and Release versions of a library in one single package, or make a package for each ?

What is the recommanded practice ?

---

<div class="post-metadata">

**Author:** ![craig.scott](https://discourse.cmake.org/user_avatar/discourse.cmake.org/craig.scott/32/20_2.png) [@craig.scott](https://discourse.cmake.org/u/craig.scott)\
**Post date:** [February 21, 2024, 11:02pm UTC](https://discourse.cmake.org/t/different-packages-for-debug-and-release-versions/10151/2 "2024-02-21T23:02:41Z")

</div>

Generally, you’d want a single package. When generating the package, you’d need to install Debug and Release versions, then package them up together into a single package with a single `<packageName>-config.cmake` file, etc. If you need to do this, using a multi-config generator like “Ninja Multi-Config” is likely to be easier, since you can use a single build directory to produce all the required content to install.

---

<div class="post-metadata">

**Author:** ![Oodini](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/o/db5fbb/32.png) [@Oodini](https://discourse.cmake.org/u/Oodini)\
**Post date:** [February 22, 2024, 7:32am UTC](https://discourse.cmake.org/t/different-packages-for-debug-and-release-versions/10151/3 "2024-02-22T07:32:08Z")

</div>

OK, thank you !
