Well, it might be possible to do it using the OCI without any glue at all. In fact, that would be the preferred situation. Daniel had a heck of a time trying to get the marshalling to work properly with it. I think it should be feasible. I don't know a lot about marshalling, but interop gurus could definitely be helpful.
Of course, figuring out what libraries to link against could be a struggle in itself. What were you using? I suppose I could try some more and see what happens. Thanks, Tim > Microsoft's System.Data.OracleClient.dll doesn't use any glue-library. > Perhaps we should investigate further why _we_ have to? > > Note: I have tried to modify the code in > mcs/class/System.Data.OracleClient/System.Data.OracleClient to connect > without the glue, but have so far failed. > > Any interop-gurus who can shed some light on the matter? > > Best regards > Steinar Herland > > > -----Opprinnelig melding----- > Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sendt: 11. februar 2003 05:27 > Til: [EMAIL PROTECTED] > Kopi: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Emne: [Mono-list] Automake: System.Data.OracleClient > > Howdy folks, > > I picked up where Daniel Morgan left off with the Mono OracleClient, > and this client uses a "glue" library to connect the managed provider > with the unmanaged Oracle call interface (OCI). This is written in > C. Daniel had written makefiles for Borland and Visual C; I created > a simple make file that works with GCC on my system. > > I was wondering how easy it would be to create some sort of automake > solution that would build this automatically as part of the class > library build. I know very little about automake, so I'm willing > to take any suggestions, code, whatever. If you want to do it yourself, > you're more than welcome. > > Before we build the code, I think that it should probably be moved > from its present home, but for now it works where it is. It's > in mcs/class/System.Data.OracleClient/System.Data.OracleClient. > The two source files are ociglue.c and ociglue.h. > > The makefile must make use of the user's install Oracle client > libraries, > and if these aren't detected, then the glue library probably shouldn't > be built. In fact, in light of this, maybe the OCI glue library should > be in a separate module. I'm not really sure what the best policy is > for something like this. > > Any insights would be greatly appreciated! > > Thanks, > > -- > Tim Coleman <[EMAIL PROTECTED]> [43.43 N 80.45 W] > BMath, Honours Combinatorics and Optimization, University of Waterloo > "Under capitalism, man exploits man. Under communism, it's just the > opposite." -- J.K. Galbraith > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list > _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
