Eclipse Target Communication Framework 1.4.0
Wednesday, June 22, 2016
- TCF Core Java, Python and Ada bindings (tagged as 1.4_neon in the org.eclipse.tcf git repository)
- TCF C Agent and Building Blocks (tagged as 1.4_neon in the org.eclipse.tcf.agent git repository)
- org.eclipse.tcf.repo downloadable p2 repository, includes:
- TCF C/C++ Debugger (Eclipse plug-ins, downloadable as a p2 repository)
- TCF Target Explorer (Eclipse plug-ins, downloadable as a p2 repository)
- CDT GDB Remote via TCF/TE Launcher (Eclipse plug-ins, downloadable as a p2 repository)
- TCF Protocol Compatibility: The TCF 1.4 protocol is binary compatible on the wire with previous releases down to 1.0. New features have been added in a discoverable fashion, extending older versions of the protocol.
- API Compatibility: The TCF-Core 1.4 release is fully compatible with TCF 1.3 and older.
- The Eclipse plugins leverage Eclipse mechanisms for internationalization. All messages are externalized, and have been submitted to the Babel project for translation. No formal testing for internationalization is performed though.
- The TCF Agent (C code), Services API, and Python and Lua bindings use plain English messages that do not support internationalization.
- The Java and Eclipse clients are routinely tested with Oracle Java 7 on Eclipse 3.8.2 Juno, 4.3.2 Kepler, 4.4.2 Luna and 4.5 Mars. Oracle Java 8 is used for testing against Eclipse 4.6 Neon.
The TCF C Agent is being tested routinely on Linux (gcc), Windows (Microsoft, Cygwin and MinGW compilers) and VxWorks.
- Frequent unit and stress tests are run on various Linux distributions as well as VxWorks 7.
- Compilation on MacOS X Darwin, FreeBSD, Solaris and other POSIX compliant systems should work without problems for the TCF Core. Services can be disabled on a case-by-case basis.
- The Python binding requires Python 2.6 or newer. Compatibility with Python 3.x has been significantly improved.
- The Lua binding is tested with Lua 5.2.1 on Linux.