Windows DLL Path

[EricksonTim]

When a LabVIEW Client is built into an exe, the path to the DLL resolves to "\Libraries\Win32"

However, using a typical build specification, the DLL is not copied to this folder because of the way the path is dynamically determined in "Get Server DLL Path.vi"

What is the recommended way to include the DLL in the build process?

AB#2636750

[bbanacki]

I have encountered this issue as well, if a build is created and deployed on a machine without LabVIEW and the GRPC package installed the "\Libraries\Win32\labview_grpc_server .dll" file will not exist. Temporarily I've modified the "Get Server DLL Path.vi" and placed the file in the data folder. It may not be the best approach but it worked until it's officially supported.

[dreamflow]

@EricksonTim :

i've automatised it like this :

.lvproject file -> project explorer -> build specifications
-> pre/post build actions
-> [X] execute vi after build
within this sepcial execute-after-build.vi , is available
the build_dirPath (= where the compiled exe lands) .

the compiled exe expects relative to itself in the folder
"Libraries\Win64\" : the "labview_grpc_server.dll"
together with the "feature_config.ini" .

therefore the folder "Win64\" (or "Win32\") sitting in
"<vilib_dirPath>\gRPC\LabVIEW gRPC Library\Libraries\"
needs to be copied into the folder
"<build_dirPath>\Libraries\" .

the VI Library Function delivers the vilib_dirPath .

[jasonmreding]

For reference, here is what we do in the measurement-plugin-labview repo when building an exe for the server code. It also uses a post build step in the build spec.

The VI is located here. At some point, it might be a nice feature for the generator to have an option to generate a buildspec in the target project as well.