Browse files

Updated documentation

  • Loading branch information...
1 parent 28f6d06 commit 7522f793e635052527b7ca1ceb38715644de3acc @pkleef pkleef committed Mar 27, 2012
Showing with 136 additions and 4 deletions.
  1. +1 −1 ChangeLog
  2. +1 −1 IAFA-PACKAGE
  3. +4 −2 LICENSE.BSD
  4. +10 −0 README.CVS
  5. +120 −0 README.GIT
@@ -1,7 +1,7 @@
- * Added support for Mac OS X 10.7
* Updated version number to 3.52.8
+ * Added support for Mac OS X 10.7
@@ -1,6 +1,6 @@
Title: iODBC Driver Manager
-Version: 3.52.8-rc1
+Version: 3.52.8
Description: iODBC (independent Open Database Connectivity)
driver manager is compatible with ODBC 3.x specification
@@ -1,4 +1,6 @@
-Copyright (C) 1995-2012, OpenLink Software Inc and Ke Jin.
+iODBC Driver Manager
+Copyright (C) 1995 by Ke Jin <>
+Copyright (C) 1996-2012 by OpenLink Software <>
All rights reserved.
Redistribution and use in source and binary forms, with or without
@@ -10,7 +12,7 @@ are met:
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
- 3. Neither the name of OpenLink Software Inc. nor the names of its
+ 3. Neither the name of OpenLink Software nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
@@ -3,6 +3,16 @@ Copyright (C) 1995 by Ke Jin <>
Copyright (C) 1996-2012 by OpenLink Software <>
All Rights Reserved.
+The iODBC development team has decided to use GIT instead of CVS.
+Users who are tracking the iODBC project or want to aid in it's
+development are encouraged to move with us to github via:
+For information about GIT see also README.GIT
@@ -0,0 +1,120 @@
+Using the iODBC GIT Tree
+Copyright (C) 1996-2012 OpenLink Software <>
+This document describes how to checkout a copy of the git tree for
+development purposes. It also lists the packages that need to be
+installed prior to generating the necessary scripts and Makefiles to
+build the project.
+Git access is only needed for developers who want to actively track
+progress of the iODBC source code and contribute bugfixes or
+enhancements to the project. It requires basic knowledge of git
+itself, the general layout of open source and GNU projects, the use
+of autoconf and automake etc, which is beyond the scope of this
+If you have any questions, please email us at <>.
+Git Archive Server Access
+For main development OpenLink Software will publish the iODBC tree
+to GitHub and encourage everyone who is interested in tracking the
+project, to make an account there.
+Users who mainly just want to track the code can use the following
+command to get a copy of the tree:
+ $ git clone git://
+At this point you can create your own work branch based on any of
+the branches available, create bugfixes and commit them to your own
+branch and then use the 'git format-patch' command to generate the
+appropriate diffs to send to:
+Developers are encouraged to fork the project using GitHub, create
+their own branches to make enhancements/bugfixes and then send pull
+requests using the excellent GitHub interface for the OpenLink team
+to examine and incorporate the fixes into the master tree for an
+upcoming release.
+Github has excellent documentation on how to fork a project, send
+pull requests, track the project etc. on:
+OpenLink Software will continue to use for the
+source tarball releases and certain binary releases, and for
+completenes will also provides read-only Git Archive access.
+For more information read:
+Package Dependencies
+To generate the configure script and all other build files necessary,
+please make sure the following packages and recommended versions are
+installed on your system.
+ Package Version From
+ autoconf 2.57
+ automake 1.9
+ libtool 1.5
+ make 3.79.1
+ gtk+ 1.2.10
+and any GNU packages required by these. The and configure
+scripts check for the presence and right version of some of the required
+The above version are the minimum recommended versions of these
+packages. Older version of these packages can sometimes be used, but
+could cause build problems.
+To check the version number of the tools installed on your system,
+use one of the following commands:
+ $ autoconf --version
+ $ automake --version
+ $ libtoolize --version
+ $ make --version
+ $ gtk-config --version
+Generate build files
+To generate the configure script and all related build files, use one
+of the following commands:
+ $ autoreconf --install
+or use the supplied script in your checkout directory:
+ $ ./
+If the above commands succeed without any error messages, please use the
+following command to check out all the options you can use:
+ $ ./configure --help
+Certain build targets are only enabled when the --enable-maintainer-mode
+flag is added to configure.
+Please read the files INSTALL and README in this directory for further
+information on how to configure the package and install it on your system.

0 comments on commit 7522f79

Please sign in to comment.