Linux Build

Prerequisite:

You may need pip version version 10.0.1 or higher, if not upgrade

# pip3 install --upgrade pip
pip install --upgrade pip
FYI: Unicode encoding

The python interpreter used should match with operating system default Unicode encoding. Some of the Linux flavors, python interpreter is available with UCS2/UTF16 and also UCS4/UTF32. If the OS default for Unicode is UTF32 then the OpenInformix driver will work if the python interpreter is also using the Unicode UCS4/UTF32.

To check which Unicode encoding your python interpreter is using.
>>> import sys
>>> print sys.maxunicode
### output
# if it is built with --enable-unicode=ucs4: then you will see
1114111

# if it is built with --enable-unicode=ucs2: then you will see
65535

Build Python from its source code

By any chance if you don’t have the right python interpreter or you don’t have the development environment for building native library then you may have to build python from its source. Python can be built from it source by using the following steps.

Determine the Unicode encoding needed for your python interpreter. Most of the Linux platforms are by default UCS4/UTF32, the following step is to build python for UCS4/UTF32 Unicode encoded string.

Download and extract python source code

This instruction is for both Python 2.7 and Python 3.x build. The commented Python 3.x build instruction is good for building it from source.

cd /work/dev

rm ./Python
sudo rm -rf ./Python-2.7.13
# sudo rm -rf ./Python-3.6.4
sudo rm -rf ./Python-3.7.1

wget https://www.python.org/ftp/python/2.7.14/Python-2.7.13.tgz
# If Python 3.x
# wget https://www.python.org/ftp/python/3.7.1/Python-3.7.1.tgz
wget https://www.python.org/ftp/python/3.7.1/Python-3.7.1.tgz

tar zxvf Python-2.7.13.tgz
# if python 3.x
tar zxvf Python-3.7.1.tgz

ln -s  ./Python-2.7.13  ./Python
# if python3.x
ln -s  ./Python-3.7.1  ./Python

cd /work/dev/Python
sudo ./configure --enable-unicode=ucs4
Fire the Python build
$ cd /work/dev/Python
$ sudo ./configure --enable-unicode=ucs4
$ sudo make

$ sudo make install

# /work/dev/Python to be added to the path
# install is not needed for driver build thouhg
# sudo altinstall
Upgrade tools
# if python 3.x
sudo pip3 install setuptools --upgrade
sudo pip3 install wheel --upgrade
sudo pip3 install twine --upgrade
pip3 install --upgrade pip

Build Informix Python driver

Clone the informix python driver source code
mkdir /work/t1
cd /work/t1

git clone https://github.com/OpenInformix/IfxPy.git
Set Env for driver build
# sudo ln -s /home/informix/1210UC9 /work/informix
# Assuming 'CSDK' is installed at /work/informix
export CSDK_HOME=/work/informix <= This is optional on 64-bit platforms. If you don't have CSDK installed, in the build phase it will download/install CSDK/ODBC in the MY_PY_DIR\build\lib.linux* folder "onedb-odbc-driver" 
and internally will be set to CSDK_HOME. The "onedb-odbc-driver" could be used to set the value of INFORMIXDIR for runtime.
export MY_PY_DIR=/work/dev/Python <= If not set, then internally, it will use "current directory" to set the value of MY_PY_DIR.
export PATH=/work/dev/Python:$PATH

Fire the driver build

You may choose one of the two build instructions to do the driver build. We recommend Wheel build.

1) The legacy build

cd /work/t1/IfxPy/IfxPy
rm -rf build

# '/work/dev/Python' has added to the path, then
# export PATH=/work/dev/Python:$PATH
# $ which python
# /work/dev/Python/python
# pip install setuptools
python setup.py build > out.txt 2>&1
#python3 setup.py build > out.txt 2>&1

# if all go well, then Informix native python driver will be at

# if Linux x86_64bit with Python 2.7 build then
ls -l ./build/lib.linux-x86_64-2.7/IfxPy.so

# if ARM v7 with Python 2.7 then
ls -l build/lib.linux-armv7l-2.7/IfxPy.so

# if Linux x86_64bit with Python 3.x build then
# ls -l ./build/lib.linux-x86_64-3.5/IfxPy.cpython-35m-x86_64-linux-gnu.so

# on armv7 with Python 3.x
# ls -l ls ./build/lib.linux-armv7l-3.5/IfxPy.cpython-35m-arm-linux-gnueabihf.so

2) Wheel build

The wheel built package format includes these tags in its filenames, of the form
{distribution}-{version}(-{build tag})?-{python tag}-{abi tag}-{platform tag}.whl.
Other package formats may have their own conventions.

Python Tag

The Python tag indicates the implementation and version required by a distribution. Major implementations have abbreviated codes, initially:

ABI Tag

The ABI tag indicates which Python ABI is required by any included extension modules. For implementation-specific ABIs, the implementation is abbreviated in the same way as the Python Tag, e.g. cp33d would be the CPython 3.3 ABI with debugging.

Platform Tag

The platform tag is simply distutils.util.get_platform() with all hyphens - and periods . replaced with underscore

# Make sure you have installed wheel before doing the build
pip install wheel
#pip3 install wheel

cd /work/t1/IfxPy/IfxPy
rm -rf /work/t1/IfxPy/IfxPy/build
rm -rf /work/t1/IfxPy/IfxPy/dist



python setup.py bdist_wheel
#python3 setup.py bdist_wheel

# If Linux x86_64 then
python setup.py bdist_wheel  --plat-name manylinux1_x86_64
#python3 setup.py bdist_wheel  --plat-name manylinux1_x86_64

# On successful build, it would have created the whl file under dist folder.
# For example :
########### Python 3.x build on Linux x86 64
ls /work/t1/IfxPy/IfxPy/dist/IfxPy-3.0.1-cp35-cp35m-linux_x86_64.whl
# Copy the binary to prebuild (if you are refreshing the prebuild binary)
cp /work/t1/IfxPy/IfxPy/dist/IfxPy-3.0.1-cp35-cp35m-linux_x86_64.whl /work/t1/IfxPy/prebuilt/3x/Linux64/.
# FYI: to install
# pip3 install /work/t1/IfxPy/prebuilt/3x/Linux64/IfxPy-3.0.1-cp35-cp35m-linux_x86_64.whl
Post successful installation of wheel file, you would see "onedb-odbc-driver" in the "site-packages" directory. The "onedb-odbc-driver" could be used to set the value of INFORMIXDIR for runtime.


######### ARM v7
# /work/t1/IfxPy/IfxPy/dist/IfxPy-3.0.1-cp27-cp27mu-linux_armv7l.whl
# /work/t1/IfxPy/IfxPy/dist/IfxPy-3.0.1-cp35-cp35m-linux_armv7l.whl

# Python 3.x wheel build to the prebuilt location for ARM v7
# cp /work/t1/IfxPy/IfxPy/dist/IfxPy-3.0.1-cp35-cp35m-linux_armv7l.whl /work/t1/IfxPy/prebuilt/3x/ARM/.
# md5sum /work/t1/IfxPy/prebuilt/3x/ARM/IfxPy-3.0.1-cp35-cp35m-linux_armv7l.whl

# You may use pip install to install the driver from the whl file
# For example:
# pip3 install  /work/t1/IfxPy/prebuilt/3x/ARM/IfxPy-3.0.1-cp35-cp35m-linux_armv7l.whl
# pip3 uninstall  /work/t1/IfxPy/prebuilt/3x/ARM/IfxPy-3.0.1-cp35-cp35m-linux_armv7l.whl

Install from the Wheel build

You may use pip install to install the driver build

# Example:
pip3 install   /work/t1/IfxPy/prebuilt/3x/Linux64/IfxPy-3.0.1-cp35-cp35m-linux_x86_64.whl

pip3 uninstall /work/t1/IfxPy/prebuilt/3x/Linux64/IfxPy-3.0.1-cp35-cp35m-linux_x86_64.whl

# if ARM v7
# pip3 install    /work/t1/IfxPy/prebuilt/3x/ARM/IfxPy-3.0.1-cp35-cp35m-linux_armv7l.whl

# pip3 uninstall  /work/t1/IfxPy/prebuilt/3x/ARM/IfxPy-3.0.1-cp35-cp35m-linux_armv7l.whl

upload the driver binaries to PyPi

We have been using Wheel build to upload the binary. FYI: You need to have PiPy account and permission to upload the build binary

cd /work/t1/IfxPy/IfxPy

# make sure pip and wheel are upgradedfs
# pip2.7 install --upgrade --user travis pip setuptools wheel

python setup.py bdist_wheel  --plat-name manylinux1_x86_64
#python3 setup.py bdist_wheel  --plat-name manylinux1_x86_64

#ls dist
# Py3x:   IfxPy-3.0.1-cp35-cp35m-manylinux1_x86_64.whl
# Py27:   IfxPy-2.7.1-cp27-cp27mu-manylinux1_x86_64.whl

#FYI: Upload the build to PyPi
twine upload dist/*
ad hoc testing: Copy the dirver native lib

The native lib is good enough to get advance features working. The Python Database API Specification v2.0 features are wrapper on top of the advance features that can be obtained by copying IfxPyDbi.py

# Copy Informix python package (IfxPy.so) to your Python module directory
# For example:
# Python 2.7 on linux-x86_64
cp /work/t1/IfxPy/IfxPy/build/lib.linux-x86_64-2.7/IfxPy.so .

# Python 2.7 ARMv7 
# cp /work/t1/IfxPy/IfxPy/build/lib.linux-armv7l-2.7/IfxPy.so .

# Python 3.x on ARMv7 
# cp /work/t1/IfxPy/IfxPy/build/lib.linux-armv7l-3.5/IfxPy.cpython-35m-arm-linux-gnueabihf.so  ./IfxPy.so

Quick test of the local build

Get a sample code

cd /work/try/
cp /work/t1/IfxPy/Examples/Sample1.py Sample.py

rm IfxPy.so
# rm *.so

# Python 2.7 on linux-x86_64
cp /work/t1/IfxPy/IfxPy/build/lib.linux-x86_64-2.7/IfxPy.so .

# Python 3.x on linux-x86_64
# cp /work/t1/IfxPy/IfxPy/build/lib.linux-x86_64-3.5/IfxPy.cpython-35m-x86_64-linux-gnu.so .

# if ARM then
# cp /work/t1/IfxPy/IfxPy/build/lib.linux-armv7l-2.7/IfxPy.so .

# Python 3.x on ARM v7
# cp /work/t1/IfxPy/IfxPy/build/lib.linux-armv7l-3.5/IfxPy.cpython-35m-arm-linux-gnueabihf.so ./IfxPy.so

Set runtime environment to pick Informix Client SDK libraries

export INFORMIXDIR=/work/informix
export LD_LIBRARY_PATH=${INFORMIXDIR}/lib:${INFORMIXDIR}/lib/esql:${INFORMIXDIR}/lib/cli
# Set the INFORMIXSQLHOSTS too, say 
export INFORMIXSQLHOSTS=/work/dev/srv/ids0/sqlhosts

Run the sample

# '/work/dev/Python' has added to the path, then
# $ which python
# /work/dev/Python/python

cd /work/try/
vi Sample.py
# Edit Sample.py connection information, and then run
python Sample.py