Re: linking issue



You're clearly doing something squirrelly, but it's not clear from anything
that you've said so far what. Send a *very* small example that yields a
single unresolved external and I'll try it.

I also just realized that you've told us *nothing* about what tools, what
versions, what Windows CE version, what target platform, etc. Are you sure
that the target platform *has* the functions that you're finding unresolved?
If they're DC-related, a device with no display support might not have them.

Paul T.

"Surbhi" <cutiegoyal@xxxxxxxxx> wrote in message
news:1154422631.209497.299740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
i havealready included the libs in Project Settings. but the issue is
my code (of which i have made my lib) consist of Functions which are
mapped into the WinCE API's. so while compiling my application with
this library it is giving me linking issues.

like if WInCE API ReleaseDC() which i have called through my function
say OSL_ReleaseDC()
then it is giving me linking issue like "unresolved external symbol
ReleaseDC() refered in OSL_ReleaseDC()".
i am not able to recognise what is this issue.is this any path issue
which i have to include while compiling or any flags issue.
Please do tell me all the paths and flags needed to compile code on
WinCE.

r_z_aret@xxxxxxxxxxxx wrote:
On 26 Jul 2006 03:50:12 -0700, "Surbhi" <cutiegoyal@xxxxxxxxx> wrote:

Hi
I have made library of my code and is linking one application with that
library. The problem which i am facing in this is that application is
linking with that library but functions used in that are not getting
linked.The functions used in my library are just WinCE API's.Could
anyone tell me what is the issue in this.Is this any compiler flag
issue which i have used while making that library.

Links to built in functions are not established until the application
is linked. I think you need to add to the list of .lib files in
Project->Settings->Link->Object/library modules.
in your _application_ project. Some (but definitely not all) function
descriptions in MSDN Library (AKA F1 Help) specify the required .lib
file.

-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and
please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com



.



Relevant Pages

  • Re: linking issue
    ... my code (of which i have made my lib) consist of Functions which are ... mapped into the WinCE API's. ... which i have to include while compiling or any flags issue. ... Please do tell me all the paths and flags needed to compile code on ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: linking issue
    ... my code (of which i have made my lib) consist of Functions which are ... mapped into the WinCE API's. ... this library it is giving me linking issues. ... which i have to include while compiling or any flags issue. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: DDK W2k3 bug? WNET and WXP build ok, W2k doesnt work
    ... > Linking Executable - ...
    (microsoft.public.development.device.drivers)
  • DDK W2k3 bug? WNET and WXP build ok, W2k doesnt work
    ... W2k does only work for executables and some of the libraries. ... Compiling message file - src\input\kbdclass\kbdlog.mc for all platforms ...
    (microsoft.public.development.device.drivers)
  • RE: Did we ever get a solution to CE6 Slow Debug Message Flusing??
    ... I do some stuff in the WinCE command ... prompt and the debug messages might take an extra 15 seconds or so to flow ... Compiling a code change should be a lot faster than you ae experiencing. ... you're just developing one driver then try just doing a build by right ...
    (microsoft.public.windowsce.platbuilder)