Bizarre problem with PDA project: BuildReport.txt

[gpatnude@idynatech.com]

LV 8.5
PDA Module for Window 5.0
CF-6004 DAQ
DaqMXBase configured properly

I started using an inline C node then subsequently changed my mind -- so I deleted the inline C node in my PDA Project. Now the project won't compile -- I get some strange errors --

Apparently -- when I deleted the inline C node -- it broke a chain of dependencies in LV that I cant figure out how to resolve.

Ultimately: I investigated the BuildReport.txt file. Inside -- it claims that there are 3 unresolved externals.... How do I find out what these are ?

Any ideas, thoughts or a solution would be greatly appreciated....



Greg

[TMC-NI]

Hi Greg,

You might be able to resolve this issue if you add #pragma comment(lib, "nidaqmxbase.lib") to the top of your source file and also making sure that in your build specifications, you include nidaqmxbase.lib as an additional file under Source Files.  Those error codes are telling us that your program cannot find the library, and I think that in this case, the library is related to DAQmx base.  Try this and let me know of your results.

[codeWarrior]

Yolga --

Thank you for the tips -- This project is being done completely in LabView -- I don't know how I would go about adding the pragma directive you specified.

As far as adding a reference to "nidaqmxbase.lib" -- I did that and I am still having the same problem -- the project fails to build and I get a 43K BuildReport.txt file.

[TMC-NI]

Hello Greg,

Do you happen to have any formula or expression nodes in your LabVIEW PDA code?  If so, do they contain ** (literally two star characters next to each other)?  There have been couple of customers who have had the exactly the same type of error with LabVIEW PDA, and by removing the ** coding, they were able to resolve the issue.

There are some known issues with formula and expression nodes and the PDA compiler.  If you do have the above **, can you please change it to (-1,x) instead of (-1**x) for example?

Otherwise, can you post the new buildreport.txt file so that I can see if anything else has changed after you followed the earlier suggestion?

Thanks, I'm looking forward to your reply.