Adding a so-version means defining an ABI level. This level is decoupled
from the ordinary version, even a major version change doesn't
necessarily mean that the so-version should change (and thus have all
dependencies to be rebuilt).
Adding the public header to clarify the setup.
Note: cherry-pick from PR #231
Conflicts:
CMakeLists.txt
Author: Alec Leamas <leamas.alec@gmail.com>
Date: Tue Sep 22 13:28:04 2020 +0200
Gbp-Pq: Name 0002-cmake-Add-defined-so-version-and-public-header-to-li.patch
Signed-off-by: Alex Moriarty <alex.moriarty@picknik.ai>
Cmake made major changes in the 2.x -> 3.0 switch, keeping the 2.x
compatiblity just isn't worth it. Since serial anyway doesn't build on
versions before xenial, use xenial's cmake at 3.5 as baseline.
Cherry-pick from PR #231
Conflicts:
CMakeLists.txt
Author: Alec Leamas <leamas.alec@gmail.com>
Date: Tue Sep 22 13:08:46 2020 +0200
Gbp-Pq: Name 0001-cmake-Use-cmake-3.5-add-project-setup.patch
Signed-off-by: Alex Moriarty <alex.moriarty@picknik.ai>
This couldn't be cherry-picked because but essentially the same change
from the ros2 branch here:
d8d160678a
Fixes this error:
```
/usr/bin/ld: /home/alex/ros/h/robotiq/install/serial/lib/libserial.a(serial.cc.o): relocation R_X86_64_PC32 against symbol `_ZTVN6serial6SerialE' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
```
Signed-off-by: Alex Moriarty <alex.moriarty@picknik.ai>
