microsoft visual studio code editor statically linked

It doesn't need to, because it contains the tools to create the kind of library that you want.' Obviously not, I miss the option to pass DLL files as input to the linker. b) Such a reverse-generated static lib would be much smaller than the original static lib. 'And why would the method used by the link I showed you change the situation?' a) Such a tool would get rid of the unnessary symbols (as compared to a static lib) as it only knows about the exported symbols of the DLL. Why do you say a static lib exposes more information than a DLL?' Call dumpbin /EXPORTS for a DLL (in our case we have about 20 functions exported) and then compare this to the visible symbols in a lib file (our lib is built from multiple libs which each are built from multiple objs, so there are thousands of symbols visible, thereby also exposing the internal structure of our SW which we do not want to expose). extern 'C' const char * _stdcall AD_GetVersion ( void ) ) '2. 'What kind of interface does it have?' A number of _stdcall functions (i.e.

as that of the EXE and also relies on internal helper functions of the CRT etc. As opposed to this a normal static lib uses the same malloc/new etc. _stdcall) where is does not matter how and with which compiler/assembler the DLL was created. exe?' Well, I assume that the DLL specification specifies something along the lines that it is possible to have functions within the DLL with a specific interface (i.e. What makes you thin k that your DLL does not need to match the compiler used for the.

Microsoft visual studio code editor statically linked