Re: Linking a LIB file



It could be simpler if you could post the full result of the compilation
(including your error message).
Did you check that your function is not defined as static in the lib? There
is no prob of C/C++?

HTH

--
--
--
----------------------------------------------------------------
Anthony Pellerin (eMVP)
ADENEO (ADESET)
Windows Embedded Consultant
<apellerin AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------
"Rams" <Rams@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de news:
CB67102F-AB9A-45DA-8242-5BFF36BB1FC5@xxxxxxxxxxxxxxxx
Hi Anthony,

Thanks for the quick response. The library file's source entry is
as
below:
TARGETNAME=my_lib
RELEASETYPE=PLATFORM
TARGETTYPE=LIBRARY

The dll source file contains:
TARGETNAME=my_dll
TARGETTYPE=DYNLINK
RELEASETYPE=PLATFORM
SYNCHRONIZE_DRAIN=1
DLLENTRY=DllEntry

SOURCELIBS= \
$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\ceddk.lib \
$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\ufnmdd.lib \
$(_TARGETPLATROOT)\lib\$(_CPUDEPPATH)\cspddk.lib \
$(_TARGETPLATROOT)\lib\$(_CPUDEPPATH)\my_lib.lib
I even have a .def file for this dll file
Can you find any problem in the entries or any area that I need to look
into?

Thanks & Regards,
-Rams

"Anthony Pellerin" wrote:

When compiling a lib, it does not try to resolve external symbols, while
it
does it for a DLL.
So make sure the function is really implmented in the library, not as
static
and be carefull with C and C++ files.
Then in you SOURCES file of your DLL, add your library to the list of
linked
libraries.

HTH

--
--
--
----------------------------------------------------------------
Anthony Pellerin (eMVP)
ADENEO (ADESET)
Windows Embedded Consultant
<apellerin AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78



.



Relevant Pages

  • Re: Linking Application with the Library file
    ... libraries you need in your SDK, ... The DLL will go in the TARGET folder of your BSP and also in the ... <apellerin AT adeneo DOT adetelgroup DOT ...
    (microsoft.public.windowsce.embedded)
  • Re: How the linker imports DLL functions
    ... > DLL and you declare it without __declspecin your source file. ... > The problem is, in all import libraries I've examined, I just can't find the ... > I'm not sure where the stub comes from. ...
    (microsoft.public.vc.language)
  • Re: How to get imagebase after a DLL gets loaded
    ... The main difference between DLL and static library in this context is ... so that it is not meant to be integrated with the client code ... SPEAKING ABOUT STATIC LIBRARIES HERE, AND I *EXPLICITLY* SAID IT THIS ...
    (microsoft.public.win32.programmer.kernel)
  • Re: How to get a .lib from .dll
    ... Using the Borland tools, you should first run "IMPDEF" on the DLL file ... information in it to create ".LIB" import libraries with;)... ... from Windows version to Windows version...so, ...
    (comp.lang.asm.x86)
  • Re: How to get a .lib from .dll
    ... Using the Borland tools, you should first run "IMPDEF" on the DLL file ... information in it to create ".LIB" import libraries with;)... ... from Windows version to Windows version...so, ...
    (alt.lang.asm)

Loading