Package Details: ros-melodic-laser-assembler 1.7.7-6

Git Clone URL: https://aur.archlinux.org/ros-melodic-laser-assembler.git (read-only, click to copy)
Package Base: ros-melodic-laser-assembler
Description: ROS - Provides nodes to assemble point clouds from either LaserScan or PointCloud messages.
Upstream URL: https://wiki.ros.org/laser_assembler
Licenses: BSD
Submitter: GPereira
Maintainer: None
Last Packager: bionade24
Votes: 0
Popularity: 0.000000
First Submitted: 2018-05-13 18:42 (UTC)
Last Updated: 2021-03-23 02:02 (UTC)

Latest Comments

1 2 Next › Last »

jerry73204 commented on 2019-12-19 15:54 (UTC)

The build failed due to wrong path in prepare(). Please modify it to the following.

prepare() {
  cd "${srcdir}/${_dir}"
  patch -uN CMakeLists.txt "${srcdir}/CMakeLists-signal.patch" || return 1
}

hansbonini commented on 2019-05-31 03:32 (UTC)

boost_signals fix

add this to line 56 of PKGBUILD:

# Fix Boost Signals
    sed -i -e 's/signals//g' laser_assembler-release-release-melodic-laser_assembler-1.7.6-0/CMakeLists.txt

GPereira commented on 2019-01-09 18:24 (UTC)

Done

Eyolon commented on 2018-11-28 10:09 (UTC)

please update the source link with https://github.com/ros-gbp/laser_assembler-release/archive/release/melodic/laser_assembler/1.7.6.tar.gz

cbjamo commented on 2018-11-22 12:25 (UTC)

This package is now out of date, 1.7.6 fixes the boost issue.

cbjamo commented on 2018-11-14 20:50 (UTC) (edited on 2018-11-14 20:51 (UTC) by cbjamo)

Unless the patch causes issues for users of older versions of boost, a new release should come along soon. It should be noted that this package is not currently out of date, the latest release is 1.7.5. Until a new release is pushed, this patch (copied from the fix in the upstream git) will fix the build issue for us.

From 1a03f7c288ed03d7e21d764b1267338434db27e4 Mon Sep 17 00:00:00 2001
From: Tobias Fischer <t.fischer@imperial.ac.uk>
Date: Thu, 26 Apr 2018 11:05:41 +0100
Subject: [PATCH] Fix compilation issues with new boost

See https://github.com/ros/actionlib/issues/104
---
 test/test_assembler.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/test_assembler.cpp b/test/test_assembler.cpp
index c08de43..bc760a8 100644
--- a/test/test_assembler.cpp
+++ b/test/test_assembler.cpp
@@ -117,7 +117,7 @@ TEST_F(TestAssembler, non_zero_cloud_test)

   while(n_.ok() && !got_cloud_)
   {
-    cloud_condition_.timed_wait(lock, boost::posix_time::milliseconds(1000.0f));
+    cloud_condition_.timed_wait(lock, boost::posix_time::milliseconds(1000));
   }

   EXPECT_LT((unsigned int) 0, cloud_.points.size());
--
2.19.1

evopen commented on 2018-09-26 14:27 (UTC)

This tarball version can't be built with new boost. see: https://github.com/ros-perception/laser_assembler/commit/1a03f7c288ed03d7e21d764b1267338434db27e4 need to use upstream git version.

GPereira commented on 2018-06-22 19:07 (UTC)

Problem solved

Elephantusparvus commented on 2018-06-22 11:51 (UTC)

Another option might be to just disable testing. Then the test is not compiled. I think this should be done anyways.

https://aur.archlinux.org/packages/ros-melodic-urdf/#comment-651796

Elephantusparvus commented on 2018-06-22 09:42 (UTC) (edited on 2018-06-22 10:00 (UTC) by Elephantusparvus)

It seems like the interface for boost::posix_time::miliseconds() changed. (Seems like it should be constructed with a long: https://www.boost.org/doc/libs/1_67_0/doc/html/date_time/posix_time.html)

Here is a patch so it at least compiles: https://pastebin.com/zERZxGsr

Functionality is not checked, but I think it is "fine" because it is just a test and should not effect anything else.

E: Okay there is even a pull request pending for this: https://github.com/ros-perception/laser_assembler/pull/16 https://github.com/ros/actionlib/issues/104