Closed ntorresalberto closed 3 years ago
Thanks for the contribution!
A quick fix to fix the build:
diff --git a/.ci/Dockerfile.bionic b/.ci/Dockerfile.bionic
index fb92e82..07688fb 100644
--- a/.ci/Dockerfile.bionic
+++ b/.ci/Dockerfile.bionic
@@ -11,5 +11,6 @@ RUN apt-get update && apt-get install -y \
libeigen3-dev \
libpoco-dev \
rename \
+ rpm \
valgrind \
&& rm -rf /var/lib/apt/lists/*
diff --git a/.ci/Dockerfile.focal b/.ci/Dockerfile.focal
index c15aade..55c0b3b 100644
--- a/.ci/Dockerfile.focal
+++ b/.ci/Dockerfile.focal
@@ -12,5 +12,6 @@ RUN apt-get update && apt-get install -y \
libeigen3-dev \
libpoco-dev \
rename \
+ rpm \
valgrind \
&& rm -rf /var/lib/apt/lists/*
diff --git a/.ci/Dockerfile.xenial b/.ci/Dockerfile.xenial
index 0fbc135..393006e 100644
--- a/.ci/Dockerfile.xenial
+++ b/.ci/Dockerfile.xenial
@@ -11,5 +11,6 @@ RUN apt-get update && apt-get install -y \
libeigen3-dev \
libpoco-dev \
rename \
+ rpm \
valgrind \
&& rm -rf /var/lib/apt/lists/*
Thanks for the contribution!
A quick fix to fix the build:
I added these changes and rebased the branch over develop but github is not reflecting the changes. Should I create a new PR? Here's the commit: https://github.com/ntorresalberto/libfranka/commit/31e5e39e6882309a020267fbcb126212268c4dac
edit: nevermind, it's showing now.
Merged, thank you!
Hi, @fwalch @sgabl
I've recently tried to use this functionality but according to the main CMakeLists.txt
commit history these changes are no longer available since commit cac09ea3377f76f51c5d734f4d9a69701cebc468 even though they do appear in the previous commit 700e3808e6a4289ceca0a4a1c87af0e4fca12b5f.
I don't see the removal of the relevant code in the changelog so I guess it could have been a bad merge or a push force somewhere? Would it be possible to cherry-pick these changes?
Uh yeah something strange happened there. I am sorry. We also have the problem that some changes that happend in the CmakeList were resulting in failing builds on the ROS buildfarm. As it only happens on the buildfarm and not in the test builds for the buildfarm, we can only test by doing a full release. So for the next time we will probably try to revert all the changes in CMakeLists.txt or maybe we find the root cause of the problem. Then we can probably reapply your changes.
Hi, I've added:
USE_SOURCE_PERMISSIONS
allows maintaining the original permissions in the case of creation of while usinginstall(DIRECTORY ...)
(check docs).CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS
sets default permissions. By default, it hasWORLD_WRITE
was enabled which makes no sense for installed system files.CPACK_DEBIAN_PACKAGE_RELEASE
(the proper way to set a build number according to cpack docs). To expand a bit on this,CPACK_DEBIAN_PACKAGE_VERSION
has theMAJOR.MINOR.PATCH-RELEASE
info deduced fromCPACK_PACKAGE_VERSION
(which in term comes from the projectVERSION
string) and should not be manually modified. Here's a quote from the cpack docs:PACKAGE_RELEASE
variable. Example: you've releasedlibfranka-0.8.0-1
and now want to releaselibfranka-0.8.0-2
(there must be a new commit withset(PACKAGE_RELEASE 2)
).