LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview create dll in Windows11 22H2 Error

building shared library...

Pop-up window,click OK,build Errors

Pic 2022-10-07 002357.png

0 Kudos
Message 1 of 12
(1,974 Views)

LabWindows/CVI messages are rare in LabVIEW....

 

Pretty sure it's not related to LabVIEW...

0 Kudos
Message 2 of 12
(1,931 Views)

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?

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 3 of 12
(1,913 Views)

t1 2022-10-08 163919.png

 

Thanks!

0 Kudos
Message 4 of 12
(1,892 Views)

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.

Rolf Kalbermatter
My Blog
Message 5 of 12
(1,849 Views)

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...

0 Kudos
Message 6 of 12
(1,825 Views)

The default temp directory is set test, in the same case, only the folder path different

0 Kudos
Message 7 of 12
(1,788 Views)

@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...

0 Kudos
Message 8 of 12
(1,767 Views)

Use "%USERPROFILE%\AppData\Local\Temp" to set the default directory, 

Same question

 

aaa.png

0 Kudos
Message 9 of 12
(1,749 Views)

@liulong wrote:

Use "%USERPROFILE%\AppData\Local\Temp" to set the default directory, 

Same question

 

aaa.png


Well at least now we know for sure...

0 Kudos
Message 10 of 12
(1,733 Views)