[unixODBC-dev] ODBCConfig (QT4) on Solaris 10

Peter Harvey pharvey at peterharvey.org
Thu Aug 13 19:57:32 BST 2009


We can probably find a way for you to use Qt3 (assuming your concerns over the 
license are well founded). I have a commercial license.

I would much rather spend my time on the new version however ;) In fact; I 
have some changes in the works. I will get them checked in and make a release 
(including some binaries) - just waiting for Nick to pull the trigger on the 
next release of the Core.

Also; I have a sparc box here - which may be of some help.


On Thursday 13 August 2009 10:00:43 am David Brown wrote:
> [Hi Nick & Peter - I tried sending this to
> unixodbc-dev at mailman.unixodbc.org but it doesn't appear to have gotten
> through. BTW, I really appreciate all the work you guys do for unixODBC -
> wish I could contribute more than I do.  I have access to a number of
> systems - AIX, HP-UX (PA-RISC), Solaris SPARC (with manufacturer-supplied
> compilers), FreeBSD, MacOS & Linux - and would be willing to run test
> builds of 2.2.15 when it gets close to release, but don't really have the
> bandwidth or in-depth knowledge to do a lot of troubleshooting if things
> don't build or function properly]
> We have a driver (StarSQL) (commercial product) that works with unixODBC.
> Up until now, we have been including only the non-GUI components of the
> driver manager.
> We now have a need to include ODBCConfig (and libodbcinstQ.so and our own
> setup library).
> No problems on Linux (where QT3 is already present).
> But we're having a lot of problems for our other platforms - I'm starting
> with Solaris, but will need to do the same for AIX & HP-UX.
> (we also support FreeBSD, but I'm not expecting any problems there because
> it also has Qt present).
> It is my understanding that only QT 4.5 and later is covered by LGPL -
> earlier versions of QT are either GPL or commercial.  So I am working with
> QT 4.52.
> We just upgraded our Solaris system from Solaris 8 to Solaris 10 (and the
> compiler environment to the latest - Sun Studio 12 update 1).
> After some struggle, I got QT 4.52 to build (using
> ./configure -opensource -make libs -make tools - I got build errors in the
> examples, which I don't need)
> I then built unixODBC 2.2.14p2 - had a couple of minor issues (see next
> email) but it built.
> ODBCConfig starts up OK (I was a bit startled by the change in the UI from
> the QT3 version) but parts of it are non-functioning -
> the existing DSN's, existing drivers (as displayed under list of installed
> drivers, and displayed when I click to Add a new DSN) are displayed in a
> grid - but when I try to click on a line in the grid, nothing happens.  The
> rest of the UI behaves as expected.
> Suggestions? Is anyone else using odbcinstQ4 on Solaris?
> I'd rather work with the released version of unixODBC (2.2.14p2) rather
> than the 2.2.15 pre stuff from CVS - I know that the GUI stuff has all
> moved in 2.2.15 (so I expect I might encounter even more issues there)
> I'm also trying a build of QT3 right now to see if it behaves any better
> (and for our purposes, would be preferable so that the UI that we document
> with screen shots in our documentation matches what we've already
> documented for Linux).  However, I am not sure about the distribution
> rights for QT3 - possibilities might be:
> * buy a commercial license so we can redistribute QT3
> * package QT binary with unixODBC - or perhaps by itself? - in a package
> that we freely distribute (so we can use the GPL license) totally separate
> from our commercial package.
> The latter would be a hassle for a customers, since we would prefer a
> single click installation, though I suppose we could have it in a separate
> package that is
> installed by a master setup program.
> David Brown

More information about the unixODBC-dev mailing list