Home > Back-end > About XXX. The problem of lib introduction of call
About XXX. The problem of lib introduction of call
Time:10-09
H header file. # # ifndef _ILBC_H # define _ILBC_H
# include & lt; Mmsystem. H> //macro definition, if the system didn't declare WINAPI, is declared, it is a standard _stdcall invocation style # # ifndef WINAPI # define WINAPI _stdcall # endif
//////////////////////////////////////////
# ifdef __iLBC_DLL_IMPORT
# include "iLBC_encode. H" # include "iLBC_decode. H"
Generate a lib and a DLL I opened another DLL project to introduce the lib after introduction, what should call? I am a c + + white to find more information or do not understand, you great god, beg to solve!
Or you can give me a direct call iLBC. Lib also tell me how to use! The last 30 points, to solve!
CodePudding user response:
Exe DLL in the same folder Lib to try to introduce in the compiler Point file to expand into the function called statement or directly include your export function. H file
CodePudding user response:
. Libraries (lib) is divided into two kinds, one kind is a dynamic library (DLL) import libraries, one is static library (including implementation), it seems that you use is the first,
Then in your Project, contains the lib library after the corresponding header file, put the lib files are added to the Project can directly use the functions (Project - & gt; Add to the project)
CodePudding user response:
# include "iLBC. H" # pragma link "iLBC. Lib//with this line, is to tell the link, link to join iLBC. The lib, the lib files are added to the engineering effect is the same,