Closed adham-elarabawy closed 4 years ago
Just a heads up, it is considered best practice for projects to have a root catkin_ws
for the packages. I've also noticed that you decided to go with one big package for everything. I recommend breaking down the codebase into multiple packages.
For example, the ROV MIND repository has a dedicated ros_ws
that houses seperate packages, such as global launch files, various hardware interfaces, and other code functions.
In Bytes Robotics we have around 6 packages for our main robot that are ours, and 8 or so that we build from forks.
@caelinsutch That's a good point. I'm only using 1 custom package though (all of the other packages are installed via apt-get), so it seems to be cleaner to have my repo be the package. What do you think?
@caelinsutch Actually, I heeded your advice and restructured my repo again to follow the format you outlined. Thanks for the tip!
I realized that my previous dir structure meant that I was uploading my catkin workspace to github. This is completely unnecessary and confusing for anyone trying to replicate my project. So, I decided to do a major restructuring of my repository to facilitate ROS usage.