Re: adding a lib to the hal.lib

Probably an error in your sources file, which you didn't post. Note that
the best way to do this is probaby to not reference the new library in
hal.lib, but reference it in your targets in the BUILDEXE tree. You should
be using TARGETLIBS in that tree.

The _CloseHandle reference is probably coming in because of a function you
referenced in your new code.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Gizmo" <jens.fuellemann@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:1148980117.525558.255430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
hi all

i have a problem to add a self created lib to the existing hal.lib in
the platform part.

i try to replace the existing drwatsorn functionality with an own self
created on which allows to dump on non volatile storage. for this case
i wrote a static library called kerneldump.lib.
in the oeminit() function i do reprogramm the global function pointers
with the new ones i wrote from my kerneldump.lib.

so i added the kerneldump.lib to the souces file under SOURCELIBS
section. the hal.lib is linked whitouht problems.

--> but when i try to build the kern.exe which needs the hal.lib i get
this strange errors:

BUILD: [01:0000000050:ERRORE] hal.lib(Init.obj) : error LNK2019:
unresolved external symbol _CFDrWatsonWrite referenced in function
_OEMPostInit
BUILD: [01:0000000051:ERRORE] hal.lib(Init.obj) : error LNK2019:
unresolved external symbol _CFDrWatsonRead referenced in function
_OEMPostInit
BUILD: [01:0000000052:ERRORE] hal.lib(Init.obj) : error LNK2019:
unresolved external symbol _CFDrWatsonClear referenced in function
_OEMPostInit
BUILD: [01:0000000053:ERRORE] hal.lib(Init.obj) : error LNK2019:
unresolved external symbol _CFDrWatsonFlush referenced in function
_OEMPostInit
BUILD: [01:0000000054:ERRORE] hal.lib(Init.obj) : error LNK2019:
unresolved external symbol _CloseHandle referenced in function
_OEMPostInit

the unresolved external symbols are all implemented in the
kerneldump.lib.
the _coloseHandle error is completly strange for me.

now my question:
1. why do i get these errors whe i build the kern.exe and not at the
time when i build the hal.lib? and how can i eliminate them?

can anybody help me?
regards gizmo



.

Relevant Pages

  • Re: Unresolved Externals creating driver
    ... usbpdi.obj: error LNK2019: unresolved external symbol ... > an identical driver, under a different name. ... > I get in this vicious circle of putting in a reference to a library, ... > having the build complain about multiply defined symbols. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Trying to build berkeleyDB module against M$ VStudio 2005 SDK stuff
    ... The failing command was: ... ran into several other similar occurrences. ... BerkeleyDB.obj: error LNK2019: unresolved external symbol ...
    (comp.lang.perl.modules)
  • Re: Problem in compiling firefox 3 source against my extension
    ... for your reference. ... nsPlayBackUtils.obj: error LNK2019: unresolved external symbol ... nsPlayBackUtils::CheckTitle(class nsIDOMWindow *,class nsAString ... nsPlayBackUtils::GetXULTextNode(class nsIDOMDocument *,class nsAString ...
    (microsoft.public.vc.language)
  • Linker error building DLL with old time(),ctime(), difftime() functions - ideas?
    ... am converting a static C and C++ library to a DLL. ... without MFC support), the reference to "difftime" links in just fine, but ... lCoreSupport.obj: error LNK2019: unresolved external symbol time referenced ... function lSessionClose ...
    (microsoft.public.pocketpc.developer)
  • CRT link error on OAL.EXE and KITL.DLL on CE 6
    ... I link FULLLIBC.DLL into my KITL.DLL and OAL.EXE for my CE 6 BSP but I ... set NOLIBC=1 in my sources file and use TARGETLIBS for the reference ...
    (microsoft.public.windowsce.platbuilder)