I tried getting 2024.04.23 working with python_qt_binding
without success (none of the backends built in a clean chroot), but after the upgrade to Python 3.12, none of them will build even in my host environment.
This, combined with long build times and the faster update pace of Arch compared to ROS causing dependency issues, has led me to decide to disown this package.
Search Criteria
Package Details: ros2-iron 2024.04.23-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/ros2-iron.git (read-only, click to copy) |
---|---|
Package Base: | ros2-iron |
Description: | A set of software libraries and tools for building robot applications |
Upstream URL: | https://docs.ros.org/en/iron/ |
Licenses: | Apache-2.0 |
Submitter: | 14mRh4X0r |
Maintainer: | None |
Last Packager: | 14mRh4X0r |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2023-05-30 08:03 (UTC) |
Last Updated: | 2024-07-02 16:01 (UTC) |
Dependencies (4)
- lttng-ust
- qt6-base (qt6-base-headlessAUR, qt6-base-gitAUR)
- ros2-arch-depsAUR
- git (git-gitAUR, git-glAUR) (make)
Required by (0)
Sources (2)
14mRh4X0r commented on 2024-07-02 16:03 (UTC)
DragonflyRobot commented on 2024-06-14 18:31 (UTC)
Hello! I know for recent builds, there is an issue with Fortified build requiring optimization. It is failing at the mimick_vendor package and I resolved the error by stripping the environment CMAKE flags from the _FORTIFY_SOURCE variable letting the individual CMAKE files autoselect and override the build variables. That seems to work on my modified PKGBUILD file. Since I cannot push here, I have cloned this repo to my personal Github with hopes that @14mRh4X0r will update the AUR PKGBUILD!
https://github.com/DragonflyRobotics/ros2-iron-fork
Please let me know if you want me to push via a more direct means which I would prefer.
rossbridger.cc commented on 2024-05-25 17:58 (UTC)
I notice that both ros2-iron and ros2-humble depend on qt6, but ros2-arch-deps depends on qt5. Is it possible to unify the qt version?
zergler commented on 2024-05-18 14:23 (UTC) (edited on 2024-05-18 15:07 (UTC) by zergler)
@Sir-Photch Add the following before colcon build
to fix
printf '{ "names": { "tracetools" : { "cmake-args": ["-DTRACETOOLS_TRACEPOINTS_EXCLUDED=ON"]}}}' > colcon.meta
shtrophic commented on 2024-05-10 08:25 (UTC)
Errors on tracetools:
--- stderr: tracetools
In file included from /usr/include/lttng/tracepoint-event.h:69,
from /home/chris/Source/ros2-iron/src/build/tracetools/include/tracetools/tp_call.h:508,
from /home/chris/Source/ros2-iron/src/ros2/src/ros2/ros2_tracing/tracetools/src/tp_call.c:18:
/home/chris/Source/ros2-iron/src/build/tracetools/include/tracetools/tp_call.h: In function ‘lttng_ust__event_probe__ros2___rclcpp_ring_buffer_enqueue’:
/home/chris/Source/ros2-iron/src/build/tracetools/include/tracetools/tp_call.h:474:5: error: initialization of ‘const uint64_t *’ {aka ‘const long unsigned int *’} from ‘uint64_t’ {aka ‘long unsigned int’} makes pointer from integer without a cast [-Wint-conversion]
474 | ctf_integer(const uint64_t *, index, index_arg)
| ^~~~~~~~~~~
make[2]: *** [CMakeFiles/tracetools.dir/build.make:104: CMakeFiles/tracetools.dir/src/tp_call.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:161: CMakeFiles/tracetools.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
---
14mRh4X0r commented on 2024-04-25 09:58 (UTC)
Hi all, sorry for the delay in getting this package updated. I'm currently in the process of making sure everything works for version 2024-04-23, which may take a day or so with all the compile time (and me not paying attention to the build).
etherswangel commented on 2024-04-19 04:41 (UTC)
@enf yes, at least it works for me. You may need to install shiboken2 related packages if problems encountered, but that's included in ros2-arch-deps recently so simply removing the option should be fine:)
enf commented on 2024-04-18 22:11 (UTC)
Has anyone managed to get rqt working? Is it enough removing the --packages-skip-by-dep python_qt_binding
option from the PKGBUILD?
kistlin commented on 2024-04-18 15:25 (UTC)
@Sir-Photch thanks! The build worked fine. I don't have orocos-kdl
installed and the build was successful.
shtrophic commented on 2024-04-16 07:43 (UTC)
@kistlin: So the diff for building (if you have -D_FORTIFY_SOURCE=3
set) is just this:
diff --git a/PKGBUILD b/PKGBUILD
index e5dd6c5..c68475b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -58,8 +58,8 @@ build() {
## For people with the old version of makepkg.conf
unset CPPFLAGS
## For people with the new version of makepkg.conf
- CFLAGS="${CFLAGS//-Wp,-D_FORTIFY_SOURCE=2[[:space:]]}"
- CXXFLAGS="${CXXFLAGS//-Wp,-D_FORTIFY_SOURCXXE=2[[:space:]]}"
+ CFLAGS="${CFLAGS//-Wp,-D_FORTIFY_SOURCE=3[[:space:]]}"
+ CXXFLAGS="${CXXFLAGS//-Wp,-D_FORTIFY_SOURCXXE=3[[:space:]]}"
# Build
colcon build --merge-install ${_colcon_extra_args} --packages-skip-by-dep python_qt_binding
also, the build seems to depend on orocos-kdl
. Maybe this is missing from ros2-arch-deps
though?
Pinned Comments
14mRh4X0r commented on 2024-07-02 16:03 (UTC)
I tried getting 2024.04.23 working with
python_qt_binding
without success (none of the backends built in a clean chroot), but after the upgrade to Python 3.12, none of them will build even in my host environment. This, combined with long build times and the faster update pace of Arch compared to ROS causing dependency issues, has led me to decide to disown this package.