A Very Simple Introduction to Xcode, Cocoa and Quartz

Total Page:16

File Type:pdf, Size:1020Kb

A Very Simple Introduction to Xcode, Cocoa and Quartz A very simple introduction to XCode, Cocoa and Quartz XCode is a Mac application which provides a programming environment (editor, documentation, project manager, debugger and compiler) for writing scripts and applications. It is especially suited for writing programs in C, C++, Objective C, Cocoa, Ruby and Python. XCode is installed on all the CoMPLEX computers and can also be downloaded for free from the Mac Dev Center after you sign up for a free account. Cocoa is a programming language which is what native Mac applications are written in. It is based on Objective C, which is in turn based on C. It is object-oriented. Objective C can be compiled to run on any platform, but Cocoa contains frameworks which are only designed to run on the Mac. Quartz is a technology used for rendering 2D graphics on the Mac. It provides a means for drawing simple shapes (rectangles, ovals, paths and text) onto the screen. There are a range of Cocoa drawing commands which let you create Quartz graphics and display them in application windows. Core Image is a technology which extends the capabilities of Quartz with extra effects. ButtonPush The ButtonPush project makes a simple application that increments a counter each time a button is pushed and displays it in a window. To make this, open a new Cocoa Application project in XCode. Double click the NIB file: MainMenu.xib. This opens Interface Builder – an application that lets you build graphical user interfaces for your application. The Library window contains GUI elements that you can drag onto your window. Search for "Button" and "Label" (a kind of NSTextField) and drag them onto the window. Resize the elements and the window to look as they do in the example. The Inspector window (Tools > Inspector) lets you edit the attributes of your GUI elements and window. With the window selected, use the Inspector to edit the window's title and deselect "Resize" so that the window has fixed dimensions. Press Command-R to simulate your interface. You shouldn't be able to resize the window. Use the Inspector to change the title of the button and the label elements. Make sure the text of the label is centred. Save and quit. Create a new class file in XCode (Command-N). Choose Objective-C class. Name it something like "AppController". You should see two files created: AppController.h and AppController.m. The "h" file is an interface file and the "m" file is an implementation file. The interface file gives information about what kind of objects and functions (methods) the class has. The implementation file contains all the code that actually implements those methods using those objects. Edit the interface file to match the example. An IBOutlet is an object that outputs data from the program to a GUI element in your window. This one (myTextField) will control the appearance of your label. An IBAction is a function (method) which is called by a GUI element in your window. This one (buttonPush) is called whenever the button is pushed. Save the file. Open up Interface Builder again by double clicking on MainMenu.xib. Find the "Object" object in the Library and drag it into the window with MainMenu.xib(English) at the top. Select the object and, in the Inspector, choose the "Identity" tab (i in a circle) and find AppController in the Class Identity menu. Select it. Now, right-click on the AppController object. You should see a list of Outlets and Actions. Drag from the circle next to "myTextField" onto your label. It should form a connection. Then do the same from the action "buttonPush" onto your button. Now these outlets and actions are connected to the code in XCode. Edit the implementation file to match the one in the example. Start by making the buttonPush method write a log to the console. Console logs are called with the Objective C method: Edit the implementation file to match the one in the example. Start by making the buttonPush method write a log to the console. Console logs are called with the Objective C method: NSLog(@"This is a log to the console"); The @ sign just tells you that a string object is coming up. You can mix strings and variable values in your logs using format strings. These use the % sign to mark positions where you want to insert a variable. %d represents an integer value and %f marks a float value. So: int numberOfOranges = 10; NSLog(@"There were %d oranges in the basket", numberOfOranges); will print: There were 10 oranges in the basket You can make a format string object by calling the stringWithFormat: method on the NSString object: int numberOfOranges = 10; NSString *myString = [NSString stringWithFormat:@"There were %d oranges in the basket", numberOfOranges]; The square bracket notation is the way Objective C calls methods on objects. The general form is: [objectName methodNameWithParameter:parameterName]; The awakeFromNib method is always called right at the start of launching an application. You don't need to declare this method in the interface file. It's like an initial set-up method. We're using it to set the counter to zero and also test writing logs to the console. Save your project and click Build and Go. Hopefully it should increment the counter when you click the button. QuartzDraw This application creates a window containing a graphical View object which displays a range of images generated with Quartz 2D commands. Open a new project and, first off, open up the MainMenu.xib in Interface Builder again. In Library, search for Custom View and drag it into the window. Resize the view to 500×500. Change the title of the window to whatever you want and make it fixed-size. Save and quit. Create a new class, but choose Objective C NSView Subclass instead of Objective C Class. Call it something like QuartzView. The NSView class generates two code blocks in your implementation file automatically: initWithFrame: and drawRect: . The second of these, drawRect: is the one where all of the drawing commands have to go. Add the following code to the drawRect: code block: [[NSColor whiteColor] set]; NSRectFill([self bounds]); NSRect myRect = NSMakeRect(50,50,50,50); [[NSColor redColor] set]; NSRectFill(myRect); The set method chooses what colour is being used to either fill or stroke (colour the outlines) of your shapes. NSRect is a class which generates rectangular shapes. [self bounds] is a rectangle object which covers the whole canvas, so the second line fills the whole canvas with white. In the third line, we create a rectangle object at position (50,50) (measured from bottom left) with width 50 and height 50. In the third line, we create a rectangle object at position (50,50) (measured from bottom left) with width 50 and height 50. Save the project, open up the NIB file again and select the Custom View. In the Identity tab of the Inspector, select "QuartzView" in the Class menu. Now the behaviour of the view is linked to your NSView subclass object. Quit Interface Builder. Back in XCode, click Build and Go. You should get a white background with a red rectangle on it. Play with the coordinates and dimensions of the red rectangle until you're happy with it. Have a look through the rest of the drawing code and try to work out what's going on. There are explanations of how to generate different 2D graphics objects at Cocoa Dev Central: http://cocoadevcentral.com/d/intro_to_quartz/ and in the Cocoa Drawing Guide: http://developer.apple.com/documentation/Cocoa/Conceptual/ CocoaDrawingGuide Further resources There is extensive documentation on Apple's developer pages http://developer.apple.com/documentation/Cocoa/ but the documents are quite long and technical. Cocoa Dev Central http://cocoadevcentral.com/ has some short introductions to Cocoa, Objective C, C and Quartz with simple examples to work through. Macresearch has a series of tutorials designed for scientists http://www.macresearch.org/cocoa_for_scientists which takes you through some basics of Cocoa programming, looks at Quartz and OpenGL (3D graphics) and also has topics in parsing data and creating animations. The best book for learning Cocoa is by Aaron Hillegass http://www.amazon.co.uk/Cocoa-Programming-Mac-OS-X/dp/0321503619/ ref=sr_1_1?ie=UTF8&s=books&qid=1241709583&sr=8-1 If you have problems in Cocoa or other programming languages http://stackoverflow.com/ has quite newbie-friendly support..
Recommended publications
  • KDE 2.0 Development, Which Is Directly Supported
    23 8911 CH18 10/16/00 1:44 PM Page 401 The KDevelop IDE: The CHAPTER Integrated Development Environment for KDE by Ralf Nolden 18 IN THIS CHAPTER • General Issues 402 • Creating KDE 2.0 Applications 409 • Getting Started with the KDE 2.0 API 413 • The Classbrowser and Your Project 416 • The File Viewers—The Windows to Your Project Files 419 • The KDevelop Debugger 421 • KDevelop 2.0—A Preview 425 23 8911 CH18 10/16/00 1:44 PM Page 402 Developer Tools and Support 402 PART IV Although developing applications under UNIX systems can be a lot of fun, until now the pro- grammer was lacking a comfortable environment that takes away the usual standard activities that have to be done over and over in the process of programming. The KDevelop IDE closes this gap and makes it a joy to work within a complete, integrated development environment, combining the use of the GNU standard development tools such as the g++ compiler and the gdb debugger with the advantages of a GUI-based environment that automates all standard actions and allows the developer to concentrate on the work of writing software instead of managing command-line tools. It also offers direct and quick access to source files and docu- mentation. KDevelop primarily aims to provide the best means to rapidly set up and write KDE software; it also supports extended features such as GUI designing and translation in con- junction with other tools available especially for KDE development. The KDevelop IDE itself is published under the GNU Public License (GPL), like KDE, and is therefore publicly avail- able at no cost—including its source code—and it may be used both for free and for commer- cial development.
    [Show full text]
  • Note on Using the CS+ Integrated Development Environment
    Tool News RENESAS TOOL NEWS on April 16, 2015: 150416/tn2 Note on Using the CS+ Integrated Development Environment When using the CS+ IDE, take note of the problem described in this note regarding the following point. Statements in source code which form a deeply-nested block 1. Products Concerned Products from the following list for which the version number of the CS+ common program is 3.00.00 to 3.01.00. - RX Family C/C++ Compiler Package (with IDE) - RL78 Family C Compiler Package (with IDE) - RH850 Family C Compiler Package (with IDE) - CS+ evaluation edition To check the version number of the product you have, refer to the following URL. https://www.renesas.com/cubesuite+_ver 2. Description CS+ might be terminated forcibly when a program is downloaded to a debugging tool or when an editor panel is opened after downloading a program. 3. Conditions Forced termination may occur when the source code for a project includes code that meets any of the following conditions. (a) { } blocks nested to a depth of 128 or more within a function. (b) 64 or more consecutive "else if" conditions are in sequence. (c) The total of double the number of consecutive "else if" conditions and the depth of the nesting of {} blocks at some point in the sequence of consecutive "else if" conditions is 128 or more. With conditions (b) and (c) above, the problem only arises when the C99 option is designated and the product is the RX family C/C++ compiler package (with IDE). 4. Workaround To avoid this problem, do any of the following.
    [Show full text]
  • Embrace and Extend Approach (Red Hat, Novell)
    Integrated Development Environments (IDEs) Technology Strategy Chad Heaton Alice Park Charles Zedlewski Table of Contents Market Segmentation.............................................................................................................. 4 When Does the IDE Market Tip? ........................................................................................... 6 Microsoft & IDEs ................................................................................................................... 7 Where is MSFT vulnerable?................................................................................................. 11 Eclipse & Making Money in Open Source........................................................................... 12 Eclipse and the Free Rider Problem ..................................................................................... 20 Making Money in an Eclipse World?................................................................................... 14 Eclipse vs. Microsoft: Handicapping the Current IDE Environment ................................... 16 Requirements for Eclipse success......................................................................................... 18 2 Overview of the Integrated Development Environment (IDE) Market An Integrated Development Environment (IDE) is a programming environment typically consisting of a code editor, a compiler, a debugger, and a graphical user interface (GUI) builder. The IDE may be a standalone application or may be included as part of one or more existing
    [Show full text]
  • Kinect in Mac: QC and Processing
    Kinect in Mac: Quartz Composer and Processing A brief tutorial by NIRTeam @ TEI Crete Contents ● Using Quartz Composer with Kinect ● Using Processing programming language with kinect ● 3D scanning using Kinect Quartz Composer (QC) ● Node-based visual programming language used mainly for processing and rendering graphics. ● Included in the Xcode developer tools package by Apple ● Quartz Composer uses OpenGL (including GLSL), OpenCL, Core Image, Core Video, JavaScript, and other technologies to build an API and a developer tool Data types inside QC Boolean - a boolean value, 0 or 1 Index - a positive integer between 0 and 2147483647 Number - a double precision floating point number String - a unicode string Color - an RGBA or CMYK quartet, or a Grayscale value Image - a 2D image of arbitrary (possibly infinite) dimensions Structure - a named or ordered collection of objects, including nested structures Virtual - any of the above Mesh - a collection of vertices, and per-vertex normals, texture coordinates, and colors in 3-space. Interaction - a valueless type used to associate user input with user-interactive elements of the composition. QC Programming QC Programming = connecting different nodes (Patches). QC Patches The patches are divided into three categories: 1. “Providers” 2. “Processors” 3. “Consumers” QC resources - http://kineme.net/ - http://quartzcomposer.com/compositions - http://www.quartzcompositions.com/ - http://guides.macrumors.com/Quartz_Composer Kinect & QC Kineme KinectTools plugin http://kineme.net/KinectTools Synapse plugin http://synapsekinect.tumblr.com/ v002 open Kinect example http://kineme.net/forum/Discussion/Programming/v002OpenKinectBeta Quartz-Composer-Open-Kinect-Plugin https://github.com/stoulouse/Quartz-Composer-Open-Kinect-Plugin UIO Kinect with TUIO client QC Plugin https://code.google.com/p/tuiokinect/ http://prdownloads.sourceforge.net/reactivision/TUIO_Quartz-1.4.zip?download Tryplex Toolkit http://code.google.com/p/tryplex/ Kinect & QC: Kineme KinectTools plugin ● Retrieves color and depth image data from the Kinect.
    [Show full text]
  • The C Programming Language
    The C programming Language The C programming Language By Brian W. Kernighan and Dennis M. Ritchie. Published by Prentice-Hall in 1988 ISBN 0-13-110362-8 (paperback) ISBN 0-13-110370-9 Contents ● Preface ● Preface to the first edition ● Introduction 1. Chapter 1: A Tutorial Introduction 1. Getting Started 2. Variables and Arithmetic Expressions 3. The for statement 4. Symbolic Constants 5. Character Input and Output 1. File Copying 2. Character Counting 3. Line Counting 4. Word Counting 6. Arrays 7. Functions 8. Arguments - Call by Value 9. Character Arrays 10. External Variables and Scope 2. Chapter 2: Types, Operators and Expressions 1. Variable Names 2. Data Types and Sizes 3. Constants 4. Declarations http://freebooks.by.ru/view/CProgrammingLanguage/kandr.html (1 of 5) [9/6/2002 12:20:42 ] The C programming Language 5. Arithmetic Operators 6. Relational and Logical Operators 7. Type Conversions 8. Increment and Decrement Operators 9. Bitwise Operators 10. Assignment Operators and Expressions 11. Conditional Expressions 12. Precedence and Order of Evaluation 3. Chapter 3: Control Flow 1. Statements and Blocks 2. If-Else 3. Else-If 4. Switch 5. Loops - While and For 6. Loops - Do-While 7. Break and Continue 8. Goto and labels 4. Chapter 4: Functions and Program Structure 1. Basics of Functions 2. Functions Returning Non-integers 3. External Variables 4. Scope Rules 5. Header Files 6. Static Variables 7. Register Variables 8. Block Structure 9. Initialization 10. Recursion 11. The C Preprocessor 1. File Inclusion 2. Macro Substitution 3. Conditional Inclusion 5. Chapter 5: Pointers and Arrays 1.
    [Show full text]
  • FEI~I<Ts Ltistttute NEWS LETTER
    NEWS LETTER FEI~I<tS ltiSTtTUTE from l\Yron J. Brophy, President VOL. 1. NO.7 Big Rapids, !.Iichigan July 23, 1951 . BUlmmG ffiOOR,i1SS. Mon~ Progress Meeting was held at the site at 1 p.m. Wednesday, Jul¥ lB. Those present were: For the Institution" . President Brophy, It'. Pattullo" and Mr. DeMOSS; for the Building Division" Mr. J. ~-'angema.n, and 11:r. Arthur Decker, the project Superintendent; for the IJuskegon Construction Company, Mr. Smith and Mr. Mastenbrook; fC1!.' t...~e Distel Heating Company, ur. Holgate; and for the Electric Construction t.; Machiner"J COmpany, ur. Brabon and Mr. Knight,; and for the Architect, l!r'. Roger Allen. Mr. Allen reported that the color scheme for all rooms in the East Wing has been determined. Mr. lD:rnest King, from the architect1s office, conferred With l!r. pattullo Friday to discuss the preparation of similar color schemes for the Vlest Wing. Work on General C~struction is proceeding rapidq and all mechanical contractors are keeping up with the construction. All structural steel roof framing for the one-story sections will be in place by the middle of this 'week and will be ready to receiVe steel roof deck. ];!t'. Smith hB.f3 received word from the Detroit Steel Products Company (sub­ contractors for the steel deck) that this material Will be Shipped some­ time bet\"loon July 30th and August loth. The fin!ll poUring of cement sla.bin the classroom building was completed last l'leck. The stone Window Sills have been received and installation has started. The alllnlinum vlindow frames Bl'e now being in­ stalled and arc ready for the laying of the glass blockS.
    [Show full text]
  • 2.3.7 80X86 Floating Point
    Open Watcom C/C++ Compiler Options data segment. For example, the option "zt100" causes all data objects larger than 100 bytes in size to be implicitly declared as far and grouped in other data segments. The default data threshold value is 32767. Thus, by default, all objects greater than 32767 bytes in size are implicitly declared as far and will be placed in other data segments. If the "zt" option is specified without a size, the data threshold value is 256. The largest value that can be specified is 32767 (a larger value will result in 256 being selected). If the "zt" option is used to compile any module in a program, then you must compile all the other modules in the program with the same option (and value). Care must be exercised when declaring the size of objects in different modules. Consider the following declarations in two different C files. Suppose we define an array in one module as follows: extern int Array[100] = { 0 }; and, suppose we reference the same array in another module as follows: extern int Array[10]; Assuming that these modules were compiled with the option "zt100", we would have a problem. In the first module, the array would be placed in another segment since Array[100] is bigger than the data threshold. In the second module, the array would be placed in the default data segment since Array[10] is smaller than the data threshold. The extra code required to reference the object in another data segment would not be generated. Note that this problem can also occur even when the "zt" option is not used (i.e., for objects greater than 32767 bytes in size).
    [Show full text]
  • Mac OS X: an Introduction for Support Providers
    Mac OS X: An Introduction for Support Providers Course Information Purpose of Course Mac OS X is the next-generation Macintosh operating system, utilizing a highly robust UNIX core with a brand new simplified user experience. It is the first successful attempt to provide a fully-functional graphical user experience in such an implementation without requiring the user to know or understand UNIX. This course is designed to provide a theoretical foundation for support providers seeking to provide user support for Mac OS X. It assumes the student has performed this role for Mac OS 9, and seeks to ground the student in Mac OS X using Mac OS 9 terms and concepts. Author: Robert Dorsett, manager, AppleCare Product Training & Readiness. Module Length: 2 hours Audience: Phone support, Apple Solutions Experts, Service Providers. Prerequisites: Experience supporting Mac OS 9 Course map: Operating Systems 101 Mac OS 9 and Cooperative Multitasking Mac OS X: Pre-emptive Multitasking and Protected Memory. Mac OS X: Symmetric Multiprocessing Components of Mac OS X The Layered Approach Darwin Core Services Graphics Services Application Environments Aqua Useful Mac OS X Jargon Bundles Frameworks Umbrella Frameworks Mac OS X Installation Initialization Options Installation Options Version 1.0 Copyright © 2001 by Apple Computer, Inc. All Rights Reserved. 1 Startup Keys Mac OS X Setup Assistant Mac OS 9 and Classic Standard Directory Names Quick Answers: Where do my __________ go? More Directory Names A Word on Paths Security UNIX and security Multiple user implementation Root Old Stuff in New Terms INITs in Mac OS X Fonts FKEYs Printing from Mac OS X Disk First Aid and Drive Setup Startup Items Mac OS 9 Control Panels and Functionality mapped to Mac OS X New Stuff to Check Out Review Questions Review Answers Further Reading Change history: 3/19/01: Removed comment about UFS volumes not being selectable by Startup Disk.
    [Show full text]
  • Mac OS X and PDF: the Real Story
    Mac OS X and PDF The Real Story Leonard Rosenthol Lazerware, Inc. Copyright©1999-2001, Lazerware, Inc. Overview •Mac OS X •PDF • Where’s the overlap? Copyright©1999-2001, Lazerware, Inc. You are here because… • You’re currently working with Mac OS and are interested in what Mac OS X brings to the table. • You’re curious about what Apple’s latest hype is all about. • You’re already awake and had to find something to kill time. • You’re a friend of mine and wanted to heckle Copyright©1999-2001, Lazerware, Inc. How I do things • You should all have copies of the presentation that you received when you walked in. • There is also an electronic copy of this presentation (PDF format, of course!) on my website at http://www.lazerware.com/ • I’ve left time at the end for Q&A, but please feel free to ask questions at any time! Copyright©1999-2001, Lazerware, Inc. Mac OS X Overview Copyright©1999-2001, Lazerware, Inc. Darwin • “Core OS” (Kernel) – Solid Unix foundation • FreeBSD 3.2 & Mach 3.0 • Memory protection, preemptive multitasking, etc. – High performance I/O • Firewire, USB, etc. • Open source Copyright©1999-2001, Lazerware, Inc. Graphics •Quartz – Adobe Imaging Model (PDF) • Includes full anti-aliasing and opacity/transparency • OpenGL – Industry standard 3D engine used by Quake & Maya • QuickTime Copyright©1999-2001, Lazerware, Inc. Graphics Demos - Quartz Copyright©1999-2001, Lazerware, Inc. Graphics Demos – OpenGL Copyright©1999-2001, Lazerware, Inc. Application Frameworks • Classic – Compatibility “box” for existing Mac OS applications. • Carbon – Modern versions of Mac OS applications prepared for Mac OS X.
    [Show full text]
  • Top Productivity Tips for Using Eclipse for Embedded C/C++ Developers
    Top Productivity Tips for Using Eclipse for Embedded C/C++ Developers Garry Bleasdale, QNX Software Systems, [email protected] Andy Gryc, QNX Software Systems, [email protected] Introduction This paper presents a selection of Eclipse IDE tips and tricks gathered from: the QNX® development community: our engineers, techies and trainers Foundry27, the QNX Community Portal for open development, where we have an Eclipse IDE forum Eclipse.org forums public web sites and blogs that offer Eclipse-related expertise The 27 tips described in this paper are the tips that we received from these sources and identified as most interesting and useful to developers. We present them here with the hope that they will help make you more productive when you use the Eclipse IDE. About Eclipse A modern embedded system may employ hundreds of software tasks, all of them sharing system resources and interacting in complex ways. This complexity can undermine reliability, for the simple reason that the more code a system contains, the greater the probability that coding errors will make their way into the field. (By some estimates, a million lines of code will ship with at least 1000 bugs, even if the code is methodically developed and tested.) Coding errors can also compromise security, since they often serve as entry points for malicious hackers. No amount of testing can fully eliminate these bugs and security holes, as no test suite can anticipate every scenario that a complex software system may encounter. Consequently, system designers and software developers must adopt a “mission-critical mindset” and employ software architectures that can contain software errors and recover from them quickly.
    [Show full text]
  • Using the Java Bridge
    Using the Java Bridge In the worlds of Mac OS X, Yellow Box for Windows, and WebObjects programming, there are two languages in common use: Java and Objective-C. This document describes the Java bridge, a technology from Apple that makes communication between these two languages possible. The first section, ÒIntroduction,Ó gives a brief overview of the bridgeÕs capabilities. For a technical overview of the bridge, see ÒHow the Bridge WorksÓ (page 2). To learn how to expose your Objective-C code to Java, see ÒWrapping Objective-C FrameworksÓ (page 9). If you want to write Java code that references Objective-C classes, see ÒUsing Java-Wrapped Objective-C ClassesÓ (page 6). If you are writing Objective-C code that references Java classes, read ÒUsing Java from Objective-CÓ (page 5). Introduction The original OpenStep system developed by NeXT Software contained a number of object-oriented frameworks written in the Objective-C language. Most developers who used these frameworks wrote their code in Objective-C. In recent years, the number of developers writing Java code has increased dramatically. For the benefit of these programmers, Apple Computer has provided Java APIs for these frameworks: Foundation Kit, AppKit, WebObjects, and Enterprise Objects. They were made possible by using techniques described later in Introduction 1 Using the Java Bridge this document. You can use these same techniques to expose your own Objective-C frameworks to Java code. Java and Objective-C are both object-oriented languages, and they have enough similarities that communication between the two is possible. However, there are some differences between the two languages that you need to be aware of in order to use the bridge effectively.
    [Show full text]
  • GCC Toolchain Eclipse Setup Guide
    !"#$ % '#((#()*!+,-.#)/$01234 GCC Toolchain Eclipse Setup Guide WP0001 Version 5 September 23, 2020 Copyright © 2017-2020 JBLopen Inc. All rights reserved. No part of this document and any associated software may be reproduced, distributed or transmitted in any form or by any means without the prior written consent of JBLopen Inc. Disclaimer While JBLopen Inc. has made every attempt to ensure the accuracy of the information contained in this publication, JBLopen Inc. cannot warrant the accuracy of completeness of such information. JBLopen Inc. may change, add or remove any content in this publication at any time without notice. All the information contained in this publication as well as any associated material, including software, scripts, and examples are provided “as is”. JBLopen Inc. makes no express or implied warranty of any kind, including warranty of merchantability, noninfringement of intellectual property, or fitness for a particular purpose. In no event shall JBLopen Inc. be held liable for any damage resulting from the use or inability to use the information contained therein or any other associated material. Trademark JBLopen, the JBLopen logo, TREEspanTM and BASEplatformTM are trademarks of JBLopen Inc. All other trademarks are trademarks or registered trademarks of their respective owners. Contents 1 Overview 1 1.1 About Eclipse ............................................. 1 2 Eclipse Setup Guide (Windows) 2 2.1 MSYS2 Installation .......................................... 2 2.2 Eclipse Installation .......................................... 11 2.3 Toolchain Installation ......................................... 16 2.4 Environment Variable Setup ..................................... 17 2.4.1 PATH Environnement Variable Setup ........................... 17 3 Eclipse Setup Guide (Linux) 22 3.1 Eclipse Installation .......................................... 22 3.2 Toolchain Installation ......................................... 27 3.3 GNU Make Installation .......................................
    [Show full text]