Copyrighrt (c) 2014-2020 UPVI, LLC
Welcome, Guest
Username: Password: Remember me
LVHDF5 Toolkit Forum
  • Page:
  • 1

TOPIC:

Standalone EXE doesn't work 6 years 4 months ago #20

  • jdsommer
  • jdsommer's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 23
  • Thank you received: 1
Hi Steffan,

The 1.8.13 version of hdf5.dll that is built and distributed by the HDF Group, and which I redistribute, imports GetTickCount64 from kernel32.dll. This function is not present in kernel32.dll on Windows XP systems. Some searching on the internet suggests that this may be a problem with the build settings used to build hdf5.dll, and you could try to rebuild it yourself and see if you can bypass this problem that way. (Alternatively, hdf5.dll may require the function, and therefore not be compatible with Windows XP. If that is the case, I haven't found any mention of an XP incompatibility on the HDF site or forum, so they don't know about it.) If you do build your own hdf5.dll, please do use the version 1.8.13 version of the source, as the HDF Group often changes the library ABI and I can't guarantee that Live HDF5 (1.0 or 1.1) will work with any other version. I know for a fact that it does not work with version 1.8.14, as they changed the names of several exported symbols.

Best regards,
Jason

Please Log in or Create an account to join the conversation.

Standalone EXE doesn't work 6 years 4 months ago #19

  • Blacky4191
  • Blacky4191's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 2
  • Karma: -1
  • Thank you received: 0
Hey Jason,

thank you so much for your answer. Maybe I didn't look close enough but I didn't a help-file with this information in it. Now the executable runs without any problems on my system :) But now another error occured - I forgot to tell you that my colleagues who should use the EXE later on use Windows XP on their system. For that reason I get the error "The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll". I found two solutions for that problem using Google, but I wasn't able to solve it with respect to my program. Maybe you already know more about how to handle this? :)

The reason I develop this viewer is that we get a lot of temperature data out of our automatic test systems in the department I work and HDF5View is not able to display the data in a way my colleagues can/want to handle it. Furthermore some of them want a function to save the data to MS Excel in order to show it to other colleagues who don't have HDF5 on their system. The development itself goes very well - the biggest problem is to build a working executable ;)

I'll check if I can show it to you when it's done :) Thanks again for your help!!!

Steffen

Please Log in or Create an account to join the conversation.

Standalone EXE doesn't work 6 years 5 months ago #18

  • jdsommer
  • jdsommer's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 23
  • Thank you received: 1
Hello Steffan,

Did you read the "Dependencies and Building Executables" section of the help file and follow the directions there?

Building LabVIEW Executables

To ensure that LabVIEW has access to all necessary files, please close all Live-HDF5-based VIs prior to building an executable. If VIs containing Live HDF5 xnodes remain open, LabVIEW may not be able to complete the executable build.

LabVIEW does not detect the shared-library dependencies of the HDF5 library when building a LabVIEW executable. To ensure that all of the necessary dependencies are added to your executable, please add the following files (all found in the <LabVIEW>\vi.lib\UPVI\LVHDF5 directory) to your project: 

  • hdf5.dll
  • hdf5_hl.dll
  • msvcp110.dll
  • msvcr110.dll
  • szip.dll
  • zlib.dll

Then, under the "Source Files" item of the Build Specifications, ensure that all of the DLLs are added to the "Always Include" list.

Alternatively, you may require users of your executable to have a valid installation of the HDF5 library (version 1.8.13) installed on there system with the library location added to the PATH environment variable.

Please note that the standard LVHDF5 license does not allow distribution of such executables outside of the developer's organization.


If you still can't get it to work, please let me know.

I'd be interested to see your HDF Viewer when you get it stable. Also, out of curiosity, what is your reason for your viewer? Is there something lacking from HDFView that prompted you to develop it?

Jason

Please Log in or Create an account to join the conversation.

Last edit: by jdsommer.

Standalone EXE doesn't work 6 years 5 months ago #17

  • Blacky4191
  • Blacky4191's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 2
  • Karma: -1
  • Thank you received: 0
Hello,

I tried to build a standalone exe out of my LabVIEW project. I am developing my own HDF5 Viewer using your very nice HDF5-library (thanks for it :) ). But always when I try to start the standalone exe on my system, I get several error messages (it's in german so I hope i translate it correctly) - the first one says that the "entry point of the procedure "H5P_CLS_FILE_ACCESS_ID_g" could not be found in "hdf5.dll"". Then he says that he's not able to find h5helper.dll and that an error occured in "H5ErrorHandler.vi". These messages appear about 10-15 times with the same error concerning the procedure entry point and other VIs like LVH5AwriteString.vi.

I use LabVIEW 2014 32-Bit on a Windows 7 64-Bit system. I even tried to put the missing DLLs in the LabVIEW resource folder and also in the folder where my exe is located, but it didn't help. I hope you can help me to solve my problem.

Thank you in advance and greetings from Germany,

Steffen

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.154 seconds