Jedino moze da bude "name mangling" problem u tom slucaju jer bcb i vc++ kompajler razlicito deklarisu export f-je
Nisam mislio na upotrebu takvih lib fajlova vec klasicno pozivanje api f-ja sa LoadLibrary i GetProcAddress ,
sa typdef-om function pointerima koji su deklarisani u cab sdk-u, a samim tim se preskace problem oko *.lib fajlova tj. importa tih f-ja.
Code:
#include <windows.h>
#include "fdi.h"
/* pointers to the functions in the DLL */
static HFDI (FAR DIAMONDAPI *pfnFDICreate)(
PFNALLOC pfnalloc,
PFNFREE pfnfree,
PFNOPEN pfnopen,
PFNREAD pfnread,
PFNWRITE pfnwrite,
PFNCLOSE pfnclose,
PFNSEEK pfnseek,
int cpuType,
PERF perf);
static BOOL (FAR DIAMONDAPI *pfnFDIIsCabinet)(
HFDI hfdi,
int hf,
PFDICABINETINFO pfdici);
static BOOL (FAR DIAMONDAPI *pfnFDICopy)(
HFDI hfdi,
char *pszCabinet,
char *pszCabPath,
int flags,
PFNFDINOTIFY pfnfdin,
PFNFDIDECRYPT pfnfdid,
void *pvUser);
static BOOL (FAR DIAMONDAPI *pfnFDIDestroy)(
HFDI hfdi);
Ostale deklaracije su fdi.h fajlu .
Dosta tezi nacin od onoga sto @itf trazio , al je makar besplatan :)
Viva lollapalooza