The fun never ends...
I've got one VC++ solution A that I compiled to a lib.
I've got an existing C program B which I'm compiling as C++ solution. I added the lib A into project B and set the lib as a dependency. When I build using functions from A I get the errors below.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
These 3 functions:
eap_peer_sm_init
eap_peer_r
wpabu
shou
extern "C"
{
struct eap_sm * eap_peer_sm_init(void *,struct eapol_callbacks *,void *,struct eap_config *);
int eap_peer_register_methods(
void wpabuf_free();
}
probably in eap_example_peer.h file (whatever you use in include in your program).
You can read about it here:
"Linking C and C++ code" http://en.wikipedia.org/wi
Or in MSDN: http://msdn.microsoft.com/
Shortl
Take for example the last error in your original post - the compiler looks for function void wpabuf_free() but it uses so strange name for it - ?wpabuf_free@@YAXPAUwpabuf
C++ compiler decorated the function name in this style.
C Compiler in this case does just _wpabuf_free. Just with symbol '_' in the beginning. When for C++ compiler you say extern "C" before a function prototype:
extern "C" void Nothing();
it will compile this void Nothing() in "C style" - __cdecl calling convention is used. Today it's already a deep theory. Maybe even a useless theory - who's interested now to know what is this. :(
>> I've got an existing C program B which I'm compiling as C++ solution.
As was mentioned in your other question, did you forget to rename the source file to .cpp before compiling it ? Otherwise you might THINK that it was compiled with a C++ compiler, but actually a C compiler would have been used (the compiler looks at the extension to decide what type of file it is).
Business Accounts
Answer for Membership
by: ShayanOHPosted on 2009-09-13 at 12:40:04ID: 25321444
try adding extern "C" around the include directive, like the code snippet below.
Looks to me like incompatible naming conventions.
(The names in error are using C++ conventions, but you seem to have compiled the lib using C conventions)
Select allOpen in new window