> From: Dan Stein <[EMAIL PROTECTED]> > Date: 30 March 2005 11:23:17 PM > To: <[email protected]> > Subject: Re: Witango-Talk: Fixes in the latest iodbc > Reply-To: [email protected] > > Phil, > > Is there a way to get this and install it on OSX? > > Dan
Dan, The answer to your question is that there is no easy way. You can download the source code, compile it and install it but this is not for the faint hearted or the hobbyist. You need have an intimate knowledge of iodbc, myodbc, mysql and mach to be able to do it successfully and to be able to roll back when it fails - yes some combinations just don't work on OS X. Also see the warning below if you do attempt it. If OS X is not your OS just click the delete button - you have read enough. To the OS X users I apologise for the rant you are about to read but I think this is the only way forward. You've got me on my soapbox now ... IMHO the only way to get the latest iodbc installed on OS X is to annoy the hell out of Apple to make sure they keep odbc on their radar and updated. Lobby your db vendor to lobby Apple. Every meeting you have with an Apple rep ask them what is happening with odbc and let them know its importance to your business. If you know anyone within Apple lobby them directly. Log every bug you find with odbc and the ODBC Administrator. Actually log them every time you have a problem. The more the merrier. If you are a FileMaker user lobby FileMaker to lobby Apple so that their odbc driver works with the latest iodbc. If you are an organisation that has any influence with Apple please use it no matter how small it may be. The reason odbc is seamless on Windows is because Microsoft control it - where it is installed, how it is configured and how drivers are loaded. They also provide an ODBC Admin tool that works. If we can raise Apple's awareness of the importance of a standard and up to date odbc configuration in the OS then life becomes easier for the application and driver developers who have a predictable configuration. This will then flow on to the end users who will then have access to double-clickable installers. If Apple keeping iodbc up to date then maybe OpenLink will then stop loading a second version of the driver manager on the OS when they install a db driver. We may also see them modify the compile process so that it will update the Apple installed iodbc instead of creating a 3rd instance in the /usr/local/lib directory. For those that haven't tried it yet you can actually end up with iodbc installed in 3 different locations on OS X. /usr/lib another in /usr/local/lib and a third in /Library/Frameworks. They can all be different versions and some drivers will only work with a particular version. Just so that you don't think that I am the only one frustrated by what Apple/OpenLink have done to odbc on OS X this is an extract from the readme.osx file of the latest myodbc source download. <snip> Well; actually I had to reinstall everything after ending up with multiple ODBC systems on my OSX. Apple has not done a good job of taking charge of the core ODBC stuff so the driver vendors and others are all trying to lead it in various self serving directions and this sometimes results in redundant driver managers and drivers with all kinds of degradation of the user experience. </snip> WARNING: Because of the situation described above the myODBC driver you download from dev.mysql.com is built against the default iodbc driver manager shipped by Apple (/usr/lib/libiodbc.2.1.6.dylib). If you load the new iodbc driver manager you will also need to compile your own version of the myodbc3 driver against the new driver manager. Sometimes you just have to grin and bear it. ;) Now that I am off the soapbox - to those that have already started the process, and I know there are a few of you, thank you. Phil ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
