Building shared library for simple add function labview VI

[AnandR]

Hi ,

I am trying to build a shared library for simple add function in labview .But getting error as attached snapshot.

Regards,

Anand

[wiebe@CARYA]

Don't forget to press "Details". It might provide, well, details.

[AnandR]

Hi,

Attached is the error details. The VI is simple one. It just add 2 numbers . Not sure why i am getting this error. Looks like calling convention error. Any input for this.

I tried for simple number increment also. There are also same error.

Regards,

Anand

[crossrulz]

You are going to have to share some code, including the project in order for us to be able to help debug this at all.  I see notes about function and parameter names, but nothing exact to look at.

[AnandR]

Hi,

Attached is the labview project.

Regards,

Anand

[crossrulz]

That DLL just built just fine for me.  Perhaps you are running into a permission issue?

[AnandR]

Hi,

Still the issue there. I am not sure where to change for permission issue.

The error line says. "An error occurred compiling the DLL because a function or parameter name is illegal. Please verify that the function and/or parameter names are legal C identifiers and do not conflict with LabVIEW headers."

Regards,

Anand

[wiebe@CARYA]

Especially when building exe or dll's, the error descriptions are not that descriptive.

Are you using the dll anywhere? That will lock it, and builds will fail. Make sure it's not in loaded. A VI, even when it's not running, using it will keep the file locked. Or try to (temporarily) change the destination name of the dll. As it's complaining about the function name, you might (temporarily) change that too, just to see what happens.

[AnandR]

Hi,

I tried with new Labview project. closed all the VIs ,changed the destination and changed the function ,parameter name too. Still the same issue.

If my project works in your system, it might be some file missing in my system.

Regards,

Anand

[wiebe@CARYA]

That would mean a repair or reinstallation of LabVIEW.

Unless you did something out of the box, I'd think something else is happening, but a repair might be worth a shot.