V_1.18.0

[kiozen]

[QMS-558] Support for MTP devices
[QMS-648] Porting to Qt6
[QMS-656] TMS/WMTS: Fix loosing layer selection when reloading maps
[QMS-664] Fix BRouter java setup on Debian
[QMS-668] MacOS build adapted to new gdal version and new brew packages
[QMS-675] The label colors defined in the TYP are not used
[QMS-680] Fix: Sending multiple selected projects to device
[QMS-683] Fix alglib error on interpolation
[QMS-692] Trackpoints erroneously flaged invalid for short tracks (<50m)
[QMS-699] Fix writing to default config when using command line parameter -c
[QMS-706] Apply PNG file’s offset to user-defined waypoint icon from "External Icons" folder
[QMS-709] Adjust square zoom levels to fit EPSG:3857 tiles and other minor fix in Proj Wizard
[QMS-715] Remove duplicate tile map server requests for the same tile, allow HTTP(S) redirection
[QMS-732] Migrate macOS build from Qt5 to Qt6
[QMS-730] TMS/WMTS fixed accidentally removed namespace processing
[QMS-738] Use Gamin's FIT SDK to support FIT files properly
[QMS-740] Fix dbus compile issues for Windows
[QMS-743] Fix crash when reseting a range in track profile graph
[QMS-745] Remove old FIT implementation
[QMS-747] Remove support for MapQuest
[QMS-750] Fix QMS build error - Windows 10/MSVC
[QMS-753] Fix segfault for FIT sessions without track data
[QMS-756] Avoid: [warning] QIODevice::read (QProcess): device not open
[QMS-757] Avoid: [warning] Empty filename passed to function
[QMS-758] Avoid: [warning] QSqlError("19", "Unable to fetch row", "NOT NULL constraint failed: workspace.name")
[QMS-759] Avoid: [warning] QWidget::setMinimumSize: (/QTextBrowser) Negative sizes (300,-140) are not possible
[QMS-766] Avoid: [warning] QMainWindow::addDockWidget: invalid 'area' argument
[QMS-769] Fix: "Send to device" is not enabled/disabled properly
[QMS-771] Adapt Fit2 Implementation
[QMS-775] BRouter segments download: wrong accumulated size of segments, wrong outdated segments count
[QMS-777] BRouter segments download "Cancel" dialog not translated
[QMS-779] Avoid NaN when totalAscent or totalDescent = 0
[QMS-782] Solved two issues for track point viewer
[QMS-784] Solved two issues for GNOME/Wayland, Invalid Points Dialog vs Progress Dialog
[QMS-788] Fix: BRouter (offline) not shown in combobox
[QMS-791] Error determining BRouter-Web (online) version
[QMS-793] Auto-routing with BRouter & minor fixes
[QMS-794] Fix: Links to local files in Waypoint on-screen dialog not opening
[QMS-797] Enhance USB MTP to support generic devices
[QMS-799] Fix QMS icon shown in Dash for GNOME/Wayland

---

This discussion was created from the release V_1.18.0.

[blackfoxx79]

Hi. Will there be a chance to get a Windows-Setup of 1.18.0?
Like with 1.17.1 from here: https://github.com/wthaem/qmapshack/releases
@wthaem

[wthaem]

@blackfoxx79: Yes - I'm working on an update of the installer script. This needs still some time. I hope, it can be ready by the end of this month.

[blackfoxx79]

OK. So thanks in advance for your work! I appreciate that.

[dbl2126]

Merci beaucoup...

[blackfoxx79]

Today I updated QMS on our companies Terminal-Server (OS: WINDOWS SERVER 2022) from V1.17.1 to V1.18.0.
After the first start of this new version our G-DATA Security Software displayed an Malware Alarm:

I've searched the www about this "win64.trojan.agent.nrtaex" but there were only 2 results showing up and they didn't tell something about the (potential) danger of it.
The G-DATA Security Software moved this file to the quarantine and QMS still works (so far).
It would be nice, if somebody around here would be able to tell me something about this issue.
I'm not allowed to install software which triggers security-alarms on our servers.
Thank you.

@wthaem @kiozen

[kiozen]

qmt_map_2jnx is a small command line tool used by QMapTools. If it's missing you can't convert raster maps into the jnx format for Garmin devices.

But I can't tell why the binary is triggering the virus scanner

[JFritzle]

#802 (comment)

About QMapShack V1.18.0 for Microsoft Windows:
Attention: this version has currently an issue with online maps requiring OpenSSL support!

Qt6 plugin tls is missing! Copying folder <Qt_installation_tree>/plugins/tls as folder <QMapShack_installation_folder>/tls solves issue.

[wthaem]

@JFritzle: Thanks for the hint. Comparing my dev with my master version I found this difference, too, and gave a corresponding advice at naviboard. I have still to investigate where this difference did come from.

[kiozen]

If you create a new binary package mark it by appending the version number with "_1"

[JFritzle]

#802 (comment)

About G-DATA Security Software Malware Alarm:

I uploaded and checked file qmt_map2jnx.exe from QMapShack V1.18.0 for Microsoft Windows at VirusTotal:

-> Detected by GData as malware.

Then I uploaded and checked own generated file qmt_map2jnx.exe at VirusTotal:

-> Not detected by GData as malware.

Strange, as source code is identical and compiler probably too:

• Microsoft (R) C/C++-Optimierungscompiler Version 19.44.35213 für x64
• Visual Sudio 2022 with cmake generated project

What is different:

• I am using GDAL 3.10.3 and Proj4 Rel. 9.6.2 June4th, 2025
• Released installer uses GDAL 3.11.3 and same Proj4 Rel. 9.6.2 June4th, 2025

As VirusTotal only checks executable file without it's dependent dlls, executables differ in GDAL and Proj4 libs bound into executable and loading corresponding dlls at runtime.

!!! Update !!!
Now I have re-build qmt_map2jnx.exe using GDAL 3.11.3 and Proj4 Rel. 9.6.2 June4th, 2025 too.
VirusTotal result: Not detected by GData as malware.

Maybe of interest:
I did not build GDAL nor PROJ myself, but used ready-to-use stable release from GISInternals, containing compiled libraries, headers and binaries for MSVC 2022.

[wthaem]

@JFritzle: (I could not yet find in the GitHub discussson page #802 the content of the mail I received concerning DLLs in the GDAL plugiin folder)

About gdalplugins subfolder:

We should not include 2 DLL files ogr_OCI.dll and gdal_GEOR.dll into QMS installation subfolder gdalplugins or all plugins lack of DLL OCI.dll which is not part of QMS installation:

Today, I published a new Windows installer. The 2 mentioned DLL files are not part of this installer.

Certainly, you will find more DLLs distributed with the installer not really used in QMS. But I'm not able to decide which ones to drop (e.g. the list of files found by the used windeployqt tool to collect necessary Qt files is most likely too long). Thus my strategy is: better one more instead of one missing.

Help here very welcome!

[JFritzle]

@wthaem: Sorry, I have withdrawn my comment when I noticed those 2 mentioned DLL files were not at all part of installer.

I was too checking for DLL files not needed. I am using Cygwin's command line tool cygcheck to find out, which DLLs are essential for the EXE and DLL loader without which the program does not start at all.

My method:

• first separating all EXEs in a folder and checking for missing DLLs:
  Cygwin bash: for f in *.exe; do echo $f; cygcheck ./$f | grep "could not find"; done
• then adding missing DLLs to that folder
• then checking DLLs for further missing DLLs:
  Cygwin bash: for f in *.dll; do echo $f; cygcheck ./$f | grep "could not find"; done
• then adding these missing DLLs to that folder
• and so on until no more DLL was missing, not forgetting to check Qt and GDAL DLLs from plugin folders

At last, few DLLs were remaining, which I found not to be essential for program successfully starting.

Besides those, some are known to be still needed. This kind of DLLs is loaded only at runtime and on demand. If not available, program's functionality is restricted, e.g. no https without tls plugin and without OpenSSL DLLs. If no documentation explicitly states such a DLL as required, it is highly forensic to identify, e.g. to search and probably find it's name embedded in raw file data.

Therefore I totally agree with your strategy.

But I do we really need

• Qt plugin generic/qtuiotouchplugin.dll? Do we support TUIO devices?
  "Multi-touch devices (like interactive tables or touchscreens) equipped with TUIO support will send data in the TUIO format over a network."
• Qt plugin iconengines/qsvgicon.dll? SVGs found in QMS source tree have been rendered to PNGs by inkscape before used by QMS at runtime.
• Qt plugins qmltooling/*.dll? See Debugging QML Applications:
  "The qmltooling plugins that are required for debugging and profiling QML applications on devices are automatically installed during Qt installation."
• plugin networkinformation/qnetworklistmanager.dll? QNetworkInformation Class needs this plugin on platform Windows but class is not used by QMS.
• Qt D3D compiler with DLLs d3dcompiler_47.dll, dxcompiler.dll, dxil.dll? We do not use QShader Class at all, especially we do not create DXBC bytecode suitable for Direct3D 11/12
• all Qt plugins from sqldrivers? Digging in QMS source code, only drivers QSQLITE and QMYSQL are used.
• all Qt plugins from imageformats? I suggest to omit qpdf.dll, qsvg.dll, qtga.dll, qwebp.dll, which would make Qt6Pdf.dll and Qt6Svg.dll unreferenced and obsolete too.
• Qt plugins position/*.dll? Qt Positioning is supported "on Windows (with GPS receivers exposed as a serial port providing NMEA sentences or using Windows.Devices.Geolocation". Only useful when using QMS outdoors with a connected GPS receiver, or with sources including GPS, Wi-Fi, cell towers, and IP addresses for retrieving and tracking a device's location.

We also do not need .bat files for starting qmapshack or qmaptool:

• We do not need to set environment variables GDAL_DRIVER_PATH and GDAL_DATA, as GDAL is automatically looking for DLLs at folder $(BINDIR)/gdalplugins on Windows, which is a subfolder of QMS installation folder. See here
• We do not need to set environment variable PROJ_DATA, as PROJ9 is automatically looking for resources at subfolder share/proj of PROJ9 installation i.e. QMS installation. See here

[wthaem]

Thanks for your remarks and your work!

I must admit that I have very limited knowledge of C++ programming and the Qt package, too. I am personally interested in being able to work with the QMS dev version. To that end, I had to learn how to build the QMS package, and huirad, who had prepared and published the QMS Windows release for quite some time, was a great help to me. He could/did no longer publish the Windows release. However, people still demanded it. I decided to update and adjust his scripts and publish my QMS release, knowing that I didn't understand every detail of the build process.

One essential step of the build and deploy process is finding all necessary DLLs. Using Qt6 instead of Qt5 posed a real challenge in this respect. Using windeployqt.exe was a reliable way to accomplish this task.

All the Qt DLLs you discussed were found with the help of this Qt tool. Due to my lack of knowledge, I kept them all in the QMS package. Based on your results, I would propose using some kind of an exclusion list to drop unnecessary DLLs from deployment.

Personally, I use maps in the PDF and the webp formats. Therefore, I suppose the image processing files qpdf.dll, qsvg.dll, qtga.dll, and qwebp.dll should be kept in the package. However, I don't know if this statement is correct.

With regard to the batch files to start QMS/QMT (proposed by Mitxel): the environment variables set in these script were necessary in the previous release. After some code changes in QMS/QMT and in GDAL/proj that I didn't notice, these files are probably no longer necessary and can be omitted.