This adds an option for cmake to skip the pymavlink install. Without
this option a local install will still try to install pymavlink
system-wide which is not required in my use case, and would also require
root privileges.
* CMake: Using find_program to find mavgen(.py)
If neither mavgen nor mavgen.py have been found as executables in $PATH, then we will fallback to the hardcoded location (submodule).
Signed-off-by: Thomas Karl Pietrowski <thopiekar@gmail.com>
* CMake: Adding USE_SYSTEM_PYMAVLINK and cleanups
Adding the USE_SYSTEM_PYMAVLINK option and made some cleanups.
Enabling the option will correctly turn on the lookup for mavlink.py and generating the sources works as expected.
Signed-off-by: Thomas Karl Pietrowski <thopiekar@gmail.com>
- Mavlink 2.0 is built from v1.0 folder
- Build both MavLink 1.0 and Mavlink 2.0 C libraries
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Otherwise, it fails miserably with
from . import mavparse
ValueErrorValueError: : Attempted relative import in non-packageAttempted relative import in non-package
CMakeLists.txt: Proper use LIB_SUFFIX and LIB_INSTALL_DIR enable some 64 bit Linux distros find pkgconfig file
CmakeLists.txt: Install python on default site_packages instead of pyshared. Most Linux distros already made the transition,
for referennce Debian statement https://wiki.debian.org/Python/TransitionToDHPython2?action=show&redirect=Python%2FPyCentral2DhPython2
pc.in: Use correct package version and add proper description.
Signed-off-by: Helio Chissini de Castro <helio@kde.org>
Julian Oes