mundoload109 - Tumblr blog

mundoload109 · 4 years ago

Text

Jre Macos

Installation of the JDK and the JRE on macOS: Instructions include steps to install JDK and JRE on macOS platform. Directory Structure To learn about the files and directories that are created after JDK and JRE installation, see Installed Directory Structure of JDK and JRE.

JRE is the Java Runtime Environment – it contains a JVM, among other things, and is what you need to run a Java program. JDK is the Java Development Kit – it is the JRE, but with javac (which is what you need to compile Java source code) and other programming tools added.

The Java Development Kit (JDK), officially named 'Java Platform Standard Edition' or 'Java SE', is needed for writing and running Java programs.

Currently, the OpenJDK developed by Oracle and the Java community (@ https://openjdk.java.net/) provides a free and open-source JDK official reference implementation.

This article is based on the Oracle JDK (@ https://www.oracle.com/java/) (due to legacy), which is free for personal and development use but no longer free for commercial use.

JDK Versions

Reference: 'Java Version History' @ https://en.wikipedia.org/wiki/Java_version_history.

JDK Alpha and Beta (1995): Sun Microsystem announced Java in September 23, 1995.

JDK 1.0 (January 1996): Originally called Oak (named after the oak tree outside James Gosling's office). Renamed to Java 1 in JDK 1.0.2.

JDK 1.1 (February 1997): Introduced AWT event model, inner class, JavaBean, JDBC, and RMI.

J2SE 1.2 (JDK 1.2) (December 1998): Re-branded as 'Java 2' and renamed JDK to J2SE (Java 2 Standard Edition). Also released J2EE (Java 2 Enterprise Edition) and J2ME (Java 2 Micro Edition). Included JFC (Java Foundation Classes - Swing, Accessibility API, Java 2D, Pluggable Look & Feel, and Drag & Drop). Also introduced Collection Framework and JIT compiler.

J2SE 1.3 (JDK 1.3) (May 2000): Introduced Hotspot JVM.

J2SE 1.4 (JDK 1.4) (February 2002): Introduced assert statement, non-blocking IO (nio), logging API, image IO, Java webstart, regular expression (regex) support.

J2SE 5.0 (JDK 5) (September 2004): Officially called 5.0 instead of 1.5 (by dropping the 1.). Introduced generics, autoboxing/unboxing, annotation, enum, varargs, for-each loop, static import. See 'JDK 5 New Features'.

Java SE 6 (JDK 6) (December 2006): Renamed J2SE to Java SE (Java Platform Standard Edition). No new language features. See 'JDK 6 New Features'.

Java SE 7 (JDK 7) (July 2011): First version after Oracle purchased Sun Microsystem - aslo called OracleJDK. Introduced Strings in switch statement, Binary integer literals, allowing underscores in numeric literals, improved type inference for generic instance creation (or diamond operator <>), Catching multiple exception types and rethrowing exceptions with improved type checking. See 'JDK 7 New Features'.

Java SE 8 LTS (JDK 8) (March 2014): Included support for Lambda expressions, default and static methods in interfaces, improved collection, and JavaScript runtime. Also integrated JavaFX graphics subsystem. See 'JDK 8 New Features'.

Java SE 9 (JDK 9) (September 21, 2017): Introduced modularization of the JDK (module) under project Jigsaw, the Java Shell (jshell), and more. See 'JDK 9 New Features'.

Java SE 10 (18.3) (JDK 10) (March 2018): Introduced var for type inference local variable (similar to JavaScript). Introduced time-based release versioning with two releases each year, in March and September, denoted as YY.M. Removed native-header generation tool javah. See 'JDK 10 New Features'.

Java SE 11 LTS (18.9) (JDK 11) (September 2018): Extended var to lambda expression. Standardize HTTP client in java.net.http. Support TLS 1.3. Clean up the JDK and the installation package (removed JavaFX, JavaEE, CORBA modules, deprecated Nashorn JavaScript engine). OracleJDK is no longer free for commercial use, but OpenJDK is still free. See 'JDK 11 New Features'.

Java SE 12 (19.3) (JDK 12) (March 2019): Switch Expression (preview). See 'JDK 12 New Features'.

Java SE 13 (19.9) (JDK 13) (September 2019): Switch Expression (preview), Multi-line Text Block (preview). See 'JDK 13 New Features'.

Java SE 14 (20.3) (JDK 14) (March 2020): Records (preview)

Java SE 15 LTS (20.9) (JDK 15) (September 2020):

'JDK' or 'JRE'?

JRE (Java Runtime), which include a Java Virtual Machine and core libraries, is needed for running Java programs. JDK (Java Development Kit), which includes JRE plus the development tools (such as compiler and debugger), is need for writing as well as running Java programs. In other words, JRE is a subset of JDK. Since you are supposed to write Java Programs instead of merely running Java programs, you should install JDK, which includes JRE.

How To Install JDK on Windows

Step 0: Un-Install Older Version(s) of JDK/JRE

I recommend that you install only the latest JDK. Although you can install multiple versions of JDK/JRE concurrently, it is messy.

If you have previously installed older version(s) of JDK/JRE, un-install ALL of them. Goto 'Control Panel' ⇒ (optional) 'Programs' ⇒ 'Programs and Features' ⇒ Un-install ALL programs begin with 'Java', such as 'Java SE Development Kit ..', 'Java SE Runtime ..', 'Java X Update ..', and etc.

Step 1: Download JDK

Goto JDK (or Java SE) download site @ https://www.oracle.com/java/technologies/javase-downloads.html.

Under 'Oracle JDK', click 'JDK Download'.

Download the 'Windows x64 Installer' (e.g., 'jdk-15.0.(x)_windows-x64_bin.exe' - about 159MB), where (x) is a fast changing update number.

Step 2: Install JDK

Run the downloaded installer. Accept the defaults and follow the screen instructions to complete the installation. By default, JDK is installed in directory 'C:Program FilesJavajdk-15.0.(x)', where (x) denotes the update number.

Launch 'File Explorer'. Navigate to 'C:Program FilesJava' to inspect the directories. Take note of your JDK Installed Directoryjdk-15.0.(x), in particular, the update number (x) which you will need in the next step.

I shall refer to the JDK Installed Directory as <JAVA_HOME>, hereafter, in this article (corresponding to environment variable %JAVA_HOME% in Windows or $JAVA_HOME in Unix/macOS).

Step 3: (SKIP for JDK 15) Include JDK's 'bin' Directory in the PATH

Windows' Command Prompt (CMD) searches the current directory and the directories listed in the PATHenvironment variable for executable programs.

JDK's programs (such as Java compiler 'javac.exe' and Java runtime 'java.exe') reside in the sub-directory 'bin' of the JDK installed directory. JDK's 'bin' needs to be added into the PATH.

Prior to JDK 15, you need to explicitly add JDK's 'bin' into the PATH. Starting from JDK 15, the installation process adds the directory 'C:Program FilesCommon FilesOracleJavajavapath' to the PATH. The 'javapath' directory is a link to 'javapath_target_xxxxxx', which contains a copy of the following JDK programs:

java.exe: Java Runtime

javac.exe: Java Compiler

javaw.exe: Java Runtime for Windows Console-less

jshell.exe: Java Command-line Shell (since JDK 10) - a Read-Evaluate-Print Loop (REPL) which evaluates declarations, statements, and expressions as they are entered and immediately shows the results.

Link is used so that you can keep multiple copies (versions) of JDK.

To edit the PATH environment variable in Windows 10:

Launch 'Control Panel' ⇒ (Optional) 'System and Security' ⇒ 'System' ⇒ Click 'Advanced system settings' on the left pane.

Switch to 'Advanced' tab ⇒ Click 'Environment Variables' button.

Under 'System Variables' (the bottom pane), scroll down to select variable 'Path' ⇒ Click 'Edit..'.

For Newer Windows 10: You shall see a TABLE listing all the existing PATH entries (if not, goto next step). Click 'New' ⇒ Click 'Browse' and navigate to your JDK's 'bin' directory, i.e., 'c:Program FilesJavajdk-15.0.(x)bin', where (x) is your installation update number ⇒ Select 'Move Up' to move this entry all the way to the TOP.

For Older Windows 10 (Time to change your computer!): (CAUTION: Read this paragraph 3 times before doing this step! Don't push 'Apply' or 'OK' until you are 101% sure. There is no UNDO!!!) (To be SAFE, copy the content of the 'Variable value' to Notepad before changing it!!!) In 'Variable value' field, APPEND 'c:Program FilesJavajdk-15.0.(x)bin' (where (x) is your installation update number) IN FRONT of all the existing directories, followed by a semi-colon (;) to separate the JDK's bin directory from the rest of the existing directories. DO NOT DELETE any existing entries; otherwise, some existing applications may not run.

You need to re-started CMD for the new environment settings to take effect.

Step 4: Verify the JDK Installation

Launch a CMD via one of the following means:

Click 'Search' button ⇒ Type 'cmd' ⇒ Choose 'Command Prompt', or

Right-click 'Start' button ⇒ run.. ⇒ enter 'cmd', or

Click 'Start' button ⇒ Windows System ⇒ Command Prompt

Issue the following commands to verify your JDK installation:

(Skip for JDK 15) Issue 'path' command to list the contents of the PATH environment variable. Check to make sure that your JDK's 'bin' is listed in the PATH.

Issue the following commands to verify that JDK/JRE are properly installed and display their version:

Step 5: Write a Hello-World Java Program

Create a directory to keep your works, e.g., 'd:myProject' or 'c:myProject'. Do NOT save your works in 'Desktop' or 'Documents' as they are hard to locate. The directory name shall not contain blank or special characters. Use meaningful but short name as it is easier to type.

Launch a programming text editor (such as TextPad, NotePad++, Sublime Text, Atom). Begin with a new file and enter the following source code. Save the file as 'Hello.java', under your work directory (e.g., d:myProject).

Step 6: Compile and Run the Hello-World Java Program

To compile the source code 'Hello.java':

Start a CMD Shell (Search ⇒ enter 'cmd' ⇒ select 'Command Prompt').

Set the Current Drive to the drive where you saved your source file 'Hello.java'. If you use drive 'c', skip this step. Else if you use drive 'd', enter 'd:' as follow:

Set the Current Working Directory to the directory that you saved your source file via the cd (Change Directory) command. For example, suppose that your source file is saved in directory 'myProject'.

Issue a dir (List Directory) command to confirm that your source file is present in the current directory.

Invoke the JDK compiler 'javac' to compile the source code 'Hello.java'. The compilation is successful if the command prompt returns. Otherwise, error messages would be shown. Correct the errors in your source file and re-compile. Check 'Common JDK Installation Errors', if you encounter problem compiling your program.

The output of the compilation is a Java class called 'Hello.class'. Issue a dir (List Directory) command again to check for the output.

To run the program, invoke the Java Runtime 'java':

Everything that can possibly go wrong will go wrong: Read 'JDK Installation Common Errors'.

Step 7: (For Advanced Users Only) JDK's Source Code

Source code for JDK is provided and kept in '<JAVA_HOME>libsrc.zip' (or '<JAVA_HOME>src.zip' prior to JDK 9). I strongly recommend that you to go through some of the source files such as 'String.java', 'Math.java', and 'Integer.java', under 'javalang', to learn how experts program.

How to Install JDK on macOS

Step 1: Check if JDK has been Pre-Installed

To check if JDK has been installed, open a 'Terminal' (Search 'Terminal'; or Finder ⇒ Go ⇒ Utilities ⇒ Terminal) and issue this command:

If a JDK version number is returned (e.g., JDK x.x.x), then JDK has already been installed. If the JDK version is prior to 1.8, proceed to Step 2 to install the latest JDK; otherwise, proceed to 'Step 3: Write a Hello-world Java program'.

If message 'command not found' appears, JDK is NOT installed. Proceed to the 'Step 2: Install JDK'.

If message 'To open javac, you need a Java runtime' appears, select 'Install' and follow the instructions to install JDK. Then, proceed to 'Step 3: Write a Hello-world Java program'.

Step 2: Download JDK

Goto JDK (or Java SE) download site @ https://www.oracle.com/java/technologies/javase-downloads.html.

Under 'Oracle JDK', click 'JDK Download'.

Download the 'macOS DMG installer' (e.g, jdk-15.0.(x)_osx-x64_bin.dmg - about 172MB, where (x) is a fast changing update number).

Step 3: Install JDK/JRE

Double-click the downloaded Disk Image (DMG) file. Follow the screen instructions to install JDK/JRE.

Eject the DMG file.

To verify your installation, open a 'Terminal' and issue these commands.

Step 3: Write a Hello-World Java Program

Create a directory called 'myProject' under your 'home' directory (Launch 'Finder' ⇒ 'Go' ⇒ 'Home'; Select 'File' ⇒ 'New Folder' ⇒ 'myProject'). In macOS/Unix, the 'home' directory of the current user can be referenced as '~'. Hence, this new directory can be referenced as '~/myProject'.

Use a programming text editor (such as Sublime Text or Atom) to input the following source code and save as 'Hello.java' under the directory '~/myProject'. (If you use macOS's default text editor 'TextEdit' (NOT recommended), you need to open a new file ⇒ choose 'Format' ⇒ 'Make Plain Text' ⇒ Enter the source code ⇒ Save as 'Hello.java'.)

Step 4: Compile and Run the Hello-World Java Program

To compile the source code 'Hello.java', open a new 'Terminal' ('Go' ⇒ 'Utilities' ⇒ 'Terminal') and issue these commands (as illustrated):

To run the Hello-world, invoke the Java Runtime 'java' as follows:

How to Install JDK on Ubuntu

We shall try both the OpenJDK (free and open-source) and the Oracle JDK (free for personal and development, but not free for production).

Step 0: Check if JDK has already been Installed

Open a Terminal and issue this command:

If a JDK version number (e.g., 'javac x.x.x') appears, JDK has already been installed. You can skia the installation and goto Open2.

Step 1a: Install OpenJDK

(TODO)

Jre Macos High Sierra

To remove OpenJDK, issue command:

Step 1b: Install Oracle JDK

Goto Oracle JDK (Java SE) download site @ https://www.oracle.com/java/technologies/javase-downloads.html ⇒ Under 'Oracle JDK', click 'JDK Download' ⇒ Select 'Linux x64 Compressed Archive' package (e.g., 'jdk-15.0.(x)-linux-x64_bin.tar.gz' - 179MB). The tarball will be downloaded in directory '~/Downloads', by default.

We shall install JDK under '/usr/local/java' (or Ubuntu's default JDK directory /usr/lib/jvm; or /opt/java). First, create a directory 'java' under '/usr/local'. Open a Terminal and issue these commands: Extract the downloaded package (Check your downloaded filename!) JDK shall be extracted in a folder '/usr/local/java/jdk-15.0.(x)', where (x) is the update number.

Inform the Ubuntu to use this JDK/JRE: The above steps set up symlinks java, javac, jshell at /usr/bin (which is in the PATH), that link to /etc/alternatives and then to JDK bin directory. The 'alternatives' system aims to resolve the situation where several programs fulfilling the same function (e.g., different version of JDKs). It sets up symlinks thru /etc/alternatives to refer to the actual programs to be used. Alternatively, you can include the JDK's bin into the PATH directly.

To verify the JDK installation, issue these commands:

(Don't Do this step - It is taken care by 'alternatives' in Step 3. Keep here to show you how to set PATH.) Add JDK's binary directory ('bin') to the 'PATH' by editing '/etc/profile': Add these lines at the end of the file '/etc/profile', replace '(x)' with the actual number: Rerun the configuration file by:

Step 2: Compile and Run a Hello-world Java Program

File Explorer ⇒ Home ⇒ Create a new folder called 'myProject' to keep our works.

Open 'Text Editor' (gedit). Enter the following source code and save as 'Hello.java' under the '~/myProject' directory created earlier.

To compile the Hello-world Java program, launch a Terminal and issue these commands:

Run the Hello-world Java program:

Notes: Starting from JDK 11, you can compile and run the hello-world in one single step via:

Source-Code Editors & IDEs for Java Programming

Eclipse IDE

You need to first install Eclipse. Read 'How to Install Eclipse'.

javaan then proceed to write your first Java program. Read 'Writing your first Java Program with Eclipse'.

Eclipse allow you to debug program graphically. Read 'Debugging program in Eclipse'.

NetBeans IDE

You need to first install NetBeans. Read 'How to Install NetBeans'.

You can then proceed to write your first Java program. Read 'Writing your first Java program with NetBeans'.

NetBeans allow you to debug program graphically. Read 'Debugging program in NetBeans'.

Visual Studio (VS) Code IDE

Click HERE, look for 'VS Code for Java Programming'

Sublime Text (for Windows, macOS, Linux)

Click HERE, look for 'Sublime Text for Java Programming'

Atom (for Windows, macOS, Linux)

(TODO)

TextPad (for Windows only)

Click HERE, look for 'TextPad for Java Programming'.

NotePad++ (for Windows only)

Click HERE, look for 'NotePad++ for Java Programming'.

(JDK 11 New Feature) Launch Single-Source-File

From JDK 11, you can 'compile and run' a single-file program in one step, without explicit compilation.

Write a 'Hello.java' (see previous section).

Delete 'Hello.class', if it exists.

You can compile/run 'Hello.java' in one command as follows:

Notes:

This is applicable to single source-file only.

No need to use javac to compile the program.

It compiles in memory (without producing a .class file), and run.

This feature is introduced for beginners to learn Java, and for professionals to test a Java feature.

The filename and classname need not be the same.

How To Set JAVA_HOME Environment Variable

Many Java applications (such as Tomcat) require the environment variable JAVA_HOME to be set to the JDK installed directory.

See 'How to set JAVA_HOME for Windows' or 'How to set JAVA_HOME for macOS/Linux'.

Common Errors in installing JDK

(Advanced) External JAR Files and Native Libraries

Notes: This section is applicable to JDK prior to JDK 9. JDK 9 introduces a new level called 'module' on top of package, and 'jmod Mac os 10.14 mojave download. ' files for Java modules. Need to revise this section for JDK 9.

External Java API packages (such as Servlet API, MySQL Connector/J, JOGL, JUnit) are often distributed in JAR files (Java Archive - a single-file package of many Java classes similar to ZIP or TAR), with possibly Native Libraries ('.lib' and '.dll' in Windows, or '.a' and '.so' in Linux/macOS).

External JAR Files ('.jar')

If external JAR files are not properly included:

During the compilation, you will receive compilation error 'cannot find symbol' for classes belonging to the external packages.

During execution, you will get a runtime error 'Could not find or load main class xxx' or 'NoClassDefFoundError'.

To include external JAR files, you can either:

(Prior to JDK 9) Copy all the JAR files of the external packages to the Java's Extension Directories (NOT applicable from JDK 9).

For Windows, the JDK extension directory is located at '<JAVA_HOME>jrelibext' (e.g., 'c:Program FilesJavajdk1.8.0_xxjrelibext').

For macOS, the JDK extension directories are '/Library/Java/Extensions' and '/System/Library/Java/Extensions'.

For Ubuntu, the JDK extension directories are '<JAVA_HOME>/jre/lib/ext' (e.g., '/usr/user/java/jdk1.8.0_xx/jre/lib/ext') and '/usr/java/packages/lib/ext'.

The location of JDK's extension directories is kept in Java's System Property 'java.ext.dirs'. You can print its contents via System.out.println(System.getProperty('java.ext.dirs')).

You can also include all the JAR files in the CLASSPATH environment variable. CLASSPATH may contain directories (of Java classes) or JAR files (single-file archive of Java classes). If you set the CLASSPATH, you must also include the current directory (denoted as '.').

For Windows, set the CLASSPATH in Control Panel ⇒ System ⇒ Advanced system settings ⇒ Advanced ⇒ Environment Variables ⇒ System Variables ⇒ New ⇒ In 'Variable name', enter 'CLASSPATH' ⇒ In 'Variable value', enter '.;path1xxx.jar;path2yyy.jar', where the entries are separated by a semi-colon (;).

For Linux and macOS: Edit ~/.profile or ~/.bash_profile (or /etc/profile for system-wide setting) to include the following line at the end of the file: The entries are separated by colon (:).

You can also set the CLASSPATH in the javac/java command-line via the option -cp <paths> (or -classpath <paths>), for example,

External Native Libraries ('.lib', '.dll', '.a', '.so')

Some external package may provide static or shared native libraries in the form of '.lib' (Windows' static LIBrary), '.dll' (Windows' Dynamically Link Library), '.a' (Unix's static (Archive) library), or '.so' (Unix's Shared Object library).

Native Libraries are to be kept in a directory accessible via JRE's Property 'java.library.path', which normally but not necessarily includes all the directories in the PATH environment variable.

Native libraries are not involved in the compilation. But if they are not properly included during runtime time, you will get a runtime error 'java.lang.UnsatisfiedLinkError: no xxx in java.library.path'.

To include external native libraries:

Copy the native libraries into a system library directory, e.g., c:windowssystem32 (Windows), /usr/lib or /usr/local/lib (macOS/Unix). You can verify that the directory is included in Java's System Property 'java.library.path', via System.out.println(System.getProperty('java.library.path')).

You can also set the native library path via the java's command-line option -Djava.library.path=xxx, for example,

Eclipse/NetBeans

Using an IDE can greatly simplifies inclusion of external packages. Read 'Eclipse How-To' or 'NetBeans How-To'.

Link to References & Resources

The type of installation depends on your requirement and the platform that you choose to install.

Depending on the requirement, download and install JDK or JRE according to the information provided in Table 1-1:

Table 1-1 Installation Requirements and Related Tasks

RequirementTasksRun Java programs but not develop themDownload and install the JRE for your platformDevelop Java applicationsDownload and install the Java Development Kit (JDK) for your platform. The JDK includes the JRE, so you do not have to download both separately.Use JRE on a server but do not want the ability to run rich internet applications (RIAs)Download the Java SE Server JRE for your platform

Version-String Format

To understand the version-string scheme that is used to distinguish various JDK and JRE releases, see Version-String Format.

Installation

JDK, JRE, and Server JRE can be installed on the following platforms:

You can download JDK and JRE from Java SE Development Kit Downloads page.

For supported processors and browsers, see Oracle JDK Certified System Configurations.

Oracle Solaris

Installation of JDK and JRE on Oracle Solaris: Instructions include installation from Image Packaging System (IPS) and Archive binaries.

Installing Server JRE 10 on Oracle Solaris: Instructions include steps to install Server JRE.

Microsoft Windows

Installation of the JDK and the JRE on Microsoft Windows Platforms: Instructions include steps to install JDK and JRE on 64-bit Microsoft Windows operating systems.

Linux

Installation of the JDK and JRE on Linux Platforms: Instructions include installation from Archive binaries and Red Hat Package Manager (RPM).

Installation of Server JRE 10 on Linux: Instructions include steps to install Server JRE on Linux.

Manual Installation and Registration of the Java Plug-in on Linux: Instructions include steps to manually install the JRE plug-in, which is required to run Java applets in a browser. This procedure does not apply to Server JRE installation.

MS Office 2016 product key, MS Office 2016 activator, MS Office 2016 free. download full version, MS Office 2016 crack, MS Office 2016 filehippo, MS Office 2016 activator free download, MS Office 2016 product key crack, MS Office 2016 price in pakistan, MS Office 2016 setup, MS Office 2016 keygen, MS Office 2016 download for pc, MS Office 2016 shortcut keys pdf, MS Office 2016. Download Microsoft Office 2016 Preview (32-bit) for Windows for free, without any viruses, from Uptodown. Try the latest version of Microsoft Office 2016 2015 for Windows. Free ms office 2016 zip file download. Office Tools downloads - Microsoft Office by Microsoft and many more programs are available for instant and free download. Ms office 2016 free download for pc.

macOS

Jre Macos Download

The installation of JRE 10 and JDK 10 requires macOS 10.10 or later.

Installation of the JDK and the JRE on macOS: Instructions include steps to install JDK and JRE on macOS platform.

To learn about the files and directories that are created after JDK and JRE installation, see Installed Directory Structure of JDK and JRE.

0 notes

mundoload109 · 4 years ago

Text

Install Xcode Command Line Tools From Terminal

Technical Note TN2339

Install Xcode Command Line Tools Terminal Catalina

Install Xcode Command Line Tools From Terminals

Install Xcode Command Line Tools Terminal Mojave

Simple command-line tool for showing the current weather in your terminal Project site: GitHub Author: @TheDayIsMyEnemy. Dotnet tool install -g weathercli: webtty: Simple command-line tool for sharing a terminal over the web. Project site: GitHub Author: @nickvdyck. Dotnet tool install -g webtty: weeknumber: Prints the current weeknumber to the. To develop Flutter apps for iOS, you need a Mac with Xcode installed. Install the latest stable version of Xcode (using web download or the Mac App Store). Configure the Xcode command-line tools to use the newly-installed version of Xcode by running the following from the command line. Apple's Command Line Developer Tools can be installed on recent OS versions by running this command in the Terminal: xcode-select -install. Older versions are found at the Apple Developer site, or they can be installed from within Xcode back to version 4. Users of Xcode 3 or earlier can install them by ensuring that the appropriate option(s. There are several ways to install Git on a Mac. In fact, if you've installed XCode (or it's Command Line Tools), Git may already be installed. To find out, open a terminal and enter git -version. $ git -version git version 2.7.0 (Apple Git-66).

This document provides answers to frequently asked questions about command line tools.

What is the Command Line Tools Package?

The Command Line Tools Package is a small self-contained package available for download separately from Xcode and that allows you to do command line development in macOS. It consists of the macOS SDK and command-line tools such as Clang, which are installed in the /Library/Developer/CommandLineTools directory.

Downloading command-line tools is not available in Xcode for macOS 10.9. How can I install them on my machine?

In macOS 10.9 and later, the Downloads pane of Xcode Preferences does not support downloading command-line tools. Use any of the following methods to install command-line tools on your system:

Install Xcode

If Xcode is installed on your machine, then there is no need to install them. Xcode comes bundled with all your command-line tools. macOS 10.9 and later includes shims or wrapper executables. These shims, installed in /usr/bin, can map any tool included in /usr/bin to the corresponding one inside Xcode. xcrun is one of such shims, which allows you to find or run any tool inside Xcode from the command line. Use it to invoke any tool within Xcode from the command line as shown in Listing 1.

Listing 1 Using xcrun to run dwarfdump in the Terminal application.

Download the Command Line Tools package from the Developer website

The Command Line Tools package is available for download on the Download for Apple Developers page. Log in with your Apple ID, then search and download the Command Line Tools package appropriate for your machine such as macOS 10.12 as shown in Figure 1.

Note: In macOS 10.9 and later, Software update notifies you when new versions of the command-line tools are available for update.

Install the Command Line Tools package via the Terminal application

You can install the Command Line Tools package by running the xcode-select --install command.

Note: macOS comes bundled with xcode-select, a command-line tool that is installed in /usr/bin. It allows you to manage the active developer directory for Xcode and other BSD development tools. See its man page for more information.

How can I uninstall the command-line tools?

Xcode includes all of the command-line tools. If it is installed on your system, remove it to uninstall the command-line tools.

If the /Library/Developer/CommandLineTools directory exists on your system, remove it to uninstall the command-line tools.

I have multiple versions of Xcode installed on my machine. What version of Xcode do the command-line tools currently use?

To find out what version of Xcode is being used by your tools, run the following command in Terminal:

Listing 2 Printing the version of Xcode currently used by the command-line tools.

How do I select the default version of Xcode to use for my command-line tools?

To select a default Xcode for your command-line tools, run the following command in Terminal:

where <path/to/> is the path to the Xcode.app package you wish to use for development.

Listing 3 Setting the default Xcode version.

How do I build my projects from the command line?

xcodebuild is a command-line tool that allows you to perform build, query, analyze, test, and archive operations on your Xcode projects and workspaces from the command line. It operates on one or more targets contained in your project, or a scheme contained in your project or workspace. xcodebuild provides several options for performing these operations as seen its man page. xcodebuild saves the output of your commands in the locations defined in the Locations preferences pane of your Xcode application, by default.

See below for various xcodebuild usage. Be sure to navigate to the directory containing your project or workspace in Terminal before running any of the following commands.

To list all schemes in your workspace, run the following command in Terminal:

where <your_workspace_name> is the name of your workspace.

Listing 4 Listing all schemes in the MyApplication workspace.

To list all targets, build configurations, and schemes used in your project, run the following command in Terminal:

where <your_project_name> is the name of your project.

Listing 5 Listing all information about MyProject, an Xcode project.

To build a scheme in your project, run the following command in Terminal:

where <your_scheme_name> and build are respectively the name of your scheme to be built and the action to be performed on your scheme.

Listing 6 Building the tvOS scheme.

Note: xcodebuild supports various build actions such as build, analyze, and archive that can be performed on your target or scheme. However, build is performed by default when no action is specified as shown in Listing 7.

To build your target with a configuration file, run the following command in Terminal:

where <your_target_name> and <your_configuration_file> are respectively the name of your target to be built and the name of your configuration file. See Xcode Help's Build configuration file reference for more information about xcconfig files.

Listing 7 Building the iOS target with a configuration file.

To change the output locations of your xcodebuild command, use the SYMROOT (Build Products Path) and DSTROOT (Installation Build Products Location) build settings that respectively specify a location for your debug products and .dSYM files and one for your released products. See Xcode Help's Build setting reference for more information about these build settings.

Listing 8 Setting up a location for iOS' debug app version.

Listing 9 Setting up a location for iOS's released app version.

My app has multiple build configurations. How do I set a default build configuration for xcodebuild?

In Xcode, the Configurations section of your project's Info pane provides a pop-up menu, which sets the default configuration to be used by xcodebuild when building a target. Use this pop-up menu to select a default build configuration for xcodebuild as seen in Figure 2.

How do I run unit tests from the command line?

xcodebuild provides several options for running unit tests.

To build and run unit tests from the command line, execute the following command in Terminal:

To build unit tests without running them from the command line, execute the following command in Terminal:

To run unit tests without building them from the command line, execute any of the following command in Terminal:

The test action requires specifying a scheme and a destination. See How do I implement the Build For Testing and Test Without Building features from the command line? for more information about build-for-testing and test-without-building actions.

Install Xcode Command Line Tools Terminal Catalina

The -workspace option allows you to specify the name of your workspace. Use this option when your scheme is contained in an Xcode workspace.

Install Xcode Command Line Tools From Terminals

The -project option allows you to specify the name of your Xcode project. Use this option when your scheme is contained in an Xcode project. It is required when there are multiple Xcode projects in the same directory and optional, otherwise.

Install Xcode Command Line Tools Terminal Mojave

The -destination option allows you to specify a destination for your unit tests. It takes an argument <destination-specifier>, which describes the device, simulator, or Mac to use as a destination. It consists of a set of comma-separated key=value pairs, which are dependent upon the the device, simulator, or Mac being used.

The -only-testing and -skip-testing options, which are optional, allow you to run only a specific test and to skip a test, respectively. They take an argument <test-identifier>, which specifies the test to be executed or excluded. test-identifier's format is as follows:

TestTarget, which is required, is the name of the test bundle. TestClass and TestMethod, which are both optional, respectively represent the name of the class and the name of the method to be tested.

Note: See Xcode Scheme and Run your app in Simulator for more information about scheme and destination, respectively.

For macOS apps, destinationspecifier supports the platform and arch keys as seen in Table 1. Both keys are required for running your unit tests in macOS.

Table 1 Supported keys for macOS apps.

Key

Ms office 2016 free download for mac. Description

Value

platform

Before we install OS X, we’ll need to set up VirtualBox so the OS X install disc can boot correctly. Here’s what you need to do: Step 1: Launch VirtualBox and click the New button. Give your new virtual machine a name (I just called it “Mac OS X”) and set the operating system to “Mac OS X Server (64-bit)”. No disk to install mac os x. How to Install Software on a Mac. So you've got a Mac, it's got so many cool programs out-of-the-box but you've got to have another program. But how do you install this sweet piece of a software on your Mac?

The supported destination for your unit tests.

macOS

arch

The architecture to use to run your unit tests.

i386 or x86_64

See Listing 10 for an example that tests a scheme in macOS and where destinationspecifier is set to 'platform=macOS,arch=x86_64'.

Listing 10 Tests the macOS scheme for 64-bit in macOS.

For iOS and tvOS apps, destinationspecifier supports the platform, name, and id keys as seen in Table 2.

Table 2 Supported keys for iOS and tvOS apps.

Key

Description

Value

platform

The supported destination for your unit tests.

iOS (for iOS apps)tvOS (for tvOS apps)

name

The full name of your device to be used for your unit tests.

The name of your device as displayed in the Devices Organizer in Xcode.

The identifier of your device to be used for your unit tests.

See Locate a device identifier for more information about getting your device identifier.

The name and id keys are intergeably used with platform, which is a required key as seen in Listing 11 and Listing 12.

Listing 11 Tests the iOS scheme on a device identified by 965058a1c30d845d0dcec81cd6b908650a0d701c.

Listing 12 Testing the iOSApp scheme on an iPhone.

Listing 13 Do not test iOSAppUITests on an iPhone.

Listing 14 Only testing SecondTestClass' testExampleB in the iOSAppTests unit test.

For iOS Simulator and tvOS Simulator apps, destinationspecifier supports the platform, name, id, and OS keys as seen in Table 3.

Table 3 Supported keys for iOS Simulator and tvOS Simulator apps.

Key

Description

Value

Before initiating a Mac OS E El Capitan download and installation, you need to ensure that your Mac can run the operating system. For starters, if your Mac is listed here below, it should be able to run the El Capitan operating system: Late 2008 or newer MacBook or MacBook Air; Mid 2007 MacBook Pro or iMac; Early 2009 or newer Mac Mini or XServe. If you're using OS X El Capitan v10.11.5 or later and your App Store preferences or Software Update preferences are set to download new updates when available, macOS Big Sur will download conveniently in the background, making it even easier to upgrade. A notification will inform you when macOS Big Sur is ready to be installed. Click Install to. Mac os 10.14 mojave download.

platform

The supported destination for your unit tests.

iOS Simulator (iOS apps)tvOS Simulator (tvOS apps)

name

The full name of the simulator (iOS simulator for iOS apps and tvOS Simulator for tvOS apps) to be used for your unit tests and as displayed in the run destination of your Xcode project.

The name of your device as displayed in the Devices Organizer in Xcode.

The identifier of your device to be used for your unit tests.

See Locate a device identifier for more information about getting your device identifier.

The version of iOS or tvOS to simulate such as 9.0 or the string latest to indicate the most recent version of iOS supported by your version of Xcode.

An iOS version, tvOS version, or latest

The name and id keys are intergeably used with platform, which is a required key as shown in Listing 15 and Listing 16. The OS key is optional.

Listing 15 Tests the iOS scheme on an iPad Pro (12.9 inch) with iOS 10.2 in the Simulator.

Listing 16 Tests the tvOS scheme on an tvOS Simulator identified by D6FA2C2A-E297-406A-AA22-624B4834ACB2.

The -destination option also allows you to run the same unit test on multiple destinations. This is done by adding it multiple times to your xcodebuild test command as demonstrated in Listing 17.

Listing 17 Tests the iOS scheme in both the Simulator and on an iPod touch.

Note: xcodebuild runs your tests sequentially. For instance In Listing 17, xcodebuild will first test iOS in the Simulator before executing it on the iPod touch.

How do I implement the Build For Testing and Test Without Building features from the command line?

xcodebuild provides the build-for-testing action for Xcode's Product > Build For > Testing feature. You must specify a scheme to use it. To use it, execute the following command in Terminal:

See How do I run unit tests from the command line? for more information about xcodebuild build-for-testing's options.

Listing 18 Builds tests and associated targets in the tvOS scheme using the tvOS Simulator identified by D6FA2C2A-E297-406A-AA22-624B4834ACB2.

build-for-testing generates an xctestrun file, which is saved in the derived data folder. See xcodebuild.xctestrun's man page for more information about xctestrun files.

xcodebuild provides the test-without-building action for Xcode's Product > Perform Action > Test Without Building feature. test-without-building requires that you specify either a scheme or an xctestrun file.

Usage when using a scheme

See How do I run unit tests from the command line? for more information about xcodebuild test-without-building's options.

Important: When using a scheme, test-without-building searches for bundles in the build root (SYMROOT). Therefore, be sure to build your target or that your build root includes the bundles to be tested before running this command. See Xcode Help's Build settings reference for more information about SYMROOT.

Listing 19 Tests the iOSApp scheme on an iPhone SE with iOS 10.1 in the Simulator.

Usage when using an xctestrun file

where <your_xctestrun_name> is the name of the file containing your test run parameters. See xcodebuild.xctestrun' s man page for more information about xctestrun files. See How do I run unit tests from the command line? for more information about the other options.

Important: When using an xctestrun file, test-without-building searches for bundles at paths specified in the file. Therefore, be sure that the bundles exist at the specified paths before running this command.

Listing 20 Testing bundles and other parameters specified in iOSApp_iphonesimulator.xctestrun using the iOS Simulator identified by 6DC4A7BA-EA7F-40D6-A327-A0A9DF82F7F6.

Listing 21 Tests everything but iOSAppUITests specified in iOSApp_iphonesimulator.xctestrun using the iOS Simulator identified by 3D95DF14-E8B7-4A05-B65B-78F381B74B22.

Note:build-for-testing and test-without-building provide support for continuous integration systems.

What keys can I pass to the exportOptionsPlist flag?

To get all available keys for -exportOptionsPlist, run the following command in Terminal:

Listing 22 Fetching all keys supported by -exportOptionsPlist.

See Figure 3 for a sample file that contains some options for the -exportOptionsPlist flag.

How do I archive and export my app for distribution?

To archive and export your app for distribution, run the following command in Terminal:

where <xcarchivepath> specifies the archive or the path of the archive to be exported, <destinationpath> specifies where to save the exported product, and <path> is the path to the file with a list of options for the -exportOptionsPlist flag.

Listing 23 Exports the iOSApp archive to the Release location with the options saved in the OptionsPlist.plist.

Document Revision History

DateNotes2017-06-19

Updated the 'How do I run unit tests from the command line?' question.Added the 'How do I implement the Build For Testing and Test Without Building features from the command line?' and 'What keys can I pass to the exportOptionsPlist flag?' questions.

2014-05-21

New document that provides answers to frequently asked questions about command-line tools.

0 notes

mundoload109 · 4 years ago

Text

Windows 10 Usb Installer Mac

Download Usb Drivers For Windows 10. Free and safe download. Download the latest version of the top software, games, programs and apps in 2021.

Windows 10 Usb Installer Macos

Windows 10 Usb Installer Macbook

Usb Universal Installer Windows 10

Macos Create Windows 10 Usb Installer

If you have Office 2010 or earlier and choose to perform a clean install of Windows 10, you will need to locate your Office product key. For tips on locating your product key, check Find your Office 2010 product key or Enter the product key for your Office 2007 program.

Download the Windows 10 ISO file. You can download the ISO file straight from Windows.

For instructions on creating macOS Catalina/ High Sierra USB installer, check: macOS USB.

Make Windows Bootable USB Mac with PassFab 4WinKey. Thinking about how do I.

What you need to install Windows 10 on Mac

MacBook introduced in 2015 or later

MacBook Air introduced in 2012 or later

MacBook Pro introduced in 2012 or later

Mac mini introduced in 2012 or later

iMac introduced in 2012 or later1

iMac Pro (all models)

Mac Pro introduced in 2013 or later

The latest macOS updates, which can include updates to Boot Camp Assistant. You will use Boot Camp Assistant to install Windows 10.

64GB or more free storage space on your Mac startup disk:

Your Mac can have as little as 64GB of free storage space, but at least 128GB of free storage space provides the best experience. Automatic Windows updates require that much space or more.

If you have an iMac Pro or Mac Pro with 128GB of memory (RAM) or more, your startup disk needs at least as much free storage space as your Mac has memory.2

An external USB flash drive with a storage capacity of 16GB or more, unless you're using a Mac that doesn't need a flash drive to install Windows.

A 64-bit version of Windows 10 Home or Windows 10 Pro on a disk image (ISO) or other installation media. If installing Windows on your Mac for the first time, this must be a full version of Windows, not an upgrade.

If your copy of Windows came on a USB flash drive, or you have a Windows product key and no installation disc, download a Windows 10 disk image from Microsoft.

If your copy of Windows came on a DVD, you might need to create a disk image of that DVD.

How to install Windows 10 on Mac

To install Windows, use Boot Camp Assistant, which is included with your Mac.

No disk available to install mac os x. Storage: At least 400 Mbytes available disk space for a default install via download. Graphics: 1024 x 768 or higher resolution with 16.7 million colours. Additional Resources. Click here to download; Click here to get install instructions for OpenOffice on macOS; Click here to get help and support in the Community Support Forums. Before we install OS X, we’ll need to set up VirtualBox so the OS X install disc can boot correctly. Here’s what you need to do: Step 1: Launch VirtualBox and click the New button. Give your new virtual machine a name (I just called it “Mac OS X”) and set the operating system to “Mac OS X Server (64-bit)”. Run it and install darktable. Download the latest DMG disk image for darktable; Mount the thing; Pull the darktable icon into applications folder; Good luck:) This bundle supports macOS versions starting with 10.7 (Lion) running on 64 bit Intel architecture. If you have an iMac Pro or Mac Pro with 128GB of memory (RAM) or more, your startup disk needs at least as much free storage space as your Mac has memory. 2 An external USB flash drive with a storage capacity of 16GB or more, unless you're using a Mac that doesn't need a flash drive to install Windows. How to Install Software on a Mac. So you've got a Mac, it's got so many cool programs out-of-the-box but you've got to have another program. But how do you install this sweet piece of a software on your Mac?

Ms office 2016 for mac free download. MS Office 2016 product key, MS Office 2016 activator, MS Office 2016 free. download full version, MS Office 2016 crack, MS Office 2016 filehippo, MS Office 2016 activator free download, MS Office 2016 product key crack, MS Office 2016 price in pakistan, MS Office 2016 setup, MS Office 2016 keygen, MS Office 2016 download for pc, MS Office 2016 shortcut keys pdf, MS Office 2016.

1. Check your Secure Boot setting

Learn how to check your Secure Boot setting. The default Secure Boot setting is Full Security. If you changed it to No Security, change it back to Full Security before installing Windows. After installing Windows, you can use any Secure Boot setting without affecting your ability to start up from Windows.

2. Use Boot Camp Assistant to create a Windows partition

Open Boot Camp Assistant, which is in the Utilities folder of your Applications folder. Follow the onscreen instructions.

If you're asked to insert a USB drive, plug your USB flash drive into your Mac. Boot Camp Assistant will use it to create a bootable USB drive for Windows installation.

When Boot Camp Assistant asks you to set the size of the Windows partition, remember the minimum storage-space requirements in the previous section. Set a partition size that meets your needs, because you can't change its size later.

3. Format the Windows (BOOTCAMP) partition

When Boot Camp Assistant finishes, your Mac restarts to the Windows installer. If the installer asks where to install Windows, select the BOOTCAMP partition and click Format. In most cases, the installer selects and formats the BOOTCAMP partition automatically.

4. Install Windows

Unplug any external devices that aren't necessary during installation. Then click Next and follow the onscreen instructions to begin installing Windows.

5. Use the Boot Camp installer in Windows

After Windows installation completes, your Mac starts up in Windows and opens a ”Welcome to the Boot Camp installer” window. Follow the onscreen instructions to install Boot Camp and Windows support software (drivers). You will be asked to restart when done.

If the Boot Camp installer never opens, open the Boot Camp installer manually and use it to complete Boot Camp installation.

If you have an external display connected to a Thunderbolt 3 port on your Mac, the display will be blank (black, gray, or blue) for up to 2 minutes during installation.

How to switch between Windows and macOS

Restart, then press and hold the Option (or Alt) ⌥ key during startup to switch between Windows and macOS.

Windows 10 Usb Installer Macos

Learn more

Windows 10 Usb Installer Macbook

If you have one of these Intel-based Mac models using OS X El Capitan or later, you don't need a USB flash drive to install Windows:

MacBook introduced in 2015 or later

MacBook Air introduced in 2017 or later3

MacBook Pro introduced in 2015 or later3

iMac introduced in 2015 or later

iMac Pro (all models)

Mac Pro introduced in late 2013 or later

To remove Windows from your Mac, use Boot Camp Assistant, not any other utility.

Usb Universal Installer Windows 10

For more information about using Windows on your Mac, open Boot Camp Assistant and click the Open Boot Camp Help button.

1. If you're using an iMac (Retina 5K, 27-inch, Late 2014) or iMac (27-inch, Late 2013) or iMac (27-inch, Late 2012) with a 3TB hard drive and macOS Mojave or later, learn about an alert you might see during installation.

2. For example, if your Mac has 128GB of memory, its startup disk must have at least 128GB of storage space available for Windows. To see how much memory your Mac has, choose Apple menu  > About This Mac. To see how much storage space is available, click the Storage tab in the same window.

Macos Create Windows 10 Usb Installer

3. These Mac models were offered with 128GB hard drives as an option. Apple recommends 256GB or larger hard drives so that you can create a Boot Camp partition of at least 128GB.

0 notes