10-06-2022 11:29 AM
building shared library...
Pop-up window,click OK,build Errors
10-07-2022 07:51 AM
LabWindows/CVI messages are rare in LabVIEW....
Pretty sure it's not related to LabVIEW...
10-07-2022 09:02 AM
wiebe@CARYA wrote:
LabWindows/CVI messages are rare in LabVIEW....
Pretty sure it's not related to LabVIEW...
I think there was one build I had that required a LabWindows/CVI toolkit of some sort, but that's it.
To the OP:
What happens when you delete that file?
10-08-2022 03:41 AM
Thanks!
10-09-2022 11:19 AM - edited 10-09-2022 11:20 AM
wiebe@CARYA wrote:
LabWindows/CVI messages are rare in LabVIEW....
Pretty sure it's not related to LabVIEW...
The messages are rare indeed but the DLL build does require a C toolchain and the according build step invokes (or at least invoked in the past) a version of the CVI runtime engine with built in compiler.
While a LabVIEW DLL is for most of the part simply an archive of the compiled VIs, there needs to be a stub function compiled in C for every exported DLL function, that locates the correct LabVIEW runtime and then invokes the compiled VI resource through it, possibly massaging any memory buffers (arrays and strings) between the configured C parameter type and the native LabVIEW datatype and vice versa for indicators.
10-10-2022 03:04 AM
OK, so it does seem to come from LabVIEW.
The relocatiob of UserTemp to E:\ could be a problem.
Changing the temp directory should be possible, but things aren't always as they should be...
It is suspicious...
10-11-2022 01:56 AM
The default temp directory is set test, in the same case, only the folder path different
10-11-2022 03:34 AM
@liulong wrote:
The default temp directory is set test, in the same case, only the folder path different
I don't know what that means.
The path is different, and there's a related error. It's suspicious.
Somewhere some code might still be using the old temp folder. That would be a bug, but not unlikely.
It you'd (temporarily) revert the temp folder to its original path, you'd know for sure if this causes the problem.
If the non-default temp directory does cause the problem, you could make a link from the temp folder's parent to the new temp folder. That would put your temp folder on the new location, and application would still be able to use the old folder. There might be scenario's where this doesn't work, so I'd revert the folder first. Take it step by step...
10-11-2022 05:42 AM
Use "%USERPROFILE%\AppData\Local\Temp" to set the default directory,
Same question
10-11-2022 12:08 PM
@liulong wrote:
Use "%USERPROFILE%\AppData\Local\Temp" to set the default directory,
Same question
Well at least now we know for sure...