# I am trying to build a navigation stack

**URL:** <https://forum.ubiquityrobotics.com/t/i-am-trying-to-build-a-navigation-stack/759>\
**Category:** Uncategorized\
**Created:** [March 21, 2021, 9:32am UTC](https://forum.ubiquityrobotics.com/t/i-am-trying-to-build-a-navigation-stack/759 "2021-03-21T09:32:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![IngeniousDoc](https://forum.ubiquityrobotics.com/letter_avatar_proxy/v4/letter/i/94ad74/32.png) [@IngeniousDoc](https://forum.ubiquityrobotics.com/u/IngeniousDoc)\
**Post date:** [March 21, 2021, 9:32am UTC](https://forum.ubiquityrobotics.com/t/i-am-trying-to-build-a-navigation-stack/759/1 "2021-03-21T09:32:29Z")

</div>

So I’ve been using “catkin\_make” to build the packages inside my catkin\_ws, but there is this package that is really giving me a hard time because it can only be built thru “catkin build” (neither “catkin\_make” nor “catkin\_make\_isolated”). When I tried to build it using “catkin build”, it gave me the error shown in the screenshot.

 ![WhatsApp Image 2021-03-20 at 6.03.34 PM](https://frm.ubiquityrobotics.com/uploads/default/original/1X/d024e6f2b10febb208e7f4602b1d47be19cc053e.jpeg)

My question is, how can I build this package? and for the future, how can I use both “catkin\_make” and “catkin build” without getting much pain?

---

<div class="post-metadata">

**Author:** ![MoffKalast](https://forum.ubiquityrobotics.com/user_avatar/forum.ubiquityrobotics.com/moffkalast/32/214_2.png) [@MoffKalast](https://forum.ubiquityrobotics.com/u/MoffKalast)\
**Post date:** [March 24, 2021, 11:02am UTC](https://forum.ubiquityrobotics.com/t/i-am-trying-to-build-a-navigation-stack/759/2 "2021-03-24T11:02:54Z")

</div>

Ah yes, the simplest way to solve that is to create a separate workspace just for that. So beside your `catkin_ws` you’ll need to make another, perhaps `catkinbuild_ws`, then add only the build packages into the `src` folder of that one and `catkin build`.

Of course don’t forget to source the new workspace in .bashrc as well (note that the order of sourcing matters). To verify that all has been sourced correctly run `env | grep CMAKE` and you should see all the workspace paths listed, along with the ros installation dir. I can’t recall the correct order off the top of my head but it should be easy to switch them and check.