On Tuesday 12 May 2009 17:42:03 OpenDBX devel list wrote: > After spending several hours with this, I think I got it. As I said > "odbxdrv_register" is in libsqlite3backend-1.dll. But when int > _odbx_lib_open( struct odbx_t* handle, const char* backend ) is called, it > first tries to load just "backend" (sqlite3 in this case). And then tries > with > > The idea is this to load the libsqlite3backend-1.dll, but, sqlite3.dll is > found first, in the first if. And obviously, sqlite3.dll doesn't have the > function "odbxdrv_register".
You are right. Windows seems to search for a DLL even if the extension is missing (sqlite3 vs. sqlite3.dll). I've already changed the code for loading and referencing the odbx_register() function. It tries now to get the function address directly after loading the DLL and tries with the next library if the functions wasn't found. I will do more testing and try to find a problem for the path of the backend. Afterwards, a new release candidate will be created. Thank you very much for debugging. Norbert -- OpenPGP public key http://www.linuxnetworks.de/norbert.pubkey.asc
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________ libopendbx-devel mailing list libopendbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libopendbx-devel http://www.linuxnetworks.de/doc/index.php/OpenDBX
