ProTcXl can be loaded dynamically into a running ECLiPSe session or it can be linked statically into the ECLiPSe binary file. Static linking should be used first of all on machines where dynamic linking does not work, and second when dynamic loading is slow and would be frequently used. On machines where ECLiPSe uses shared objects for dynamic loading, it is not necessary to make static linking because the dynamic loading of shared libraries is sufficiently fast.
For static linking, first install ProTcXl normally as described above. Then edit the INST_PARAMS file in the ECLiPSe boot/$ARCH directory: set the macro WANT_STATIC_TCL to 'yes'. The macros TCL_LIBRARY_PATH and TK_LIBRARY_PATH may stay empty, because the appropriate paths are taken from the ProTcXl Makefile. The X_LIBRARIES macro, however, must be correctly set to the path where the -lX11 library can be found.
The (re-)install ECLiPSe as described in its README file. For ProTcXl programs it makes no difference if its object files are linked statically or dynamically, the tk library makes automatically the proper initialisation.