“MetaWare(R) announced today at the Embedded Systems Conference
Spring that it is offering an Integrated Development Environment
(IDE) for its High C/C++(TM) and SeeCode(TM) software through the
use of the CodeWright(R) editor from Premia. The addition of an IDE
benefits the growing number of High C/C++ and SeeCode users who
prefer an integrated, point-and-click environment for their
development.
Programmers who are writing their code using the CodeWright
editor and compiling with High C/C++ from the DOS command line can
now compile, link, and debug their application all from the
CodeWright window. Additionally MetaWare has configured CodeWright
to allow its users to manage projects, generate make files, and
interact with the SeeCode Debugger. A MetaWare-specific item is
inserted into CodeWright’s pull down menus during installation of
High C/C++, and when selected it brings up a tabbed dialog for
configuring the High C/C++ compile environment specific to their
development.
‘Selecting CodeWright to serve as our IDE was easy, since the
majority of our customer base was already using the CodeWright
editor,’ states John Ryal, COO of MetaWare. ‘Integration of their
GUI and editor with High C/C++ and SeeCode clearly enhances our
product offering.’
The integration of the CodeWright editor as an IDE for High
C/C++ and SeeCode continues MetaWare’s tradition of providing
developers with the most productive, robust embedded software
development tools in the industry. High C/C++ toolsets include a
C/C++ and Embedded C++ compiler, assembler, linker-locator, and
run-time libraries with source, and the SeeCode Debugger. SeeCode
enables you to simulate your program, or debug it running directly
on the hardware, and is OS-aware and fully thread-capable. SeeCode
offers separate windows for each thread, and the ability to set
thread-specific breakpoints and watchpoints. Additionally,
MetaWare’s own performance analysis tool, the Statistical Profiler,
is included with each license of High C/C++. The Statistical
profiler captures program specifics during compile time and
displays a complete call tree in an ASCII text or graphical format
that shows code bottlenecks, thus allowing the developer to better
optimize their program.”