On 04/02/2017 01:38, Alessandro Volpi wrote:
-------- Forwarded Message --------
Subject: Re: Fwd: importing smarttrak slg logs
Date: Fri, 3 Feb 2017 23:15:55 +0000
From: Alessandro Volpi <[email protected]>
<mailto:[email protected]>
To: Salvador Cuñat <[email protected]>
<mailto:[email protected]>
CC:
Dear Salvador,
I have imported my (large) dive_log.slg file, relying on
smtk2ssrf_test.AppImage. The program did find data formatting errors
in several dives in the slg file, but, surprisingly, such errors did
not result in any visible flaw in the imported data for the concerned
dives. The log of the import operation is attached, in case you are
curious to have a look at it.
I have opened the imported xml file with the subsurface version
installed from the Fedora 24 repo.
I was very impressed by the quality of the application you are
developing and maintaining ... I cannot find good words for qualifying
it, other than EXCELLENT !
Al details of the dive, including gas switches during sidemount dives,
were perfectly imported. Before trying subsurface I was planning to
edit the notes of every single dive in order to insert the data
concerning fish species spotted during the dive. I was very glad to
discover that also this information has been automatically added to
the dive's notes. Therefore the log is perfectly good as it is and no
manual editing intervention is needed!
Also the management of dive sites and their coordinates is better than
my more optimistic forecasts.
I am very grateful to you for your prompt answer to my messages
concerning my difficulties in building subsurface and smtk2ssrf on
Fedora 24.
I do not need to do that once again, since I have a working instance
of both programs. MoreoverI think I will never have in the future any
reason for importing the dive_log. slg file: I am not going to keep on
using SmartTrack on my Windows XP virtual machine. Unfortunately I
cannot ditch it right now, since I occasionally need to modify my dive
computer settings and it is easier to do that by means of SmartTrak,
instead of fiddling with the Galileo button driven menu.
Since am am a curious man, I have anyway tried to build the objects
and the executables, after having created a suitable symbolic link :
ln -s /usr/lib64 /usr/lib/x86_64-linux-gnu .
After having done so, I was guessing the the required library should
have been made available to build.sh .The available libmdb shared
objects were thus:
ls -l /usr/lib/x86_64-linux-gnu/libmdb*
lrwxrwxrwx. 1 root root 15 2016-02-04_09:38:43
/usr/lib/x86_64-linux-gnu/libmdb.so.2 -> libmdb.so.2.0.1
-rwxr-xr-x. 1 root root 87280 2016-02-04_09:38:49
/usr/lib/x86_64-linux-gnu/libmdb.so.2.0.1
lrwxrwxrwx. 1 root root 18 2016-02-04_09:38:44
/usr/lib/x86_64-linux-gnu/libmdbsql.so.2 -> libmdbsql.so.2.0.0
-rwxr-xr-x. 1 root root 40096 2016-02-04_09:38:49
/usr/lib/x86_64-linux-gnu/libmdbsql.so.2.0.0
I created a ~/src/ folder in my home folder, since you say that it is
a bad idea to build subsurface as root.
I then went through the build operation, but the procedure failed once
again, the script being unable to find a suitable libmdb shared object.
See the attached file build.log .
In any case, as far as I am concerned, everything is now OK with
subsurface. The only problem is now that I am not able to get a
working the irda interface in Fedora 23.
The module mcs7780.ko.xz is present on my system and is loaded with
modprobe. Nevertheless the irda interface is not working on my system.
I guess that one possible explanation for that is the absence of any
irda configuration file in the system.
It is obvious that my troubles with the irda interface have nothing to
do with your excellent software and that I am not therefore asking for
your help about that.
In case I do not succeed in setting up the irda interface in my
desktop PC with Fedora 24 I am going to try to do that in my Dell XPS
13 Developer Edition with Ubuntu trusty.
Thank you once again for your help and your development activity.
Best regards.
Alessandro
Dear Allessandro,
The IrDA upload has been working flawlessly on by Ubuntu box since I
started using Subsurface. I cannot see that this can be a fundamental
stumbling block, even on Fedora. But I have never done this on Fedora
myself. The basic procedure I followed is the one I documented in the
Subsurface user manual: download (from Linux-IrDA project) and install
the driver, then execute an irattach instruction AS ROOT (i.e. using
sudo) before starting Subsurface. Only snag with the Galileo is it
downloads the full memory of the dive computer every time, even if only
the last dive is needed. Fortunately Subsurface knows which dives have
been downloaded previously and only shows the new dives for download.
Salvador is working hard on the AppImage for smtk2ssrf that can execute
on a wider range of Linux flavours.
Kind regards,
willem
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
