Goodbye (MEZZANINE) Mac OS

This document shows how to create and download project files for use with the Mac tools from the command line.

  1. Shipping offer valid on orders shipped to US addresses. Free Standard Shipping and Returns. with any purchase. Upgrade to 2nd Day Shipping for $5.00 or Overnight Shipping for $10.00. Standard Shipping is always complimentary on MAC Gift Cards. No offer code necessary. Shipping offer not applicable to Pro members.
  2. Mezzanine is a powerful open source content management platform built using the Django framework. In many ways it is like many other content management tools, offering an intuitive interface for managing all of your content. But Mezzanine is different in that it provides most of its functionality by default.

Before following these instructions, you should have already downloaded and installed the CLion software (if you haven't, go back and do so).

Section 1) Testing the Mac and Clang

And started to feel inspired by the idea of using and open source operating system. (Windows and MacOS are closed source operating systems, Linux is the most well known open source operating system.) So, I decided to use Virtual Box on my mac to run a Linux distribution called “Elementary OS”, and the experience sucked.

In this section you will create and run a trivial C++ project/program (including editing it, and seeing how syntax errors are reported).

First, we will perform a one-time only setup.

  1. Start a Terminal by clickich the (Mac Terminal icon) on the Dock.

    Perform the following actions in your come directory (mine is Richards-MacBook-Air: ~richardepattis).

    1. Use any editor (vi is automatically available on the Mac; other editors can be downloaded) to update your ~/.bash_profile file to contain the following line at the end (or put it after the other PATH settings in that file; e.g., copy/paste it):
    2. Terminate the Terminal and start a new Terminal (which executes the ~/.bash_project file automatically).
    3. Type echo $PATH and ensure the path you added appears.

    Now we will create directories for use in ICS-46, and create a trivialtest project to ensure the required operations work correctly.

    1. Make an empty directory for all ICS-46 Projects (ics46projects) using the mkdir command.
    2. Connect to the ics46projects directory using the cd command.
    3. Make an empty directory for the Trivial Test Project (trivialtest) using the mkdir command.
    4. Connect to the trivialtest project directory using the cd command.
    5. Use any editor to create a main.cpp file that contains the following code (e.g., copy/paste it):
    6. Create a CMakeLists.txt file that contains the following code (e.g., copy/paste it):
    7. List the contents of the ics46project/trivialtest directory storing these two files, by using the ls command.
    8. Create the make files needed for this project, by using the cmake . command (remember, you will do this just the first time you use a project).
    9. List the contents of the ics46project/trivialtest directory storing the new files it creates (and the new CMakeFiles directory), by using the ls command.
    10. Build the trivialtest file needed to execute this program, by using the make command (you will do this each time that you modify a .cpp file in a project).
    11. List the contents of the ics46project/trivialtest directory storing the new file it creates, by using the ls command.
    12. Run the trivialtest executable file, by using the ./trivialtest command.

    The following ~/ics46projects/trivialtest Terminal window shows all these actions (D through O).

  2. Use the finder to navigate to the Macintosh HD/users/yourname/ics46projects/trivialtest directory.

    The following Finder should appear on your screen.

    You can use any combination of Mac OS and Terminal command lines to manipulate the files in this directory: whichever is simplest.

    It would also be useful to make an alias to this ics46projects folder and place it conveniently on the desktop, so you can easliy reach the projects you are working on.

  3. Edit, rebuild, and rerun the main.cpp program,
    • Use an editor to change the cout to print 'Goodbye, World!'.
    • Show the main.cpp program file, by using the more command.
    • Rebuild the trivialtest file using the same make command. There is no reason to use the cmake command here: it must be used only if we change the CMakeLists.txt file.
    • Rerun the edited trivialtest file, by using the ./trivialtest command.

    The following ~/ics46projects/trivialtest Terminal window shows all these actions.

  4. Create a syntax error (remove the ; at the end of the cout line), and then follow the rebuilding/rerunning steps above The following ~/ics46projects/trivialtest Terminal window shows all these actions.

    The failed results of attempting to rebuild the program appear after the make command. In this case, the Clang compiler accurately indicates the source of the error. I have lengthened the window so as not cause lines to wrap.

We will now continue by learning how to download a project and run it. During the quarter, you will be asked to do this for all programming assignments and many quizzes.

Section 2) Testing Downloadable Projects with the Course Libraries

In this section you will download the course libraries and then download/build/run a project that contains various programs that use these libraries.

  1. If you have not already done so, make an alias to the folder Macintosh HD/users/yourname/ics46projects named named ics46projects and place it on your desktop.
  2. Download and unzip the file template; Copy its three directories (courselib, googletestlib, and test_all_data_types) into the directory that ics46projects aliases; it should already contain the trivialtest directory, created by the operations above.

    Generally, whenever you download projects, you will unzip them and then copy their directories into the directory that ics46projects shortcuts.

    The following ~/ics46projects Terminal window lists these four directories.

  3. Connect to the test_all_data_types directory, by using the cd command. Hint: type only cd te and then press the tab key and Terminal should complete the name of this directory; generally using tab for directory/file name completion can drastically reduce your typing in Terminal.

    List the contents of the ics46project/test_all_data_types directory, by using the ls command. Notice that this project folder contiains various .cpp files and a CMakeLists.txt file

    The following ~/ics46projects/test_all_data_types Terminal window shows all these actions.

  4. Edit the driver.cpp file by uncommenting lines 30-35, so they appear as follows
  5. Build and run the main.cpp program,
    • Create the make files needed for this project, by using the cmake . command (recall you will do this just the first time you use a project).
    • Build the test_all_data_types file needed to execute this program, by using the make command (you will do this each time that you modify a .cpp file in a project).
    • Run the test_all_data_types executable file, by using the ./test_all_data_types command (remember to use command-completion to reduce your typing: but since many file names start with test_ you will have to type test_d (a unique prefix for the exe file) before pressing tab.

    The following ~/ics46projects/test_all_data_types Terminal window shows all these actions.

    Experiment with this driver by entering commands (and their arguments, when prompted) to better understand the set data type. You can enter the q command to terminate the driver, or you can type command-c to terminate the driver.

    I suggest that you try terminating the driver with a q command; then, rerun the program and terminate it with command-c.

  6. Using the ics46projects alias (you created in step 1), naviagate to the test_all_data_types project folder.

    The following window should appear on your screen.

  7. Double-click the test_all_data_types file to run this program in a Terminal window. The following Terminal window should appear on your screen.

    You can use all commands except the lf command, which is explained below. Then terminate the Terminal window.

  8. Find the input files directory in the test_all_data_types folder and copy all of its .txt data files up one level in the directory (the one that contains the test_all_data_types file).

    Then, run the program from a Terminal window (connnected to the test_all_data_types directory) issue the lf command (load from file); when prompted for the file name, just press the enter key to choose the default (loadset.txt).

    The following ~/ics46projects/test_all_data_types Terminal window shows all these actions.

    Note that because the directory name input files contains a space, it appears in double quotes ('input files') in this and most Terminal commands.

    IMPORTANT: If a program reads data files, the root directory for the specifying the files is the directory in which the executable file appears. It is simplest to copy all the data files into this directory. An alternative would be to leave the files in the input files directory, and enter their names like input files/loadset.txt (note no quotes are needed here: this is not a Terminal command).

    When you double-click an executable file to run it (as you did in Step 7) it does not run the program in the expected directory; so a program run this way cannot correctly read files in that directory!

  9. A typical project folder may have more than one .cpp file with a main function (as test_all_data_types has). Only one of these .cpp files can have its main function uncommented, otherwise the build will fail. When working on project, it is typical to
    1. Comment-out code in one .cpp file.
    2. Uncomment code in another .cpp file.
    3. Rebuild/Rerun the newly uncommented .cpp file.

    In the test_all_data_types project folder, the driver.cpp file has many main functions: we uncommented one (in step 4) to allow us to run the Set driver. If more than one main function is uncommented, attempting to build the code will result in the compiler specifying a redefinition of 'main' error.

    The test_all_data_types project folder also contains many .cpp files (their names all start with test) that each contain one main function (each is a Googletest for one data type). If more than one file contains a main function, attempting to build the code will result in the linker specifying a multiple definition of 'main' error.

    To switch this project from running the Set driver to the Set Googletest

    1. Edit the driver.cpp file and comment-out lines 30-35.
    2. Edit the test_set.cpp file and uncomment all its lines.
      Most program editors have a special command that allows commenting on selected lines to be toggeled.

    Rebuild/Rerun the newly uncommented .cpp file.

    The following ~/ics46projects/test_all_data_types Terminal window shows all these actions.

  10. IMPORTANT:When downloading all other project folders, Mac users must remove the following two lines from their CMakeLists.txt files.

    These two lines are necessary on PCs to find the Clang C and C++ compilers, but they are not necessary on Macs. I want to supply just one download, and it is easier for Mac users to remove these two lines than for PC users to add them.

    For this document, I provided a link to Mac-compatible CMakeLists.txt files, so this operation was unneeded.

We are now at the end of this handout. You will not need to repeat the first two sections during the course, but you will frequently download project folders and use them as demonstrated in section 2.

On May 6, 1998, Steve Jobs took the stage and announced the iMac G3, a consumer counterpart to the G3-powered PowerMac and PowerBook, the only remaining computers in Apple’s lineup after he had slashed all other machines, including the popular Performa line.

“The back of our computer,” he said, “looks better than the front of the other guys’. It looks like it’s from another planet. A good planet. A planet with better designers.”

August 1998: The Bondi-Colored Savior

The original iMac was introduced in 1998. In typical Jobs style, the keynote was something to behold.

“iMac comes from the marriage of the excitement of the Internet with the simplicity of Macintosh,” he said. Internet usage was “the number one use” consumers wanted, and the iMac was built to make that easy.

The iMac started the “i” revolution. Jobs said the i stood for:

  • internet
  • individual
  • instruct
  • inform
  • inspire
Goodbye (MEZZANINE) Mac OS

In addition to the consumer, Apple aimed the iMac at the education market, one of the company’s few remaining strongholds in the market at the time.

With the iMac, Apple returned to Jobs’ vision of an all-in-one computer, with all of the guts in the same case as the display. In a world of messy PCs, the iMac stood out as a simple, elegant computing solution.

While most of the computers at the time were beige boxes — including Apple’s other desktops — the iMac G3 was bondi blue, curvy and translucent.

The iMac G3 was built around its 1024×768, 15-inch CRT. The shape of the CRT defined the machine, with a slightly curved front.
The original iMac featured a 233 Mhz G3 processor, with a 512KB backside cache, coupled with 32 MB RAM, a 4 GB hard drive and a 24x tray-loading CD-ROM drive.

The big news with the original iMac, however, was the I/O. Apple stripped away all of its previously-used ports, including SCSI, ADB
Behind the door on the side, Apple had a 100 Mb Ethernet port, modem and up front an IR port.

…aaaand a pair of USB ports, which made the old-timers light their hairs on fire, but paved the way for easy, plug-n-play support for loads of peripherals like cameras, scanners, floppy drives and more.

January 1999: The Five Flavors

The original iMac shipped in August 1998. In January 1999, Apple offered the machine in five distinct colors. These machines shipped with a more powerful 266 Mhz G3 processor, coupled with a ATI Rage Pro Turbo graphics card with 6 MB SGRAM. The IR port was scrapped, as was the internal mezzanine slot.

The colors were as follows, clockwise:

  • Tangerine
  • Lime
  • Strawberry
  • Blueberry
  • Grape

These machines followed a mostly-silent “Rev. B” upgrade that happened just two months after the initial iMacs shipped. This upgrade featured Mac OS 8.5 and a ATI Rage Pro graphics card with 6 MB of SGRAM.

The Five Flavor iMacs sold for $100 less than Rev. A & B machines, at just $1199.

The Five Flavors got a spec bump to 333 Mhz in April 1999, and were replaced in October 1999, when Apple released the iMac (Slot Loading) line.

October 1999: Slot-Loading iMacs

In October 1999, Apple started shipping a slot-loading optical drive in the iMac, marking the start of the second batch of updates to the machine. These machines shipped with 8 MB of video RAM, thanks to a new ATI Rage 128 VR card. The Slot-Loading line also shipped with a base of 64 MB RAM, up for the first time since the original iMac (with a maximum capacity of 1 GB of RAM).

With this update, Apple split out the line in to “Good, Better and Best” models.

At the base, a 350 Mhz model sold at the elusive $999 price point, and was available only in Blueberry.

The 400 Mhz models included FireWire support, and wore the “DV” badge. These machines shipped in Blueberry, Grape, Strawberry, Tangerine and Lime, as the “Five Flavor” iMacs before them.

The “DV SE” was the same machine, but in Graphite, which, in my opinion, is the best-looking of all the iMac colors.

All of the slot-loading iMacs weigh in at 34.7 pounds / 15.7 kg, with dimensions of 15.0 x 15.0 x 17.1 inches / 38,1 x 38,1 x 43,5 cm.

The previous tray-loading iMacs were slightly larger at 38.1 pounds / 17.2 kg and 15.8 x 15.2 x 17.6 inches / 40,1 x 38,6 x 44,7 cm.

Goodbye

July 2000: Summer 2000 iMacs

In July 2000, Apple revved the iMac G3 line once again. These machines got new processor and hard drive options, and added support for Apple’s new AirPort cards. These iMacs required Mac OS 9.0.4, and support up to OS X 10.4 Tiger, except for the base model, due to its lack of FireWire 400 ports.

Gone were the Five Flavor colors.

At an all new $799 level, Apple had an all-new Indigo iMac running at 350 Mhz, with no FireWire and no AirPort support.
At 400 Mhz and $999, the iMac DV (Summer 2000) was available in Indigo and Ruby. These were the first iMacs to ship with Apple’s Pro Keyboard and Mouse, in black.

The iMac DV+ (Summer 2000) was the only iMac to ship at 450 MHz. It was available in Indigo, Ruby, and Sage. A slot-loading DVD-ROM was standard.

This generation of iMac also had a “DV SE” option, in the previously-used Graphite, as well as a new Snow color.

February 2001: Early 2001 iMacs

Welcome to what I call the “WTF Phase” of the iMac G3.

With this generation, all models gained FireWire 400 ports. Apple dropped Sage and Ruby in favor of “Blue Dalmatian” and “Flower Power”, two new patterns that were molded into the iMac’s case using a technique which took Apple 18 months to perfect.
Bonkers.

The low-end option was basically a “DV (Summer 2000) with a 400 Mhz processor at $899.

On the high-end, the new iMac picked up a CD-RW drive, leading to the “Rip. Mix. Burn.” campaign. These machines came with 20 GB hard drives and 500 Mhz G3 processors, as well as new video cards. These machines required OS 9.1

July 2001: Summer 2001 iMacs

In July 2001, Apple revved the iMac G3 for the last time.

Thankfully, Flower Power and Dalmatian didn’t make it past that single generation.

At the low end, running at 500 Mhz, Apple had an iMac in Indigo and Snow, with and ATI Rage 128 Ultra (AGP 2X) graphics card with 16 MB of VRAM, an an optional CD-RW drive. This machine sold for $999, an increase over previous low-end machines.

At 600 Mhz, the middle of the road iMac came with a 40 GB hard drive, CD-RW drive and the same video card as the low-end model. It sold in Graphite and Snow for $1299.

A 700 Mhz model was also for sale for a short time, making it the fastest CRT-based iMac of all time. In Graphite and Snow, it came with a 60 GB hard drive, but otherwise was the same as the mid-range model. This machine came with Mac OS 9.1 and Mac OS X 10.0.4, the only original iMac G3 to come with OS X.

The Final Chapter

In January 2002, with the release of the iMac G4, Apple re-arranged the iMac G3 line, keeping it for sale for a short time.

The low-end $799 model had its RAM bumped to 128 MB, and shipped with Mac OS X 10.2 as the default OS.

Goodbye (mezzanine) Mac Os 11

The G3/600 saw a price drop to $999.

The G3/700 was discontinued.

See Full List On Github.com

Conclusion

Goodbye (mezzanine) Mac Os Catalina

It’s hard to overstate the importance of the iMac G3. The iMac G3 ushered Apple in to the future, and on its translucent back, Steve Jobs rebuilt the company. While it was already under early development when Jobs returned to Apple, he took the project and made it the single machine he would re-launch the Macintosh family with. Before the iMac G3, Apple had numerous, conflicting product lines, and afterwards, just a handful of complementary ones.

Image via Wikipedia