Compile, Build and Run C++

You need to have a dir with your .cpp files and the CMakeLists.txt file.

Here you can see an example of these types of directories:


Then, in this same directory, you need to create a build folder, then compile (using the CMakeLists.txt file information), then building the executable file and then launch the (just created) executable file:

$ mkdir -p build
$ cd build
$ cmake .. -DCMAKE_BUILD_TYPE=Release
$ make name_of_file
$ ./name_of_file

You just need this to run the recently created file. Every time you change the .cpp original file, you should run the last 3 command lines in order to test that changes when running the program.

The build folder should contain the following:


 

 


Comments

Post a Comment

Popular posts from this blog

Remote Control of UR10e via MoveIt (ROS)

Image
Installation First, install the External Control URCap on the UR10e Teach Pendant. See this post , to further instructions. Then, you will need to install a few packages on your Ubuntu system: sudo apt install ros-noetic-moveit sudo apt-get install ros-noetic-industrial-robot-status-interface sudo apt-get install ros-noetic-scaled-controllers sudo apt-get install ros-noetic-pass-through-controllers sudo apt-get install ros-noetic-ur-client-library sudo apt-get install ros-noetic-velocity-controllers sudo apt-get install ros-noetic-force-torque-sensor-controller ( Note: At this moment, if you do not have a catkin workspace, you should now create one, by following the steps described here ) cd catkin_ws/src git clone https://github.com/afonsocastro/larcc_interface.git git clone https://github.com/ros-industrial/ur_msgs.git cd ~/catkin_ws catkin_make  Finally, to establish the communication between the robot and the computer, it is required to connect an Ethernet cable from the UR1...
Read more

UR10e control architecture

Image
Now that I am able to control the arm of the robot as well as the gripper, it is now time to create an interface that can be used to control both the arm and the gripper.  This interface should be completely agnostic to any use case that is being developed. Since gripper control and arm control are two independent procedures that can be running simultaneously, this interface should put these two controllers at the same level. Following this philosophy, any job that I want to develop in the future will be able to call any one of these controllers by the same method! Here we can see the structure of the first complete job.  In this case, an object that is continuously being tracked through a RGB-D camera is followed by the robot arm and then is picked up and stored in a box.  As we can see, both controllers (arm and gripper) are at the same level, and the job1 ROS node is communicating with both of them simultaneously. The gripper controller is described in this previous p...
Read more

ViSP - first tutorial

Image
In order to start using (for the very first time) ViSP, I followed the tutorial for installation from source for linux ubuntu: https://visp-doc.inria.fr/doxygen/visp-3.4.0/tutorial-install-ubuntu.html I settled for the Quick ViSP installation , since probably most of the 3rd parties that compose the Advanced ViSP installation won't be useful for my particular goal. Besides that, even if some of the 3rd parties turn out to be useful, they can be installed afterward. First, I created a ViSP workspace: $ echo "export VISP_WS=$HOME/visp-ws" >> ~/.bashrc $ source ~/.bashrc $ mkdir -p $VISP_WS Installed the standard (recommended) 3rd parties: $ sudo apt-get install libopencv-dev libx11-dev liblapack-dev libeigen3-dev libv4l-dev libzbar-dev libpthread-stubs0-dev libjpeg-dev libpng-dev libdc1394-22-dev Cloned the source code: $ cd $VISP_WS $ git clone https://github.com/lagadic/visp.git  And created the build folder, to build ViSP: $ mkdir -p $VISP_WS/visp-build $ cd $VI...
Read more