Anyone use Borland C++ with ESQL/C?
Posted in 2007
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL
ESQL/C on Windows is documented as working with Borland C++ Version 5 ( http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.esqlc.doc/esqlc75.htm ) Does anyone actually use Borland with ESQL/C? If so which version of C++ and Client SDK? If Borland support were to be dropped would it bother anyone? and finally.. are their any Windows C compilers you would use if they were supported by ESQL/C? (e.g. Cygwin, Intel, Watcom etc)? Thanks Guy
Guy Bowerman wrote: > ESQL/C on Windows is documented as working with Borland C++ Version 5 ( > http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.esqlc.doc/esqlc75.htm > ) > > Does anyone actually use Borland with ESQL/C? If so which version of C++ > and Client SDK? > > If Borland support were to be dropped would it bother anyone? > > and finally.. are their any Windows C compilers you would use if they > were supported by ESQL/C? (e.g. Cygwin, Intel, Watcom etc)? Support for the GNU for Windows ports would be nice. Art S. Kagel
On Wed, 2007-03-28 at 02:48 +0000, Guy Bowerman wrote: > ESQL/C on Windows is documented as working with Borland C++ Version 5 ( > http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.esqlc.doc/esqlc75.htm > ) > > Does anyone actually use Borland with ESQL/C? If so which version of C++ > and Client SDK? > > If Borland support were to be dropped would it bother anyone? > > and finally.. are their any Windows C compilers you would use if they > were supported by ESQL/C? (e.g. Cygwin, Intel, Watcom etc)? > > Thanks > Guy I already use ESQL/C with mingw32/gcc to provide the Windows binaries for my InformixDB Python module. Of course, some trickery is involved. The module build process simply invokes only the esqlc preprocessor. The compilation of the resulting C code is invoked separately. Also, I had to use some magical mingw32 tools to conjure up link libraries for the Informix Client DLLs in a format that the gcc linker understands. Despite the trickery, the end result seems to be working. At least none of the "dozens" of users that have downloaded the module have complained ;-) -Carsten