Table of Contents
Getting Started
- Download relevant source code release
- Build and test on desired platforms
Note: If in either one of the steps above you stumble across any problems/bugs, please contact the OpenLink iODBC source archive manager at iodbc@openlinksw.com . Please provide as much information regarding the type of platform, compiler, compiler flags etc. in your bug report, we will try to get back in touch with you rapidly.
Bug Fixes
If you find a bug and have the know-how to fix it, please create a "diff file" using GNU's "diff", possibly with "context" (diff -c or diff -u).
If the patch is small, add the patch file as an attachment to your mail if possible, otherwise tell us where we can pick it up. This will reduce the turnaround time for new updates etc.
Suggestions
Suggestions for new features can be discussed with us, through one of the following forums:
- Using the Sourceforge.net mailing-lists.
- Using OpenLink's support phpBB discussion forum for general ODBC questions
- Direct e-mail to iodbc@openlinksw.com
Ideas are welcome at all times; ideas accompanied by the code that demonstrates core concepts are even more welcome.
Standards Enforcement
This initiative's greatest value is the provision of a cross-platform development interface that conforms to both the Microsoft ODBC and X/Open SQL CLI data access specifications. Thus, ensure that code contributions do not compromise this prime objective.
We will adhere to the official Microsoft ODBC and X/Open SQL CLI specs at all times.
Project Management
If you want to contribute news ideas and functionality, please talk to us on either the mailing-lists or discussion forum in advance, as this reduces the chance of development overlaps.
Development Standards
All iODBC Driver Manager development needs to be done in ANSI C to ensure the best cross platform compatibility. Code submissions need to be properly indented (we use the GNU 'indent' program) and commented in order to make group development as productive as possible.