02-26-2007 05:47 PM
02-27-2007 10:57 AM
Hi Gohar,
When did the program stop working? Did it stop working immediately after you changed your system configuration? When you say that your system configuration might have changed, do you mean you have changed versions of CVI? If so, what version of CVI are you currently using to open the project and what version of CVI was the project developed in?
Also, what line in the stdlibex.h file does the error point to?
The answers to these questions should help point us in the right direction.
Regards,
Matt
NI
02-27-2007 03:18 PM
02-27-2007 04:51 PM
Hi Gohar,
If you are unable to track down the version of CVI or if you reinstall and it still does not work I would try three steps:
1) Create a new project and include stdlibex.h. If this works then I would move to skip step 2.
2) Check your Environment settings under Options >> Environment. Then click the Include Paths button. If you have any extra paths listed, verify that stdlibex.h does not exist in multiple folders. If it does, this could be causing a problem.
3) Create a new project and copy all of your code into the new project. It is possible that your project somehow was corrupted in the transition/upgrade.
Let me know how this goes for you.
Regards,
Matt M.
NI
02-27-2007 07:46 PM
02-28-2007 08:33 AM
02-28-2007 06:17 PM
02-28-2007 06:31 PM
Hello Matt,
I still haven't re-instaled CVI (there were some unforseen complications with that), but I did try your suggestions. Step (1) worked perfectly fine. Labwindows didn't seem to have a problem with stdlibex.h in my new project. And I checked the include paths (step 2) - no extra paths are listed anywhere in the options/environment panel.
However, when I got to step 3, things stopped working again. I did create a new project and copied all my code over, but I still get the same errors. So a corrupted project is definitely not the problem.
I wen one step further and commented out the line in stdlibex.h that was giving me a problem. The error messages went away, but this is not a good solution. Plus, now I have some new errors (a long list of undefined symbols), so I am even more confused as to what the problem is. I suspect some of the device driver files (.fp files) are not as they should be. But I don't know enough about LabWindows or the drivers themselves to figure out what exactly is wrong. I guess more investigation is neede.
Anyway, thank you all for your help.
Any new insignht in this matter would be greatly appreciated.
Gohar
02-28-2007 06:36 PM
03-01-2007 11:38 AM