Software:CodeWarrior

From HandWiki
Revision as of 10:20, 9 February 2024 by JOpenQuest (talk | contribs) (linkage)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Short description: Integrated software development environment
CodeWarrior
Developer(s)Metrowerks
Initial releaseDecember 23, 1993; 30 years ago (1993-12-23)
Operating systemClassic Mac OS, Mac OS X, BeOS, Windows, Linux, Solaris
TypeSoftware development tool
LicenseProprietary

CodeWarrior is an integrated development environment (IDE) published by NXP Semiconductors for editing, compiling, and debugging software for several microcontrollers and microprocessors (Freescale ColdFire, ColdFire+, Kinetis, Qorivva, PX, Freescale RS08, Freescale S08, and S12Z) and digital signal controllers (DSC MC56F80X and MC5680XX) used in embedded systems.

The system was developed by Metrowerks on the Macintosh, and was among the first development systems on that platform to cleanly support both the existing Motorola 68k and the PowerPC (PPC) instruction set architectures. During Apple's transition to PowerPC, CodeWarrior quickly became the de facto standard development system for the Mac, rapidly displacing Symantec's THINK C and Apple's own Macintosh Programmer's Workshop. Apple's purchase of NeXT in 1996 led to a decline in CodeWarrior's relevance as Mac programming moved to the NeXT platform's own developer tools: Interface Builder and Project Builder, which were built on top of the GNU Compiler Collection.

Metrowerks responded by porting CodeWarrior to Microsoft Windows and introducing compilers for a wider variety of platforms. It became a major part of the software stack for Motorola's varied lines of microcontrollers, and eventually led to them purchasing Metrowerks in 1999. It was widely used on most platforms based on PPC or other Motorola processors, as well as many games consoles. The product moved to Freescale Semiconductor when that company formed in 2004, and then to NXP when they purchased Freescale in 2015.

Originally a single integrated product, now known as the "Classic IDE", the IDE was later replaced with Eclipse IDE. The current versions are 6.3 of the Classic IDE,[1] and 11.0 for the Eclipse IDE.[2] Languages supported are C, C++, and assembly language.

History

Origins

In October 1992, John McEnerney, formerly development manager of Symantec's Language Products Group, left the company to work on his own on a PowerPC product, initially thinking about a Pascal compiler. Rich Siegel, author of BBEdit, heard that McEnerney had left Symantec and told Greg Galanos of Metrowerks in Montreal . Galanos phoned McEnerney and asked him to "describe your dream job". McEnerney said he wanted to write a code generator for the new PowerPC (PPC) chip that Apple had announced they would be using in the future.[3]

Metrowerks had already developed Pascal and Modula-II compilers, originally for the Atari ST, but later ported to a number of contemporary machines including the Mac. They flew McEnerney to Montreal to meet with Galanos and his partner Jean Belanger. They felt that there was a huge opportunity for a new toolchain on the PPC, combining their compilers with a new code PPC code generator written by McEnerney. They felt could get to market more rapidly than Symantec, the leading supplier of development systems on the Mac. Symantec was nowhere near the release of their products for PPC, and Apple was using updated versions of their own Macintosh Programmers Workshop (MPW) for development on the PPC, a product that had been ignored for years. McEnerney was interested, but unimpressed with their compilers, and little came of this initial contact.[3]

Around the same time, Andreas Hommel was in university in Germany completing a MS in computer science. He developed an interest in writing computer games in C, but found that existing compilers generated poor-quality code. Over a series of years he developed his own C compiler for the 68k along with a simple integrated development environment (IDE). When he completed university he was offered a job in Hamburg but decided to try to see if there was a market for his compiler. A few months later he received a call from Galanos. After several transatlantic phone calls, Galanos invited Hommel to come to Montreal and discuss working with them.[4]

Development

In February 1993, Galanos called McEnerney and asked if they could meet in Palo Alto so McEnerney could review a new C compiler Metrowerks had acquired. McEnerney was extremely impressed; the system looked like early versions of Think C, and was very fast. Describing it as "a diamond in the rough", McEnerney signed a contract with Metrowerks within hours. Hommel would extend his C compiler to a full C++ implementation while disentangling it from the code generation stage. McEnerney would write a new PPC code generator that would be driven by Hommel's compiler. Hommel's existing 68K code generator would be used for that platform, slightly modified to support Pascal as well. Berardino Baratta and Marcel Achim in Montreal would continue developing the IDE and develop a Pascal compiler running on the same code generators.[3]

Examining the new system, McEnerney decided to take an entirely new approach to code generation. Typical compilers of the era would repeatedly examine their intermediate representation (IR) producing more and more optimized versions of the code until they finally converted it to machine instructions. This approach was less important for RISC platforms, as the instruction set architecture was much simpler and there was far less work involved in deciding which particular type of instruction to use for a given task. Instead, McEnerney's new code generator took the initial IR and converted that directly to PPC code.[3]

The major change was to implement Chaitin's algorithm for register use. This system, introduced in 1982, was a landmark development in compiler technique. It allowed a code generator to map local variables to processor registers with very high efficiency. On a machine that relied on register use for performance, which is one of the primary concepts of RISC processors, this technique can lead to huge improvements. The downside is that it is expensive to calculate the results, being an O(N2) process.[3]

To help develop the PPC compiler, Apple's Jordan Mattson sent McEnerney one of their RS/6000 systems. By August 1993 the basic system was running. McEnerney got a phone call from a former Symantec colleague, Dan Podwall, who was looking for work at Metrowerks. Galanos called Podwall, who was immediately hired to write a debugger, completed in only four weeks.[3]

A prototype Power Macintosh machine was sent to the company in September 1993. At the time, the main IDE and compiler toolchain was still running on the 68k machines, producing PPC binaries that were then moved to the prototype and debugged. This allowed them to quickly port the system to the PPC, and by December the entire system was ready for production.[3]

Release

The system was launched as CodeWarrior at the MacWorld Expo in January 1994. The Power Macs were slated to be launched that month as well, but a series of delays forced this to be set off until the official launch of the Power Mac machines on 14 March.[3]

At the time, both Apple's MPW and Symantec's Think C ran only on 68k machines, and only MPW was able to generate PPC binaries. Running natively on the PPC, and based on code dedicated to the platform, CodeWarrior offered dramatically higher performance, while allowing one to develop and debug on a single machine. Sales of other development systems ended practically overnight. Symantec, who had owned the Mac development market since 1986, did not release a native PPC version until late March 1995. By this time, several major Mac software vendors had moved to CodeWarrior and Symantec was never able to re-establish any sort of marketshare on the Mac.[5]

CodeWarrior was a key factor in the success of Apple's transition of its machine architecture from 68K processors to PowerPC because it provided a complete, solid PowerPC compiler when the competition (Apple's MPW tools and Symantec C++) was mostly incomplete or late to the market.[5] Metrowerks also made it easy to generate fat binaries, which included both 68K and PowerPC code.

Java support in CodeWarrior for Macintosh was announced for May 1996, slated for CodeWarrior 9.[6] Metrowerks took the approach to add Java tools support in CodeWarrior, including debugging, rather than write a new IDE.[7]

Moving to multiple platforms

In 1997, Apple purchased NeXT in order to use their operating system, OpenStep, as the basis for future Mac products. OpenStep was based around the concept of the entire operating system and all of its applications being built using an internal development system. This was, in turn, based on the GNU Compiler Collection (GCC). While CodeWarrior would still be important for developers writing "classic" Mac applications on the platform, there was a clear time frame after which development would primarily be on

In August 1996, Metrowerks announced CodeWarrior for BeBox,[8] a BeOS version of the IDE named BeIDE supplementing the PowerPC compiler that was already available to BeOS software developers.

Motorola era

After Metrowerks was acquired by Motorola in 1999, the company concentrated on embedded applications, devoting a smaller fraction of their efforts to compilers for desktop computers. On 29 July 2005, they announced that CodeWarrior for Mac would be discontinued after the next release, CodeWarrior Pro 10. Metrowerks indicated that revenue share of the product fell from 22% to 5% in the last four years and the effort by the company to concentrate on the embedded development market. The demand for CodeWarrior had presumably fallen during the time Apple began distributing Xcode (its own software development kit for OS X) for free.[9] In addition, Apple's switch to Intel chips left Metrowerks without an obvious product as they had sold their Intel compiler technology to Nokia earlier in 2005.[citation needed]

During its heyday, the product was known for its rapid release cycle, with multiple revisions every year, and for its quirky advertising campaign. Their "geekware" shirts were featured in the fashion pages of The New York Times .[10]

Old versions

CodeWarrior Professional Release 1

Prior to the acquisition of the product by Freescale, versions existed targeting Macintosh, Microsoft Windows, Linux, Solaris, PlayStation, PlayStation 2, GameCube, Nintendo DS, Wii,[11] Dreamcast, SuperH, M·CORE, Palm OS,[12] Symbian OS, and BeOS.[8]

Metrowerks versions of CodeWarrior also included Pascal, Object Pascal, Objective-C, and Java compilers.

Older versions of CodeWarrior can be used to develop on classic Mac OS. Classilla is built with Metrowerks CodeWarrior 7.1.[13]

Release name Editions Release date Notes[14]
CodeWarrior DR/1 Gold, Silver, Bronze 1993-12-23 Bronze supports 68k, Silver supports PPC, Gold supports 68k and PPC
CodeWarrior DR/2 Gold, Silver, Bronze 1994-03-11
CodeWarrior DR/3 Gold, Silver, Bronze 1994-05-05
CodeWarrior 4 Gold, Silver, Bronze 1994-06-26
CodeWarrior 5 Gold, Bronze 1994-12-15
CodeWarrior 6 Gold, Bronze 1995-05-03
CodeWarrior 7 Gold, Bronze 1995-09-05
CodeWarrior 8 Gold, Bronze 1996-01-04
CodeWarrior 9 Gold 1996-05-11
CodeWarrior 10 Gold 1996-09-09
CodeWarrior 11 Gold 1996-12-31
CodeWarrior Pro 1 1997-06-04 Mac and Windows bundled
CodeWarrior Pro 2 1997-10-23 First version to target Mach-O and Yellow Box on Rhapsody with support for Objective-C[15]
CodeWarrior Pro 3 1998-04-07
CodeWarrior Pro 4 1998-09-10 Last to include Pascal[16]

Last to run on 68k[17]

CodeWarrior Pro 5 Mac, Windows 1999-06-18
CodeWarrior Pro 6 Mac, Windows 2000-09-09 Last to support 68k compiling[16][18] Pre-release support of Mach-O, and use Aqua user interface on Mac OS X.[19]
CodeWarrior Pro 7 Mac, Windows 2001 First to run natively in Mac OS X and target Mach-O by default[18]
CodeWarrior Pro 8 Mac, Windows 2002 Last to run on Classic Mac OS
CodeWarrior 9 Mac 2003
CodeWarrior 10 Windows 2004

Origin of the name

During the 1990s, Apple Computer released a monthly series of developer CD-ROMs containing resources for programming the Macintosh. These CDs were, in the early days, whimsically titled using punning references to various movies but with a coding twist; for example, "The Hexorcist" (The Exorcist), "Lord of the Files" (Lord of the Flies), "Gorillas in the Disc" (Gorillas in the Mist), etc.[20]

One of these, volume 9, was titled "Code Warrior", referring to the movie The Road Warrior. Later Apple dropped the whimsical titling in favor of a more sober "Developer CD series". Coincidentally the Metrowerks founder, Greg Galanos, an Australian, was also inspired by the movie and proposed the CodeWarrior name. Metrowerks subsequently used the name for their new developer product.

CodeWarrior CD packaging was very much in the tradition of the Apple developer CDs, featuring slogans such as "Blood, Sweat, and Code" and "Veni, Vidi, Codi" in prominent lettering. Competing products such as Symantec's THINK C were more conventionally marketed.

CodeWarrior Latitude

Metrowerks foresaw as it had with the transition to PowerPC, a need to provide a must have developer tool to help developers transition from MacOS software to Apple's future operating system, codenamed Rhapsody.[21]

In 1997, Metrowerks acquired the principal assets of The Latitude Group Inc. from David Hempling and his partners. Latitude was a software compatibility layer used to port Macintosh applications to the NeXT Computer and other UNIX systems.[22]

Latitude presented itself as a library that implemented the Macintosh System 7 API in the same way that Lee Lorenzen's Altura Mac2Win software as well as Apple's own Quicktime for Windows SDK allowed Macintosh applications to be recompiled for Windows with minimal modifications. Latitude had previously been used successfully by Adobe to port Photoshop and Premiere to Silicon Graphics and Solaris workstations.[23]

Metrowerks rebranded Latitude as CodeWarrior Latitude,[24] updated it for Rhapsody starting with Developer Preview 1 and then marketed it to Macintosh developers as a separate product for $399, alongside CodeWarrior Professional.[25][26]

Latitude Developer Release 1 (DR1) was previewed at WWDC 1997 in the CodeWarrior Lounge. Latitude DR2 was released on Oct 27, 1997 and won an Eddy Award at the 1998 Macworld for Best Tool for New Technologies beating out Joy from AAA+ Software F&E and Visual Cafe for Macintosh 1.0.2 by Symantec.[27]

At the time, Steve Jobs was heavily promoting the OPENSTEP API (renamed Yellow Box) in order to access the new features of the operating system. For C/C++/Pascal Macintosh developers, this presented a substantial hurdle because it was markedly different from the classic MacOS API that ran inside Blue Box and was Objective-C based. Latitude was for a short time coined as the "Green Box"[28] for obvious reasons and appeared to be another hit for Metrowerks and further solidify its dominance in the Macintosh developer tools market but Apple secretly had plans of its own.

CodeWarrior's IDE for Rhapsody and CodeWarrior Latitude were both demonstrated at Worldwide Developers Conference in 1998 in the third party developer pavilion but were quietly discontinued at the show following Steve Jobs keynote address. Apple's announcement of its forthcoming Carbon API (codenamed "Ivory Tower") to appeal to developers who required a practical way to transition to the new operating system eliminated the need for any third-party solutions.[29]

Metrowerks used Latitude internally to port CodeWarrior to run on Red Hat and SuSE Linux for commercial sale and additionally to Solaris under contract from Sun Microsystems. Both products utilized gcc command line compilers rather than Metrowerks own compiler technologies to promote adoption within the UNIX developer community.

The final version of Latitude supported Solaris 2.3, SGI Irix 5.2 and Rhapsody DP2, dropping HP-UX support.

References

  1. ↑ "CodeWarrior for Microcontrollers (Classic IDE)". https://www.nxp.com/support/developer-resources/software-development-tools/codewarrior-development-tools/codewarrior-legacy/codewarrior-development-studios/codewarrior-for-microcontrollers/codewarrior-for-microcontrollers-classic-ide-rs08-hcs08-coldfire-v1-v6.3:CW-MICROCONTROLLERS. 
  2. ↑ "CodeWarrior for Microcontrollers (Eclipse IDE)". https://www.nxp.com/support/developer-resources/software-development-tools/codewarrior-development-tools/codewarrior-legacy/codewarrior-development-studios/codewarrior-for-microcontrollers/codewarrior-for-mcus-eclipse-ide-coldfire-56800-e-dsc-kinetis-qorivva-56xx-rs08-s08-s12z-v11.0:CW-MCU10. 
  3. ↑ 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 Mark 1996a.
  4. ↑ Mark 1996b.
  5. ↑ 5.0 5.1 Seiter, Charles (July 1995). "A crucial compiler ships". Macworld 12 (7): 41. https://archive.org/details/eu_Macworld-1995-07-INT_OCR/page/n44/mode/1up. 
  6. ↑ Kawakami, John (January 1996). "Yet Another Platform for CodeWarrior: Java". MacTech 12 (1): 98. http://preserve.mactech.com/articles/mactech/Vol.12/12.01/Jan96Newsbits/index.html. 
  7. ↑ Sheets, Steve (May 1998). "Java Development Environments". MacTech 14 (5): 20. http://preserve.mactech.com/articles/mactech/Vol.14/14.05/JavaDevEnvironments/index.html. 
  8. ↑ 8.0 8.1 "Pipeline". InfoWorld 18 (33): 35. 12 August 1996. https://books.google.com/books?id=Pj0EAAAAMBAJ&pg=PA35. 
  9. ↑ Handy, Alex (15 August 2005). "Metrowerks plans to ax CodeWarrior for Macintosh". SD Times (132): 1. https://archive.org/details/sdtimes132/mode/1up. 
  10. ↑ "FRONTIERS OF MARKETING; Selling Geek Chic". The New York Times. 1995-02-12. https://www.nytimes.com/1995/02/12/magazine/sunday-february-12-1995-frontiers-of-marketing-selling-geek-chic.html. 
  11. ↑ Carless, Simon (2006-05-09). "CodeWarrior Named Official Toolset For Nintendo Wii". Gamasutra. http://www.gamasutra.com/php-bin/news_index.php?story=9243. 
  12. ↑ Mark, Dave; Cloninger, Eric (March 1998). "CodeWarrior for PalmPilot". MacTech 14 (3): 49–52. http://preserve.mactech.com/articles/mactech/Vol.14/14.03/Mar98FactoryFloor/index.html. 
  13. ↑ "Classilla: HowToBuild". http://code.google.com/p/classilla/wiki/HowToBuild. 
  14. ↑ "CodeWarrior Version History". https://groups.google.com/forum/#!topic/macos9/-hOUjohAkis. 
  15. ↑ Mark, Dave (October 1997). "A CodeWarrior Rhapsody Update: Part One". MacTech 13 (10): 37–40. http://preserve.mactech.com/articles/mactech/Vol.13/13.10/Oct97FactoryFloor/index.html. Retrieved 19 February 2022. 
  16. ↑ 16.0 16.1 Atwell, Richard (July 2000). "Arnold goes to WWDC". MacTech 16 (6): 110–111. http://preserve.mactech.com/articles/mactech/Vol.16/16.07/Jul00FactoryFloor/index.html. Retrieved 19 February 2022. 
  17. ↑ Cook, David. "Metrowerks CodeWarrior Best Version and Updates". https://68kmla.org/bb/index.php?attachments/codewarrior-pro-5-article-png.47396/. 
  18. ↑ 18.0 18.1 Atwell, Richard (June 2001). "The Road from Rhapsody". MacTech 17 (6): 20–32. http://preserve.mactech.com/articles/mactech/Vol.17/17.06/Jun01FactoryFloor/index.html. Retrieved 19 February 2022. 
  19. ↑ Hayden, Joe; Henderson, Matt (May 2000). "CodeWarrior for Mac OS X". MacTech 16 (5): 64–65. http://preserve.mactech.com/articles/mactech/Vol.16/16.05/May00FactoryFloor/index.html. Retrieved 19 February 2022. 
  20. ↑ Every, David K. (1999). "Apple Developer CD Codenames: Puns, fun, and satire". MacKiDo. http://www.mackido.com/CodeNames/DeveloperCDs.html. 
  21. ↑ Mark, Dave (May 1997). "Greg Galanos and the Mac Developer's Roadmap". MacTech 13 (5). http://preserve.mactech.com/articles/mactech/Vol.13/13.05/May97FactoryFloor/index.html. 
  22. ↑ Mark, Dave (June 1997). "David Hempling and the Latitude Porting Libraries". MacTech 13 (6). http://preserve.mactech.com/articles/mactech/Vol.13/13.06/Jun97FactoryFloor/index.html. 
  23. ↑ Mark, Dave (December 1997). "Sean Parent: The Photoshop Development Process". MacTech 13 (12): 42–44. https://archive.org/details/eu_MacTech-1997-12_OCR/page/n43/mode/1up. 
  24. ↑ "[MD1 Metrowerks Acquires Latitude"]. 27 January 1997. https://www.mactech.com/1997/01/27/md1-metrowerks-acquires-latitude/. 
  25. ↑ "Developer Depot". MacTech: 2. January 1998. https://archive.org/details/eu_MacTech-1998-01_OCR/page/n91/mode/1up. 
  26. ↑ Mark, Dave (January 1998). "CodeWarrior Latitude: Porting Your Apps to Rhapsody". MacTech 14 (1). http://preserve.mactech.com/articles/mactech/Vol.14/14.01/Jan98FactoryFloor/index.html. 
  27. ↑ "[MD1 1998 Eddy Tool Awards Winners"]. MacTech. 6 January 1998. https://www.mactech.com/1998/01/07/md1-1998-eddy-award-winners/amp/. 
  28. ↑ "Metrowerks Green Box to plow Mac path to OpenStep APIs". InfoWorld. 25 April 1997. http://www.xent.com/FoRK-archive/spring97/0409.html. 
  29. ↑ Walsh, Jeff (12 May 1997). "Apple to woo developers with Rhapsody tools". InfoWorld 19 (19): 15. https://books.google.com/books?id=9zsEAAAAMBAJ&pg=PA15. 

Bibliography

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Software:CodeWarrior&oldid=3455917"