Hello DaniK,
1. Usually a .dll is what the Import Shared Library wraps up for use in LabVIEW.
2. The header files are necessary. They help expose and describe the functions in a .dll for use by LabVIEW. If we don't have a header file to define the functions inside of a .dll, we don't know what the functions inside of it expect for arguments, or what kind of data we can expect them to return.
3. The message "The shared library contains 338 function(s). The declarations of 41 function(s) are found and recognized in the header file and these function(s) can be wrapped. The remaining function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard" you're seeing here is just the Import Shared Library letting you know which functions were clearly described in the header file. Of the 338 functions it perceives in the .dll, only 41 are clearly defined.
If the vendor intended the end user to make use of only 41 functions, this is not a problem.
"The following header file was not found in the specified header file or one of the referenced header files:..."
Is a little more problematic - but it should be solveable by including the path of the location of the Vendor's header files in the "Include Paths" step of the Import Shared Library wizard.
Two additional resources that you may find helpful:
Tutorial: Creating Wrapper VIs for C/C++ DLL functions using the Import Shared Library Wizard
Calling C/C++ DLLs Containing Simple and Complex Datatypes from LabVIEW
Best regards,
Matthew H.
Applications Engineer
National Instruments
