Labwindows CVI Linker Errors

[rmayTX301]

I tried unsuccessfuly to rename files in a CVI project manually and get linker errors during build related to XML function calls. So I copied the .c, .h and .uir files to a new folder and created a new project, but get the same errors related to XML functions calls (from link process ... the source file compiles OK).  Attached is a screen capture, and it appears I need to include some library but I cannot find how/where this is done. In the original project (with another name in another directory) it builds OK but I cannot find anything there related to these XML functions. All I'm trying to do is rename the various project files (I can rename the executable OK, but not the other project files).  But there appears to be no way to do this (amazingly) within the CVI environment, and creating a new project in a new folder does get the project file renamed, but now I can't get past these XML-related link errors.  Anyone know how to solve this problem?

[Wolfgang · Accepted solution]

Hi,

did you include cvixml.fp / cvixml.h? It is found in the toolslib folder.

[rmayTX301]

---

@Wolfgang wrote:

Hi,

did you include cvixml.fp / cvixml.h? It is found in the toolslib folder.

---

Thanks ... I'll try to find these and add them.  I've edited CVI programs for many years but only the C source code as someone else set up the projects and made the "skeleton" project and base code which has all the project settings, etc. So I'm not too familiar with fixing issues like this at a project level as I've not had to set up new projects before, and spent a lot of time trying to fix this particular error before finding this forum. But this sounds like the right solution. 

[rmayTX301]

Adding these files did eliminate those particular errors but many more cropped up that I have not been able to sort out.  I can change the name of the .EXE file easily, but for the other project files (eg. the .prg, cws, .cds and .cdb files) it appears that it is not possible to change their names from within the development environment.  So we decided to just keep the old name for these files and give up on trying to change their names.  I am surprised that it is so difficult to do something like this, but the effort to get it done is more than I have time to chase down at the moment.  I do appreciate the help though.