Recently I play with C to refresh my (rather shallow) C programming skills. To make it fun, I combine this with building C DLLs to be called from LabVIEW.
Ok, lets get to the point. During C code development (I use Code::Blocks as IDE, and MINGW-gcc as compiler), I often need to make small modifications on the code, and recompile it. Since my LabVIEW project/VI uses the DLL in the Call Library Function node, I need to close the VI(s), otherwise the C IDE complains it cannot re-build the DLL.
Of course there is a workaround, explain in the following quite fresh document:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019O6eSAE
I use it, and it works. However, I find this workaround counter-intuitive and "ugly" as a solution. Idea: could we have some kind of more explicit control over DLL unloading? I imagine different options, one possibility to have a special CLN node option, like "unload" DLL...
What do you think?
Any idea that has not received any kudos within a year after posting will be automatically declined.