The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
It might be possible to build the package by invoking commands from the debian rules file directly, but it is probably easier to use dpkg-buildpackage to build a package locally as long as your local system matches your target system.
The release repository bloom created has branches of the form ${packagetype}/${rosdistro}/${suite}/${package}. For example, debian/kinetic/xenial/qt_ros_interface From a local checkout of this branch you can run the command dpkg-buildpackage -b -uc. This will build the binary package only (-b), and will not attempt to sign the changes file (-uc). This probably isn't what you want to be doing for your official release packages but it is suitable for quickly building debs.
| | 2 | No.2 Revision |
It might be possible to build the package by invoking commands from the debian rules file directly, but it is probably easier to use dpkg-buildpackage to build a package locally as long as your local system matches your target system.
After running bloom you can create a local clone of the release repository to build your package.
The release repository bloom created has branches of the form ${packagetype}/${rosdistro}/${suite}/${package}. For example, debian/kinetic/xenial/qt_ros_interface From a local checkout of this branch you can run the command dpkg-buildpackage -b -uc. This will build the binary package only (-b), and will not attempt to sign the changes file (-uc). This probably isn't what you want to be doing for your official release packages but it is suitable for quickly building debs.
| | 3 | No.3 Revision |
It might be possible to build the package by invoking commands from the debian rules file directly, but it is probably easier to use dpkg-buildpackage to build a package locally as long as your local system matches your target system.
If your package depends on any other custom packages, you will need to make sure that you build and install those packages first.
After running bloom you can create a local clone of the release repository to build your package.
The release repository has branches of the form ${packagetype}/${rosdistro}/${suite}/${package}. For example, debian/kinetic/xenial/qt_ros_interface From a local checkout of this branch you can run the command dpkg-buildpackage -b -uc. This will build the binary package only (-b), and will not attempt to sign the changes file (-uc). This probably isn't what you want to be doing for your official release packages but it is suitable for quickly building debs.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
