From: gelbeiche <in...@ra...> - 2007-02-01 22:25:34
|
Am Thu, 01 Feb 2007 16:07:28 -0600 schrieb Jeremy Bettis <je...@de...>: > gelbeiche wrote: > > Am Thu, 01 Feb 2007 15:35:51 -0600 > > schrieb Jeremy Bettis > > <je...@de...>: > > > > > >> The instant client is looking for it's other files in the same > >> folder as the oci.dll. If you copy the oci.dll you must copy all > >> of the instant client files to the same place. > >> > > > > Yep that worked. For my understanding: oci.dll requires some other > > dlls in the same directory to get its work properly, right ? > > I dropped the other dlls in the directory dll by dll and observed > > that the application did not work properly after I removed > > oraociei10.dll. > > > > I looked with a tool named "dependency walker" inside the oci.dll > > and found no dependency to oraociei10.dll. How msut I undestand > > that ? > > > > > Dependency walker only looks at static dependencies, not LoadLibrary > calls I have another related problem. If I build my application not directly under MinGW but with Codeblocks-IDE (which works with the MinGW compiler/tools) I have the same problem: The application will be created but at runtime I get the same initialization routine error from oci.dll. I use the same compiler flags as in my MinGW-Makefile and when I look with "dependency walker" I see the same static dependencies. My PATH variable is the same too, for the native MinGW-Build and the Codeblocks-IDE-Build-EXE (I started the application created from Codeblocks- from the same MSYS-terminal as the application created by the MinGW-Makefile.). What can be the reason for this difference and how can I detect it ? Thomas -- http://www.randspringer.de |