01-22-2014 01:14 PM
Well that was my last resort. That's a lot of work, this is a rather large project, and I just can't believe one would have to go through all that just because they updated the CVI version.
01-22-2014 04:55 PM
OK finally figure it out. Can't believe the CVI guys, that wrote the compiler, don't know this but the issue was with defines that are entered under the Configuration Options. Under 'Options\Build Options\Compiler Defines'. In 2009 one entered multiple defines seperated with a comma then a space, but in CVI 2010 the seperation was ONLY with a space. So in my 2009 project I had defines as "/DWIN32_LEAND_AND_MEAN, /DMY_DEFINE". Thusly the 2010 compiler was complaining that the ',' was the first character in each .c file. Taking out the ',' as in "/DWIN32_LEAND_AND_MEAN /DMY_DEFINE" fixed everthing.
Glad I didn't 'make a new project and add the files in one by one'. That would have been another day or two, fiddeling with libs, instrument files, project settings and etc.
01-23-2014 12:54 AM - edited 01-23-2014 12:55 AM
Hello atomic928,
Nice job figguring out the problem! I will ensure that this issue is documented.
As a note, I think you can select multiple files to add to a project, so that job wouldn't have been that hard.
Best regards and thank you for your input,
= Nelu F. || National Instruments.
01-27-2014 10:11 AM
Hello atomic928,
I have opened a bug report (id #447402) to cover this issue.
Best regards,
= Nelu F. || National Instruments.