OpenLibrary vs Import

[coder14]

What is the difference or advantage between the two functions? I have both the lib and dll.

Also I asked this before but to reconfirm - is there any way to link libraries (lib, obj, dll) INTO the exe so that it will not need to be distributed? Some explanations on the net explain that static linking with an obj file means that the dll is not required at runtime - that the used functions are extracted and compiled into the exe. (not talking about including the dll in memory )

Is this correct and maybe only that PB is not able to link this way?

All explanations are welcome - great way to learn.

[ts-soft]

What is the difference or advantage between the two functions? I have both the lib and dll.

With lib you make a early-binding, with dll a late-binding (dynamically). The early-binding is faster, but gives immediately a
error, after start the exe, and won't start without the dll!

Is this correct and maybe only that PB is not able to link this way?

This is not correct, but the lib must be designed to not only wrap a dll. The depedency-libs have to link (Import) also.

[coder14]

What is the difference or advantage between the two functions? I have both the lib and dll.

With lib you make a early-binding, with dll a late-binding (dynamically). The early-binding is faster, but gives immediately a
error, after start the exe, and won't start without the dll!

Is this correct and maybe only that PB is not able to link this way?

This is not correct, but the lib must be designed to not only wrap a dll. The depedency-libs have to link (Import) also.

Thank you ts-soft. I think I understand about the early and late bindings - something like constants and variables. So OpenLibrary is dynamic and Import is static, right?

But what do you mean the lib must be designed to not only wrap a dll? PB is not able to include the lib functions directly into the EXE right? In all cases the DLL is required right?

[ts-soft]

It gives different libs, mostly for dll like you can create with polib. This one can't used without DLL.
The other libs, a designed to use without dll (no dll created). This one you can also import, but you have to make sure,
all dependency (other libs, like runtimes) a solved.

SQLite is imported in PB or you can use MemoryModule.lib without DLL.

Code: Select all

CompilerIf #PB_Compiler_Processor = #PB_Processor_x64
  #MemoryModule_Lib$ = "MemoryModule64.lib"
CompilerElse
  #MemoryModule_Lib$ = "MemoryModule.lib" 
CompilerEndIf

Import #MemoryModule_Lib$
  MemoryLoadLibrary(*MemoryPointer)
  MemoryGetProcAddress(hModule, FunctionName.p-ascii)
  MemoryFreeLibrary(hModule)
  MemoryFindResource(hModule, lpName.p-ascii, lpType.p-ascii)
  MemoryFindResourceEx(hModule, lpName.p-ascii, lpType.p-ascii, wLanguage.w)
  MemoryLoadResource(hModule, hResInfo)
  MemoryLoadString(hModule, uID.l, *lpBuffer, nBufferMax.l)
  MemoryLoadStringEx(hModule, uID.l, *lpBuffer, nBufferMax.l, wLanguage.w)
  MemorySizeofResource(hModule, hResInfo)
EndImport

No dll required (only a DLL to use )

[coder14]

It gives different libs, mostly for dll like you can create with polib. This one can't used without DLL.
The other libs, a designed to use without dll (no dll created). This one you can also import, but you have to make sure,
all dependency (other libs, like runtimes) a solved.

SQLite is imported in PB or you can use MemoryModule.lib without DLL.

Code: Select all

CompilerIf #PB_Compiler_Processor = #PB_Processor_x64
  #MemoryModule_Lib$ = "MemoryModule64.lib"
CompilerElse
  #MemoryModule_Lib$ = "MemoryModule.lib" 
CompilerEndIf

Import #MemoryModule_Lib$
  MemoryLoadLibrary(*MemoryPointer)
  MemoryGetProcAddress(hModule, FunctionName.p-ascii)
  MemoryFreeLibrary(hModule)
  MemoryFindResource(hModule, lpName.p-ascii, lpType.p-ascii)
  MemoryFindResourceEx(hModule, lpName.p-ascii, lpType.p-ascii, wLanguage.w)
  MemoryLoadResource(hModule, hResInfo)
  MemoryLoadString(hModule, uID.l, *lpBuffer, nBufferMax.l)
  MemoryLoadStringEx(hModule, uID.l, *lpBuffer, nBufferMax.l, wLanguage.w)
  MemorySizeofResource(hModule, hResInfo)
EndImport

No dll required (only a DLL to use )

Thank you ts-soft. I think I understand now.

[jacdelad]

It gives different libs, mostly for dll like you can create with polib. This one can't used without DLL.
The other libs, a designed to use without dll (no dll created). This one you can also import, but you have to make sure,
all dependency (other libs, like runtimes) a solved.

SQLite is imported in PB or you can use MemoryModule.lib without DLL.

Code: Select all

CompilerIf #PB_Compiler_Processor = #PB_Processor_x64
  #MemoryModule_Lib$ = "MemoryModule64.lib"
CompilerElse
  #MemoryModule_Lib$ = "MemoryModule.lib" 
CompilerEndIf

Import #MemoryModule_Lib$
  MemoryLoadLibrary(*MemoryPointer)
  MemoryGetProcAddress(hModule, FunctionName.p-ascii)
  MemoryFreeLibrary(hModule)
  MemoryFindResource(hModule, lpName.p-ascii, lpType.p-ascii)
  MemoryFindResourceEx(hModule, lpName.p-ascii, lpType.p-ascii, wLanguage.w)
  MemoryLoadResource(hModule, hResInfo)
  MemoryLoadString(hModule, uID.l, *lpBuffer, nBufferMax.l)
  MemoryLoadStringEx(hModule, uID.l, *lpBuffer, nBufferMax.l, wLanguage.w)
  MemorySizeofResource(hModule, hResInfo)
EndImport

No dll required (only a DLL to use )

I know, I'm a bit late, but shouldn't the .l-datatypes be .i-datatypes?

[idle]

probably not unless its a pointer, windows mostly uses ints for parameters so .l longs or short int .w/.u

[jacdelad]

Sorry for asking again, but isn't it possible that the address the pointer is pointing to is above MAXINT in a x64-system?

[idle]

yes a pointer can of course point to a larger value, like values in XMM/YMM/ZMM registers 128/256/512