ok. thanks. what needs to contain in binary package installation of debian/RPM is the content under the `install` folder of the corresponding package, am I right ? If it's right, does it work with the following process for RPM creation for quick prototype/verification? as follow:
- For RPM `%build` part: invoke the `colcon` to build a package normally as the way to build with source code
- For RPM `%install` and `%files` part: manually add the content of the corresponding package underneath the `install` folder of the workspace (that's to say you have already know the details of the `install` folder with the way of source building)
- finally, rpmbuild with the above rules of spec file to create the RPM package
I know that it's not feasible to manually create spec and RPM for many package in this way, and it also requires a great deal of effort to maintain, just try to verify one project before further code development. :sweat_smile:
---
[Visit Topic](
https://discourse.ros.org/t/ros2-package-rpm-building-without-the-top-cmakelists-txt-for-cmake/5933/9) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)