07-01-2010 07:22 AM
Hello.
I am trying to solve my linking error problem for some days, but I cannot find the right answer. I have searched the forum already and read some threads with "undefined symbol link error" but they are not fitting to my problem.
What I try to do: I want to communicate with my Softing profibus card. I have includes all the header files in my source code and also I included the two .lib files to the project. But the mentioned error won't leave.
It is curiously enough when I choose "Go To Definition" in the context menu, CVI finds the right declaration in the right header file.
Who can help? What's wrong?
Best regards
der_Ben
Solved! Go to Solution.
07-05-2010 04:45 AM
Hi Ben,
could you please provide a little more information about your system and software?
Which version of CVI are you using?
Could you take a couple of screenshots of the problem?
Regards,
07-05-2010 05:09 AM
What are the lib files that you added? If you are using daqmx did you add daqmxbase.lib?
07-12-2010 08:39 AM
Hello,
I am using WindowsXP an CVI2009 (but with CVI9.0 i am getting the same issue).
The *.lib files I included in the are "papi.lib" and "pbtools.lib" from softing profibus device driver.
Which informations I should give you more?
Regards,
Ben Schmitz
07-16-2010 04:47 AM
Hi Ben,
thanks for the extra info. I haven't found any specific references to problems with profibus and CVI. This may mean that the problem is local to your PC. Does this work on any other machine? If you haven't tried it, that would be a good test to check whether it's a general or a local problem.
Regards,
07-19-2010 12:30 AM - edited 07-19-2010 12:33 AM
Does the the documentation show that either papi.lib or pbtools.lib provide a function or global variable called profi_get_cntrl_info ? If neither papi.lib nor pbtools.lib provide that , you will have find add another library that includes profi_get_cntrl_info.
07-19-2010 08:08 AM
Hey,
one of the LIB's provides this function, yes.
But now i got it. I've checked the "Build Options" and change the "Default calling convention" from "__cdecl" (must be default) to "__stdcall" and now everything works fine with that function.
I like to say thank you for your advices 😃
Regards
Ben
07-19-2010 08:12 AM
Hi Ben,
thanks for posting the solution. I also added to our databases for future reference.
Regards,
10-23-2012 03:56 AM
change the "Default calling convention" from "__cdecl" (must be default) to "__stdcall" ,I have more link error