>> http://libdivecomputer.org/ >> >> "Libdivecomputer is a cross-platform and open source library for >> communication with dive computers from various manufacturers." >> >> Tested by linking against https://github.com/kristapsdz/divecmd >> with a suunto d6i and using the native dctool(1). > > I would be willing to import this in the attached form > if someone provides an OK. > > I'd prefer to import all the diving ports below multimedia - it's > not a 100% fit, but comes close: there are hardware interfacing, > image processing, map processing, database, text processing, and > cloud aspects, so i guess it can be called multimedia. In any case, > devel is overcrowded. Any objections to that? > > Changes: > > * Sort variables. > * Start SHARED_LIBS at 0.0. > * Remove obvious third-party files aes.c and aes.h > that have no author information and no license. > Also added two patches to make that work. > * make port-lib-depends-check > WANTLIB += pthread > > After that, licensing information looks correct and the configure > and build logs look sane. > > Of course, if somebody wants to fix the Heinrichs Weikamp OSTC 3 > driver by linking against libcrypto for AES128 (see EVP_EncryptInit(3) > for frills), or alternatively embed a copy of the relevant parts > of /usr/src/sys/crypto/aes.c, or alternatively track down the author > of aes.{c,h} and get the license fixed, be my guest, but i'm not > planning to do that work, and i think it can be done in a later > REVISION.
Oop, this is probably a good time for me to put out the libdivecomputer for 0.6.0 that I've been using. I use it quite a lot (on a HW OSTC, a Suunto, and an Oceanic) using my own frontend. I haven't given my port the same attention as yours, Ingo! I'll look into getting your version (for 0.5.0) and mine in sync. (No objections about the category.)
libdivecomputer.tgz
Description: Binary data
