mkossmann, I was having identical issues as you, interfacing with a custom board that used the FTDI driver.
To shed some more light on the link that ebalci listed, here is the conversation that I had with Darren Bield NI off-forum:
Darren
Thanks for the update. Glad to hear you have a solution.
There should not be any issues with opening a 2012 CWS or PRJ in 2013, so we will likely continue to investigate this. I will let you know if we figure anything out.
Rob
Darren, sorry for the long delay. I tried just now building in both my Debug and Release configurations. No go.
But with your recommendation, I created a new project, imported the sources and LIB file. But I created new PRJ and CWS files. That cured it!
Which paints more of the picture for you… I had taken my 2012 project folder and simply opened it in 2013. But that apparently isn’t totally possible with the PRJ/CWS files. No matter, I know how to proceed now…
Darren
Hi Rob,
I still cannot reproduce this even with your project file and environment settings. Are you able to use the lib in a new project? Is there a specific build configuration that causes the error, or do both debug and release cause the error? Do you have any other systems you might be able to test this on?
Rob
Hmm, strange. Thanks, Darren, here are the files.
Darren
Hi Rob,
I was able to build an app that called FT_Open without any problems. Could you send me your project file so that I can reproduce the settings. As well as an export of your environment options (Tools >> Import/Export Settings).
Rob
Correct, Darren. Sorry about that, here’s the header…
Darren
Hi Rob,
Do you have a header file for this lib as well? I wasn't able to figure out the parameters for any of the exported symbols in the lib. I presume the error occurs when building, and not when adding the import lib.
