Eclipse Target Communication Framework 1.1.0
Primary tabs
Release Date:
Wednesday, June 26, 2013
Deliverables:
- TCF Source Code, tagged TCF_1_1 in the project's "agent" and "main" git repositories. Service releases are planned which will have the tags TCF_1_1_1 and TCF_1_1_2 for SR-1 and SR-2 respectively.
- TCF Update Site at http://download.eclipse.org/tools/tcf/releases/1.1
- Source Tarballs for agent and main, via the Eclipse.org git interface (downloadable).
- Zipped p2 repository of TCF Eclipse plug-ins (downloadable)
- TCF also feeds its Eclipse plugins to the Kepler simultaneous release.
Compatibility:
- TCF Protocol Compatibility: The TCF 1.1 protocol is binary compatible on the wire with previous releases. New features have been added in a discoverable fashion, extending older versions of the protocol.
- API Compatibility: The 1.1 release is fully compatible with TCF 1.0. An extension for signal numbers > 32 on the agent can be turned off if desired.
- Binary (plug-in) Compatibility: We have no binary compatibility issues to discuss for 1.1.
- Source Compatibility: We have no source compatibility issues to discuss for 1.1.
Internationalization:
- The TCF Agent (C code), Services API, and Python and Lua bindings use plain English messages that do not support internationalization.
- 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.
Target Environments:
- The TCF C Agent is being tested routinely on Linux (gcc), Windows (Microsoft, Cygwin and MinGW compilers) and VxWorks. Compilation on MacOS X Darwin, FreeBSD and other POSIX compliant systems should work without problems for the TCF Core. Services can be disabled on a case-by-case basis. Frequent unit and stress tests are run on various Linux distributions.
- The Java and Eclipse clients are tested with Oracle Java 6 and 7 on Eclipse 3.8 Juno and Eclipse 4.3 Kepler on Windows, Linux and MaxOS X 32-bit and 64-bit respectively.
- The Python binding requires Python 2.6 or newer (does not work with Python 3.x due to language incompatibilities).
- The Lua binding is tested with Lua 5.2.1 on Linux.
Themes:
ARM Debug Support
Initial ARM Debug support is added to the TCF Agent.
End-to-end workflows in Target Explorer
The Target Explorer is enhanced to support TCF workflows end-to-end, including discovery of agents, proxying / tunneling, dynamic launching of value-adds, process launch and attach.
Robustness and Documentation
API Documentation is revised, and a strong focus is put on testing and quality with a focus on end-to-end workflows for Debugging.
This release is part of Kepler.