Problem in Linking!

Printable View

June 8th, 2004, 09:30 AM
ilamparithi

Problem in Linking!

Hi all,

Iam using IcmpParseReplies() Api, but iam getting
error LNK2001: unresolved external symbol _IcmpParseReplies

But i had already included the IcmpAPI.h header file and icmp.lib, Iphlpapi.lib files linked in SETTINGS-> LINK.

Iam also using IcmpSendEcho2() Api in the same code.
Iam not getting unresolved error while using IcmpSendEcho2().

How to solve this problem?

With Regards,
A.Ilamparithi.
June 8th, 2004, 10:15 AM
Andreas Masur

This function is only available in Windows 2000 or higher...thus, it might be covered with an '#ifdef...#endif' guard...

Thus, you need to set the WINVER macro accordingly...

Code:

#define WINVER 0x0500
June 8th, 2004, 11:54 PM
ilamparithi

re:

Quote:

Originally posted by Andreas Masur
This function is only available in Windows 2000 or higher...thus, it might be covered with an '#ifdef...#endif' guard...

Thus, you need to set the WINVER macro accordingly...

Code:

#define WINVER 0x0500

Hi Andreas,

Iam working in a Windows 2000 Professional machine only.

Anyway i tried to set WINVER macro, still the error remains the same.

With Thanks,
A.Ilamparithi.
June 9th, 2004, 03:51 AM
Andreas Masur

Well...I did not check it, thus, it might be the other macro instead...

Code:

#define _WIN32_WINNT 0x0500
June 9th, 2004, 04:00 AM
ilamparithi

re:

Quote:

Originally posted by Andreas Masur
Well...I did not check it, thus, it might be the other macro instead...

Code:

#define _WIN32_WINNT 0x0500

Hi Andreas,

Still the same linking error occurs.

With Thanks,
A.Ilamparithi.
June 9th, 2004, 04:11 AM
Andreas Masur

Well...then I am running out of ideas at the moment...I do not have the header available, thus, cannot look for the function...sorry about that....
June 9th, 2004, 04:14 AM
ilamparithi

RE:

Quote:

Originally posted by Andreas Masur
Well...then I am running out of ideas at the moment...I do not have the header available, thus, cannot look for the function...sorry about that....

No probs!

Thanks Andreas!

Anyone know the solution?????? :(

A.Ilamparithi.
June 9th, 2004, 04:23 AM
usman999_1

Quote:

Originally posted by Andreas Masur
Well...I did not check it, thus, it might be the other macro instead...

Code:

#define _WIN32_WINNT 0x0500

Well thats a linker error, and #ifdef are resolved at compile time. So defining WIN_VER wont matter. May be u need to upgrade your SDK. Its a failrly recent API supported on Win2K and above.
Regards,
Usman.
June 9th, 2004, 04:23 AM
Andreas Masur

Ohhh....one more thing that comes to my mind...make sure that you have the latest files...in other words...does the function exists in your header file?
June 9th, 2004, 04:30 AM
ilamparithi

re:

Quote:

Originally posted by usman999_1
Well thats a linker error, and #ifdef are resolved at compile time. So defining WIN_VER wont matter. May be u need to upgrade your SDK. Its a failrly recent API supported on Win2K and above.
Regards,
Usman.

Hi Usman,

Iam using Microsoft Platform Software Development Kit (SDK) April 2000 Edition and my system is Windows 2000 Professional 5.00.2195 with service pack 4.

Should i upgrade SDK??

With Thanks,
A.Ilamparithi.
June 9th, 2004, 04:42 AM
ilamparithi

re:

Quote:

Originally posted by Andreas Masur
Ohhh....one more thing that comes to my mind...make sure that you have the latest files...in other words...does the function exists in your header file?

Hi Andreas,

I had already checked that.

That function is in the header file. :(

With Thanks,
A.Ilamparithi.
June 9th, 2004, 05:14 AM
usman999_1

Re: re:

Quote:

Originally posted by ilamparithi
Hi Usman,

Iam using Microsoft Platform Software Development Kit (SDK) April 2000 Edition and my system is Windows 2000 Professional 5.00.2195 with service pack 4.

Should i upgrade SDK??

With Thanks,
A.Ilamparithi.

I am not sure about the SDK version problem, But still April 2000 ver is more then 4 yrs old. I would say if possible try upgrading to a newer version first.
Regards,
Usman.
June 9th, 2004, 05:37 AM
ilamparithi

Re: Re: re:

Quote:

Originally posted by usman999_1
I am not sure about the SDK version problem, But still April 2000 ver is more then 4 yrs old. I would say if possible try upgrading to a newer version first.
Regards,
Usman.

Hi Usman,

If that is the case, then the header file itself should not have the function definition know??

But, that is not the case here. In the header file, the function definition is there.

With Thanks,
A.Ilamparithi.
June 9th, 2004, 05:41 AM
Andreas Masur

Quote:

Originally posted by usman999_1
Well thats a linker error, and #ifdef are resolved at compile time. So defining WIN_VER wont matter.

Well...you are right about the technical aspect....however, many functions (usually functions not available for all Windows operating systems) are covered by such a guard to prevent using these functions on systems which do not support these...and in this case 'WINVER' etc. does matter pretty much... :cool:
June 9th, 2004, 05:42 AM
Andreas Masur

Re: Re: Re: re:

Quote:

Originally posted by ilamparithi
In the header file, the function definition is there.

Then check whether the function is exported through the lib file...using the dependency walker for example...
June 9th, 2004, 06:22 AM
ilamparithi

Re: Re: Re: Re: re:

Quote:

Originally posted by Andreas Masur
Then check whether the function is exported through the lib file...using the dependency walker for example...

Hi Andreas,

How to do it???

Do you mean to open the .lib file in the dependency walker??

I think we cannot open a .lib file in the dependency walker.

If you mean to open the .dll file in the dependency walker, then the function is found when the dll is opened in the dependency walker and the other dependent dlls are also available.

Am i correct or am I missing something?

With Thanks,
A.Ilamparithi.
June 9th, 2004, 07:54 AM
Andreas Masur

Re: Re: Re: Re: Re: re:

Quote:

Originally posted by ilamparithi
Do you mean to open the .lib file in the dependency walker??

If you mean to open the .dll file in the dependency walker, then the function is found when the dll is opened in the dependency walker and the other dependent dlls are also available.

Well...yes, my previous answer was some kind of short...what I meant was actually both...however, for the import library you would rather use 'dumpbin /exports library'...
June 9th, 2004, 08:21 AM
ilamparithi

Re: Re: Re: Re: Re: Re: re:

Quote:

Originally posted by Andreas Masur
Well...yes, my previous answer was some kind of short...what I meant was actually both...however, for the import library you would rather use 'dumpbin /exports library'...

Hi Andreas,

When i used dumpbin, i got info like this

File Type: LIBRARY

Exports

ordinal name

_IcmpCloseHandle@4
_IcmpCreateFile@0
_IcmpParseReplies@8
_IcmpSendEcho2@44
_IcmpSendEcho@32
_do_echo_rep@40
_do_echo_req@40
_register_icmp@0

Summary

A5 .debug$S
14 .idata$2
14 .idata$3
4 .idata$4
4 .idata$5
A .idata$6

IcmpParseReplies seems to be there.

:cry:

Is there is any solution for this??

With Thanks,
A.Ilamparithi.
June 9th, 2004, 09:14 AM
Andreas Masur

Well...this is somehow strange...however, the dependency of the windows header files is controlled by many 'ifdefs' guards...so, one thing that comes to my mind is, that the inclusion of some header leads to a define which prevents the 'icmpapi' header file...

However, I haven't dealt with that stuff before...
June 9th, 2004, 09:34 AM
Mick

the prototype in the header is incorrect...

Code:

DWORD IcmpParseReplies( LPVOID ReplyBuffer, DWORD ReplySize );

needs to be __stdcall

Code:

DWORD WINAPI IcmpParseReplies( LPVOID ReplyBuffer, DWORD ReplySize );

either change the icmpapi.h or define the prototypes yourself <with EXTERN_C or extern "C">
June 9th, 2004, 10:49 PM
ilamparithi

Great!

Quote:

Originally posted by Mick
the prototype in the header is incorrect...

Code:

DWORD IcmpParseReplies( LPVOID ReplyBuffer, DWORD ReplySize );

needs to be __stdcall

Code:

DWORD WINAPI IcmpParseReplies( LPVOID ReplyBuffer, DWORD ReplySize );

either change the icmpapi.h or define the prototypes yourself <with EXTERN_C or extern "C">

Hi Mick,

Great Mick!

It works!

Thanks a lot!

Thank you Andreas and Usman for your help!

With Thanks,
A.Ilamparithi.

All times are GMT -5. The time now is 11:18 AM.