DOCSLIB.ORG

Codewarrior Data

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Codewarrior Data 1 ® Development Tools The CodeWarrior Development Studio everything the professional embedded CodeWarrior® Development provides a highly visual and automated developer needs: Studio is a complete framework that accelerates the development • CodeWarrior C/C++ Compiler Suite of even the most complex applications. • Runtime libraries integrated development Creating applications is fast and easy for • Assembler environment (IDE) from developers of all experience levels. As • Standard template library (STL) hardware bring-up through a single development environment, it is consistent across all supported workstations programming embedded and personal computers with an organization. Source-Level Debugger applications. By combining On each of the supported platforms, the Provides a high-performance windowed source-level debugger equipped with the state-of-the-art debugging features and uses are identical. There is no need to worry about host-to-host latest productivity—enhancing graphical technology with the simplicity incompatibilities. Learn once, use everywhere. features to shorten board bring-up and of a robust development application development time; uses the environment, CodeWarrior The CodeWarrior Development Studio symbolics database to provide source-level contains all of the tools needed to complete debugging; supports symbol formats such Development Studio takes a major embedded development project. as Microsoft® CodeView®, Debug With source-level debugging Arbitrary Records Format (DWARF) and embedded application Complete Set of Tools and STABS. From text editors to compilers and debuggers, development to a new level. CodeWarrior development studio provides 2 Instruction Set Simulator Text Editor Source Browser Jump-starts application development with Enables the creation and manipulation Maintains a symbolics database for the an integrated instruction set simulator (ISS). of source code and other text files and program (examples of symbols include is completely integrated with other names and values of variables and functions); Project Manager IDE functions. uses the symbolics database to assist code Handles top-level file management for the navigation; links every symbol to other software developer; organizes project items locations in the code related to that symbol; by major group, such as files and targets; Search Engine processes both object-oriented and tracks state information (such as file Finds a specific text string or replaces found procedural languages. modification dates); determines build order text with substitute text across multiple and inclusion of specific files in each build; files and directories; allows use of regular coordinates with plug-ins to provide services expressions; provides file-comparison and like version-control and RTOS support. differencing functionality. Debugger By combining a state-of-the-art IDE with the simplicity of a windowed environment, the debugger takes C/C++ source-level debugging to a new level. The debugger assembles a wide array of high- powered components and features into a powerful GUI to help get projects completed and to market ahead of schedule and under budget. All of the debugger hardware and software features provide simple access and execution. Any debug operation desired is done through an intuitive “point-and-click” interface to make debugging fast, flexible and easy. Window-Based Workspace Seamless Integration Single-Stepping Environment The debugger is fully integrated with a variety Supports the common single-stepping The debugger enables developers to operate of run-control devices like Ethernet TAP and mechanisms (Step Into, Step Over, Step more efficiently with user-friendly debugging, CodeWarrior USB TAP, resulting in optimized Out), stepping statements in source-level multiple windows, point-and-click capabilities run-control and faster downloads. display and instructions in Assembler and and outline format. mixed-mode level display. Single-stepping can be performed in any of the source code Full-Featured Debugging display windows (stack crawl window, class The debugger’s interface allows users to The debugger provides a rich set of browser window, source file window and customize the workspace to fit their needs: debugging features designed to help symbolics window). to create custom buttons, toolbars and the developer quickly find and repair menus, and to “float” windows that are an software defects. Contextual Data integral part of the debugger so that they Displays data values at a glance for become independent windows on the work Stack Crawl Window variables in source windows during station. This provides increased visibility and Displays information about a suspended execution. In addition to standard toolbar control over the display of information in the thread or process while debugging—all in tool tips common to applications, the debugger. Windows that have been separated debugger reveals contextual data when the primary window used during a debug from the debugger can also be “docked” to developers mouse over the variable in the session. The stack crawl window can be rejoin the main debugger workspace controls. source statement. used to view the call stack for a function, view function variables and global data, The debugger’s workspace allows users view a routine in source, assembler or Preprocessor Information to focus on complex debugging tasks. mixed-mode, view the current program Provides clear understanding of the code Each workspace contains just the set of being generated and relevant scoping counter indicating the statement about views needed for the task at hand. The used during the build cycle in the current to be executed, view and set breakpoints application workspace provides a high-level debug context. for the current function or single-step view of the target software, while the through the current function from the hardware workspace provides a low-level program counter. view of the target hardware. 3 Breakpoints Special Breakpoints Register Details Window Sets breakpoints in source display windows Special breakpoints halt program execution Shows the contents of a given register in with a simple click on the window’s left for very specific reasons, such as when pro- a format similar to a processor data book. margin or by dragging a source statement gram execution arrives at the beginning of the Register and bit field descriptions are included or assembly instruction to the breakpoints function main(), a C++ exception occurs or an along with logical groupings of bits into value window. A separate breakpoints window event occurs that the debugger plug-in has fields. Bit field values can be modified manu- in the debugger allows developers to view defined as a break event. Developers cannot ally or from a list of relevant value choices. all breakpoints consolidated into a single change or delete special breakpoints, but they The display of register details is controlled by worksheet and save them to disk for use can enable and disable them. a user-modifiable XML register description file. later or for sharing with other project members. Memory Window Cache Window CodeWarrior Debugger Displays data in various data formats: raw Displays current values and state of cache Offers Many Different hexadecimal and ASCII, standard C data contents for each data and instruction cache Types of Breakpoints types, structures and enumeration types within the target processor. Cache writes allow from the current debug project, or as developers the freedom to edit cache contents Eventpoints machine instructions either in machine and experiment with cache behavior as it Eventpoints are used to perform a task language assembly or displayed related to relates to the current code being debugged. when program execution arrives at a source code. The memory window displays specific line of source code or when an data in a “raw” hexadecimal format, as well Object File Format associated conditional expression evaluates as ASCII, with the word-length variable Supports STABS and ELF/DWARF to true. Developers can set an eventpoint through a drop-down selection at the bottom (version 1 and 2) object file output formats. that performs a task such as logging or of the screen. The memory window allows speaking a string or expression and then for the display and editing of memory Multi-Thread/Process Debugging* recording messages to the log window, locations. Allows for editing in the context Enables debugging of multi-threaded applications pausing execution just long enough to refresh of the current display format—for example, and multiple processes. Debugging can select debugger data, running a script, playing a “view as int” allows editing an integer value. and debug a single thread, multiple threads sound, skipping execution of a line of source Establishes selected memory addresses as or all threads—based on debug preferences. code or collecting trace data. An eventpoint is a watchpoint for conditional execution simply Each thread being debugged can be managed equivalent to a breakpoint that performs a task by right-click mouse selection. through the threads window or separate stack other than halting program execution. crawl windows per thread. Register Window *This capability is not available for all processors. Watchpoints Shows a complete list of available processor Watchpoints halt program execution when and peripheral registers, both built-in and a specific location in memory changes value. memory mapped. Registers are grouped Multi-Core Debugging
Load more

Recommended publications
  • Codewarrior™ Development Studio for Freescale™ 56800/E Digital Signal Controllers: Mc56f8xxx/Dsp5685x Family Targeting Manual
    CodeWarrior™ Development Studio for Freescale™ 56800/E Digital Signal Controllers: MC56F8xxx/DSP5685x Family Targeting Manual Revised: 19 June 2006 Freescale, the Freescale logo, and CodeWarrior are trademarks or registered trademarks of Freescale Corporation in the United States and/or other countries. All other trade names and trademarks are the property of their respective owners. Copyright © 2006 by Freescale Semiconductor company. All rights reserved. No portion of this document may be reproduced or transmitted in any form or by any means, electronic or me- chanical, without prior written permission from Freescale. Use of this document and related materials is gov- erned by the license agreement that accompanied the product to which this manual pertains. This document may be printed for non-commercial personal use only in accordance with the aforementioned license agreement. If you do not have a copy of the license agreement, contact your Freescale representative or call 1-800-377-5416 (if outside the U.S., call +1-512-996-5300). Freescale reserves the right to make changes to any product described or referred to in this document without further notice. Freescale makes no warranty, representation or guarantee regarding the merchantability or fitness of its products for any particular purpose, nor does Freescale assume any liability arising out of the application or use of any product described herein and specifically disclaims any and all liability. Freescale software is not authorized for and has not been designed, tested, manufactured, or intended for use in developing applications where the failure, malfunc- tion, or any inaccuracy of the application carries a risk of death, serious bodily injury, or damage to tangible property, including, but not limited to, use in factory control systems, medical devices or facilities, nuclear facil- ities, aircraft navigation or communication, emergency systems, or other applications with a similar degree of potential hazard.
    [Show full text]
  • Porting Codewarrior Projects to Xcode
    Porting CodeWarrior Projects to Xcode 2006-09-05 Intel and Intel Core are registered Apple Computer, Inc. trademarks of Intel Corportation or its © 2003, 2006 Apple Computer, Inc. subsidiaries in the United States and other All rights reserved. countries. Java and all Java-based trademarks are No part of this publication may be trademarks or registered trademarks of Sun reproduced, stored in a retrieval system, or Microsystems, Inc. in the U.S. and other transmitted, in any form or by any means, countries. mechanical, electronic, photocopying, recording, or otherwise, without prior OpenGL is a registered trademark of Silicon written permission of Apple Computer, Inc., Graphics, Inc. with the following exceptions: Any person PowerPC and and the PowerPC logo are is hereby authorized to store documentation trademarks of International Business on a single computer for personal use only Machines Corporation, used under license and to print copies of documentation for therefrom. personal use provided that the Simultaneously published in the United documentation contains Apple’s copyright States and Canada. notice. Even though Apple has reviewed this document, The Apple logo is a trademark of Apple APPLE MAKES NO WARRANTY OR Computer, Inc. REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS Use of the “keyboard” Apple logo DOCUMENT, ITS QUALITY, ACCURACY, MERCHANTABILITY, OR FITNESS FOR A (Option-Shift-K) for commercial purposes PARTICULAR PURPOSE. AS A RESULT, THIS without the prior written consent of Apple DOCUMENT IS PROVIDED “AS IS,” AND YOU, THE READER, ARE ASSUMING THE may constitute trademark infringement and ENTIRE RISK AS TO ITS QUALITY AND unfair competition in violation of federal ACCURACY.
    [Show full text]
  • Development of a Personal Diet Plan Database Application for Persons with Severe Food Allergies Heather Suzanne Ward Regis University
    Regis University ePublications at Regis University All Regis University Theses Summer 2005 Development Of A Personal Diet Plan Database Application For Persons With Severe Food Allergies Heather Suzanne Ward Regis University Follow this and additional works at: https://epublications.regis.edu/theses Part of the Computer Sciences Commons Recommended Citation Ward, Heather Suzanne, "Development Of A Personal Diet Plan Database Application For Persons With Severe Food Allergies" (2005). All Regis University Theses. 772. https://epublications.regis.edu/theses/772 This Thesis - Open Access is brought to you for free and open access by ePublications at Regis University. It has been accepted for inclusion in All Regis University Theses by an authorized administrator of ePublications at Regis University. For more information, please contact [email protected]. Regis University School for Professional Studies Graduate Programs Final Project/Thesis Disclaimer Use of the materials available in the Regis University Thesis Collection (“Collection”) is limited and restricted to those users who agree to comply with the following terms of use. Regis University reserves the right to deny access to the Collection to any person who violates these terms of use or who seeks to or does alter, avoid or supersede the functional conditions, restrictions and limitations of the Collection. The site may be used only for lawful purposes. The user is solely responsible for knowing and adhering to any and all applicable laws, rules, and regulations relating or pertaining to use of the Collection. All content in this Collection is owned by and subject to the exclusive control of Regis University and the authors of the materials.
    [Show full text]
  • Java Core Technologies (Part III)
    Extreme Java G22.3033-007 Session 5 - Main Theme Java Core Technologies (Part III) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda • Summary of Previous Session / Epilogue • Java Media APIs •Java 2D API • Java Media Framework • XBeans and Visual XBeans •JNI • Java Generative Programming Technology • Language Features •Threads • Readings 2 1 Summary of Previous Session • Summary of Previous Session • Java AWT and Swing components • Drag and Drop • Graphics and Multimedia Components (JavaMedia) • JavaBeans • Readings • Class Project & Assignment #2b 3 Java Technologies/Features in Scope • Technologies: • Collections Framework • Input Method Framework • Swing • Drag and Drop • JavaBeans •JNI • Security • Language Features: • Threads • Assertions 4 2 Part I Session 4 Epilogue 5 Drag and Drop (http://java.sun.com/j2se/1.4/docs/guide/swing/1.4/dnd.html) • See Session 4 Handout on Drag and Drop Data Transfer • Adding Drag and Drop to a JTree • In J2SE 1.4, JTree supports Drag but developers must implement and install a custom TransferHandler to fully support imports of data on Drop targets • http://www.javaworld.com/javaworld/javatips/jw-javatip97.html • http://www.javaworld.com/javaworld/javatips/jw-javatip114.html • http://sourceforge.net/projects/ijtree/ 6 3 JavaBeans and JAF (http://java.sun.com/j2se/1.4/docs/guide/beans/changes14.html) • See Session 4 Handout on Component Modeling with JavaBeans • Download the BeanBuilder • http://java.sun.com/products/javabeans/beanbuilder/index.html
    [Show full text]
  • Configuring the Codewarrior Tools to Debug a BSC9131RDB Board
    Freescale Semiconductor Document Number: AN4384 Application Note Rev. 0, 07/2012 Configuring the CodeWarrior Tools to Debug a BSC9131RDB Board by Freescale Semiconductor, Inc. Austin, TX This application note describes how to configure Contents the Freescale CodeWarrior tools to support 1 BSC9131 overview .................................................... 2 developing and debugging of embedded 2 Debugger configuration strategies ............................. 4 3 BSC9131RDB board setup ........................................ 6 software on the BSC9131RDB board. 4 Two-TAP connection scheme .................................... 7 5 Revision history ........................................................ 33 Because the QorIQ Qonverge BSC9131 Appendix A How to Disable the SC3850 Caches ....... 34 processor contains two disparate processor Appendix B DSP Debugging with a BSP Present ....... 38 Appendix C Ethernet TAP Run Controller Options ..... 39 cores, writing software for the part requires two different sets of CodeWarrior tools: one to manage the DSP core, and another to manage the system core. Care must be taken to ensure that the two sets of tools do not interact with each other. Both the proper configuration sequences and the potential pitfalls are described here. This application note assumes the use of CodeWarrior for StarCore DSPs v10.2.10 or later, and CodeWarrior for Power Architecture® v10.1.2 or later. © 2012 Freescale Semiconductor, Inc. 1 BSC9131 overview The Freescale QorIQ Qonverge BSC9131 contains two processor cores, each of whose microarchitecture is optimized for a specific purpose: StarCore SC3850 DSP core implements high-throughput signal processing functions Power Architecture e500 core implements high-volume network functions These cores manage a number of powerful peripherals, all of which are interconnected through a low- latency switching fabric (Figure 1). However, for debugging setup purposes, only the cores are considered in this application note.
    [Show full text]
  • Codewarrior™ Build Tools Reference for Freescale™ 56800/E Hybrid Controllers
    Freescale Semiconductor, Inc. CodeWarrior™ Build Tools Reference for Freescale™ 56800/E Hybrid Controllers Revised 28 October 2004 For More Information: www.freescale.com Freescale Semiconductor, Inc. Metrowerks and the Metrowerks logo are registered trademarks of Metrowerks Corporation in the United States and/ or other countries. CodeWarrior is a trademark or registered trademark of Metrowerks Corporation in the United States and/or other countries. All other trade names and trademarks are the property of their respective owners. Copyright © 2004 Metrowerks Corporation. ALL RIGHTS RESERVED. No portion of this document may be reproduced or transmitted in any form or by any means, electronic or me- chanical, without prior written permission from Metrowerks. Use of this document and related materials are governed by the license agreement that accompanied the product to which this manual pertains. This document may be printed for non-commercial personal use only in accordance with the aforementioned license agree- ment. If you do not have a copy of the license agreement, contact your Metrowerks representative or call 1-800- 377-5416 (if outside the U.S., call +1-512-996-5300). Metrowerks reserves the right to make changes to any product described or referred to in this document without further notice. Metrowerks makes no warranty, representation or guarantee regarding the merchantability or fitness of its prod- ucts for any particular purpose, nor does Metrowerks assume any liability arising out of the application or use of any product
    [Show full text]
  • Ultimate++ Forum
    Subject: Porting (Mac OS X) and "reference application" idea Posted by mirek on Thu, 17 May 2007 15:35:21 GMT View Forum Message <> Reply to Message I have an idea how to speed-up the porting (MacOS X now, be it is general). The most time consuming part of problem is to find out all the information about implementing required things on target platform, something that developer that knows the platform would find primitive. OTOH, target platform guru's are unlikely to know about U++ implementation details. So my idea is to create "reference application" that will contain all the function for minimal (and perhaps later, advanced) target platform support. Target platform guru will reimplement this application (using the most straighforward way) and submit the code, which will serve as great boost to development speed (sort of U++ oriented knowledge base). Thoughts? Mirek Subject: Re: Porting (Mac OS X) and "reference application" idea Posted by captainc on Sun, 14 Sep 2008 13:08:14 GMT View Forum Message <> Reply to Message luzr wrote on Thu, 17 May 2007 11:35I have an idea how to speed-up the porting (MacOS X now, be it is general). The most time consuming part of problem is to find out all the information about implementing required things on target platform, something that developer that knows the platform would find primitive. OTOH, target platform guru's are unlikely to know about U++ implementation details. So my idea is to create "reference application" that will contain all the function for minimal (and perhaps later, advanced) target platform support.
    [Show full text]
  • Xcode Chapter.Indd
    Chapter 1 Xcode Many computer books use Chapter 1 to cover introductory material. Xcode Tools Sensei is not one of those books. I want you to start learning immediately. After reading this chapter you’ll know how to create a project, add files to your project, edit source code, model data, read developer documentation, configure the compiler, and build your project into a working Mac OS X program. Creating a Project Every program you write with Xcode requires a project, no matter how small the program is. An Xcode project contains your program’s source code files and other files Xcode needs to build a working program, such as Interface Builder nib files. To create an Xcode project, choose File > New Project, and the Project Assistant window opens. Xcode has the following project categories: n Action n Application n Audio Units n Bundle n Command-Line Utility n Dynamic Library n External Build System n Framework n J2EE n Java n Kernel Extension n Standard Apple Plug-Ins n Static Library I will go into greater detail on the types of projects shortly, but most of you will be making application projects. After choosing the type of project you want to make, click the Next button. Tell Xcode the name of your project and where you want to store it, then click the Finish button. Congratulations! You’ve created an Xcode project. What Xcode includes in a project depends on the type of project you create. Xcode includes the following files for a Cocoa application: n An Objective C source code file, main.m.
    [Show full text]
  • Codewarrior® Palm OS 2.0 Tutorial for Windows
    CodeWarrior® Palm OS 2.0 Tutorial for Windows Because of last-minute changes to CodeWarrior, some of the information in this manual may be inaccurate. Please read the Release Notes on the CodeWarrior CD for the latest up-to-date information. Revised: 98/01/19 map Metrowerks CodeWarrior copyright ©1993Ð1998 by Metrowerks Inc. and its licensors. All rights reserved. Documentation stored on the compact disk(s) may be printed by licensee for personal use. Except for the foregoing, no part of this documentation may be reproduced or trans- mitted in any form by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission in writing from Metrowerks Inc. Metrowerks, the Metrowerks logo, CodeWarrior, and Software at Work are registered trademarks of Metrowerks Inc. PowerPlant and PowerPlant Constructor are trademarks of Metrowerks Inc. All other trademarks and registered trademarks are the property of their respective owners. ALL SOFTWARE AND DOCUMENTATION ON THE COMPACT DISK(S) ARE SUB- JECT TO THE LICENSE AGREEMENT IN THE CD BOOKLET. How to Contact Metrowerks: U.S.A. and international Metrowerks Corporation P.O. Box 334 Austin, TX 78758 U.S.A. Canada Metrowerks Inc. 1500 du College, Suite 300 Ville St-Laurent, QC Canada H4L 5G6 Ordering Voice: (800) 377Ð5416 Fax: (512) 873Ð4901 World Wide Web http://www.metrowerks.com Registration information [email protected] Technical support [email protected] Sales, marketing, & licensing [email protected] CompuServe goto Metrowerks Table of Contents Table of Contents . iii Introduction . 13 System Requirements for Macintosh Users . 14 Hardware Requirements . 14 Software Requirements .
    [Show full text]
  • Macintosh Library Modules Release 2.4.1
    Macintosh Library Modules Release 2.4.1 Guido van Rossum Fred L. Drake, Jr., editor 30 March 2005 Python Software Foundation Email: [email protected] Copyright c 2001-2004 Python Software Foundation. All rights reserved. Copyright c 2000 BeOpen.com. All rights reserved. Copyright c 1995-2000 Corporation for National Research Initiatives. All rights reserved. Copyright c 1991-1995 Stichting Mathematisch Centrum. All rights reserved. See the end of this document for complete license and permissions information. Abstract This library reference manual documents Python’s extensions for the Macintosh. It should be used in conjunction with the Python Library Reference, which documents the standard library and built-in types. This manual assumes basic knowledge about the Python language. For an informal introduction to Python, see the Python Tutorial; the Python Reference Manual remains the highest authority on syntactic and semantic questions. Finally, the manual entitled Extending and Embedding the Python Interpreter describes how to add new extensions to Python and how to embed it in other applications. CONTENTS 1 Using Python on a Macintosh 1 1.1 Getting and Installing MacPython .................................. 1 1.2 The IDE ............................................... 2 1.3 The Package Manager ........................................ 3 2 MacPython Modules 5 2.1 macpath — MacOS path manipulation functions ......................... 5 2.2 macfs — Various file system services ............................... 5 2.3 ic — Access to Internet Config ................................... 8 2.4 MacOS — Access to Mac OS interpreter features .......................... 9 2.5 macostools — Convenience routines for file manipulation ................... 10 2.6 findertools — The finder’s Apple Events interface ...................... 10 2.7 EasyDialogs — Basic Macintosh dialogs ............................ 11 2.8 FrameWork — Interactive application framework ........................
    [Show full text]
  • Engineering 101 HOW to Work Remotely from Windows
    Engineering 101 HOW TO Work Remotely from Windows If you wish to work on your Eng101 assignments from outside a CAEN lab such as your home computer or an ITD lab computer, you can do so in three different ways ¾ In terminal emulation mode you use your local computer as a text-only terminal to access the CAEN computer remotely. All editing and compiling is done on the CAEN computers. This ensures that your final code is compatible with the system on which we will compile and execute it when grading. ¾ In file transfer mode you use your local computer to edit text files and compile the code. Then when you are done you transfer your program to your Eng101 directory. It is very important if you use this method to test that your program is compatible with the CAEN compiler by compiling it remotely on the CAEN computers as well. ¾ In X server mode you connect much as you would in terminal emulation mode, but you open a connection via which both text and graphics can be displayed on your computer. This will allow you to use editors with graphical user interfaces (GUI's) as well as text- based resources. Each method differs in the ease of setup and the convenience of use. These methods also depend on your internet connection speed (or bandwidth) and the availability of software. If you are in a CAEN lab and you are working in Windows on a PC you should simply reboot your computer into Linux, otherwise proceed with this document. We will assume that you have an internet connection on your home computer.
    [Show full text]
  • Using Codewarrior for Macintosh
    CS106B Handout #5M Winter 04-05 January 7, 2005 Using CodeWarrior for Macintosh In CS106, you have the option of writing your programs on the Mac or PC. For the Macintosh environment, you will write your programs using the C++ compiler by Metrowerks called CodeWarrior Professional. The current version of CodeWarrior, Pro 8, has been site-licensed to Stanford and can be downloaded from the Software page on the course web site. CodeWarrior provides a very nice editing environment and debugger, and it is the state-of-the-art C++ compiler for the Mac. One of the consequences of using a state-of-the-art compiler is that the system requirements for CodeWarrior Pro 8 are somewhat high – it requires Mac OS 9.2.2 or later, 700MB of hard drive space, and at least 64 MB of RAM. You also have to have CarbonLib 1.5, since Pro 8 is written for Mac OS X as well. If you have OS X, then you need 128MB of RAM to run CodeWarrior Pro 8, and you don’t need CarbonLib as this is already part of OS X. You can download CarbonLib from Apple—more on this later. Using CodeWarrior at a cluster CodeWarrior is available for use in the Lair (the Tresidder Macintosh cluster), on the Macs in Meyer library, and in the residential computer clusters. Often it will already be in the Applications folder on the machine’s hard disk. If there is a folder there named something like Metrowerks CodeWarrior 8, then the application can be found within that folder.
    [Show full text]