This issue was caused because the call to the Version() function specified by the -v flag occurs before the DLL is loaded. This change loads the DLL up front, so that version information is populated before the call to Version().
I also changed the name of drvrVerDrvr to drvrVerPatch, to be consistent with semantic versioning major/minor/patch version numbers. I also added the drvrVerPatch to be printed in the -v message (it was already printed to the output file)
Example output:
*******************************************************
Institute for Telecommunications Sciences - Boulder, CO
ITM Driver Version: 1.4.0
ITM DLL Version: 1.4
Time: Wed May 8 17:24:33 2024
*******************************************************
Resolves #17
This issue was caused because the call to the
Version()function specified by the-vflag occurs before the DLL is loaded. This change loads the DLL up front, so that version information is populated before the call toVersion().I also changed the name of
drvrVerDrvrtodrvrVerPatch, to be consistent with semantic versioning major/minor/patch version numbers. I also added thedrvrVerPatchto be printed in the-vmessage (it was already printed to the output file)Example output: