MAC OSX Tips

Total Page:16

File Type:pdf, Size:1020Kb

MAC OSX Tips Table of Contents MAC OSX tips keys linux-like environment and FINK MacPorts tips Build from source VS use binaries Useful commands MAC OSX tips Overview Some tips and hints on MacOSX usage: tame your keyboard and go ahead with compilation. edit 1414069126 [MAC OSX tips] section 1-168 1/8 documentation:tools:macosx_tips Edit keys quick copy and paste with CMD touch + c and + v key pipe | : alt + Maj + l tilde ~: alt +n square brackets [ or ]: alt + Maj + ( or ) antislash \:alt + maj + : edit 1414069126 [keys] section 169-383 documentation:tools:macosx_tips Edit linux-like environment and FINK 2/8 What is Fink? Fink is a distribution of Unix Open Source software for Mac OS X and Darwin. It brings a wide range of free command-line and graphical software developed for Linux and similar operating systems to your Mac. Quick Start Download the installer disk image: Fink 0.9.0 Binary Installer Double-click ?Fink-0.9.0-XYZ-Installer.dmg? to mount the disk image, then double-click the ?Fink 0.9.0 XYZ Installer.pkg? package inside. Follow the instructions on screen. At the end of the installation, the pathsetup utility will be launched. You will be asked for permission before your shell's configuration files are edited. When the utility has finished, you are set to go! Using the fink tool The fink tool uses several suffix commands to work on packages from the source distribution. Some of them need at least one package name, but can handle several package names at once. You can specify just the package name (e.g. gimp), or a fully qualified name with a version number (e.g. gimp-1.2.1) or with both version and revision numbers (e.g. gimp-1.2.1-3). Fink will automatically choose the latest available version and revision when they are not specified. Others have different options. If you type : fink --help you get the list of options. Install The install command is used to install packages. It downloads, configure, builds and installs the packages you name. It will also install required dependencies automatically, but will ask you for confirmation before it does so. Example: fink install nedit Reading package info... Information about 131 packages read. The following additional package will be installed: lesstif Do you want to continue? [Y/n] Remove The remove command removes packages from the system by calling : 'dpkg --remove' The current default implementation has a flaw: it doesn't check dependencies itself but rather completely leaves that to the dpkg tool (usually this poses no problem, though). The remove command only removes the actual package files, (excluding configuration files), but leaves the .deb compressed package file intact. This means that you can re-install the package later without going through the compile process again. If you need the disk space, you can remove the .deb from the /sw/fink/dists tree. These flags can be used with the fink remove command 3/8 -h,--help - Show the options which are available. -r,--recursive - Also remove packages that depend on the package(s) to be removed (i.e. overcome the above-mentioned flaw). Purge The purge command purges packages from the system. This is the same as the remove command except that it removes configuration files as well. This command takes the: -h,--help -r,--recursive options. Update-all This command updates all installed packages to the latest version. It does not need a package list, so you just type: fink update-all List This command produces a list of available packages, listing installation status, the latest version and a short description. If you call it without parameters, it will list all available packages. You can also pass a name or a shell pattern, and fink will list all packages that match. The first column displays the installation state with the following meanings: not installed i latest version is installed (i) installed, but a newer version is available p a virtual package provided by a package that is installed The version column always lists the latest (highest) version known for the package, regardless of what version (if any) you have installed. To see all versions of a package available on your system, use the dumpinfo command. There are also some flags for the fink list command: -h,--help Show the options which are available. -t,--tab Output the list in a tab delimited format, useful for running the output through a script. -i,--installed Show only those packages which are currently installed. -o,--outdated Show only those packages which are out of date. -u,--uptodate Show only packages which are up to date. -n,--notinstalled Show packages which are not currently installed. -s expr,--section=expr Show only packages in the sections matching the regular 4/8 expression expr. -m expr,--maintainer=expr Show only packages with the maintainer matching the regular expression expr. -w=xyz,--width=xyz Sets the width of the display you would like the output formatted for. xyz is either a numeric value or auto. auto will set the width based on the terminal width. The default is auto. Some usage examples: fink list - list all packages fink list bash - check if bash is available and what version. fink list --tab --outdated | cut -f 2 - just list the names of the out of date packages. fink list --section=kde - list the packages in the kde section fink list --maintainer=fink-devel - list the packages with no maintainer fink --trees=unstable list --maintainer=fink-devel - list the packages with no maintainer, but only in the unstable tree. fink list "gnome*" - list all packages that start with 'gnome' The quotes in the last example are necessary to stop the shell from interpreting the pattern itself. More information on : Fink Project Home edit 1414069126 [linux-like environment andsection FINK] 384-6204 5/8 documentation:tools:macosx_tips Edit MacPorts tips edit 1414069126 [MacPorts tips] section 6205-6232 documentation:tools:macosx_tips Edit Build from source VS use binaries There is a setting called buildfromsource in the configuration file 6/8 /opt/local/etc/macports/macports.conf that controls the use of pre-built archives. edit 1414069126 [Build from source VS usesection binaries] 6233-6437 documentation:tools:macosx_tips Edit Useful commands # Uninstall all ports port -fp uninstall installed # Select which compiler/python/... you want to use : port select --list GROUP port select --set GROUP value #for example: port select --set gcc mp-gcc42 7/8 see also Using the right compiler edit 1414069126 [Useful commands] section 6438- documentation:tools:macosx_tips Edit 8/8.
Recommended publications
  • Opensource Software in Mac OS X V. Zhhuta
    Foss Lviv 2013 191 - Linux VM з Wordpress на Azure під’єднано до SQL-бази в приватному центрі обробки даних. Як бачимо, бізнес Microsoft вже дуже сильно зав'язаний на Open Source! Далі в доповіді будуть розглянуті подробиці інтероперабельності платформ з Linux Server, Apache Hadoop, Java, PHP, Node.JS, MongoDb, і наостанок дізнаємося про цікаві Open Source-розробки Microsoft Research. OpenSource Software in Mac OS X V. Zhhuta UK2 LImIted t/a VPS.NET, [email protected] Max OS X stem from Unix: bSD. It contains a lot of things that are common for Unix systems. Kernel, filesystem and base unix utilities as well as it's own package managers. It's not a secret that Mac OS X has a bSD kernel Darwin. The raw Mac OS X won't provide you with all power of Unix but this could be easily fixed: install package manager. There are 3 package manager: MacPorts, Fink and Homebrew. To dive in OpenSource world of mac os x we would try to install lates version of bash, bash-completion and few other utilities. Where we should start? First of all you need to install on you system dev-tools: Xcode – native development tools that contain GCC and libraries. Next step: bring a GIU – X11 into your system. Starting from Mac OS 10.8 X11 is not included in base-installation and it's need to install Xquartz(http://xquartz.macosforge.org). Now it's time to look closely to package managers MacPorts Site: www.macports.org Latest MacPorts release: 2.1.3 Number of ports: 16740 MacPorts born inside Apple in 2002.
    [Show full text]
  • Xcode Package from App Store
    KH Computational Physics- 2016 Introduction Setting up your computing environment Installation • MAC or Linux are the preferred operating system in this course on scientific computing. • Windows can be used, but the most important programs must be installed – python : There is a nice package ”Enthought Python Distribution” http://www.enthought.com/products/edudownload.php – C++ and Fortran compiler – BLAS&LAPACK for linear algebra – plotting program such as gnuplot Kristjan Haule, 2016 –1– KH Computational Physics- 2016 Introduction Software for this course: Essentials: • Python, and its packages in particular numpy, scipy, matplotlib • C++ compiler such as gcc • Text editor for coding (for example Emacs, Aquamacs, Enthought’s IDLE) • make to execute makefiles Highly Recommended: • Fortran compiler, such as gfortran or intel fortran • BLAS& LAPACK library for linear algebra (most likely provided by vendor) • open mp enabled fortran and C++ compiler Useful: • gnuplot for fast plotting. • gsl (Gnu scientific library) for implementation of various scientific algorithms. Kristjan Haule, 2016 –2– KH Computational Physics- 2016 Introduction Installation on MAC • Install Xcode package from App Store. • Install ‘‘Command Line Tools’’ from Apple’s software site. For Mavericks and lafter, open Xcode program, and choose from the menu Xcode -> Open Developer Tool -> More Developer Tools... You will be linked to the Apple page that allows you to access downloads for Xcode. You wil have to register as a developer (free). Search for the Xcode Command Line Tools in the search box in the upper left. Download and install the correct version of the Command Line Tools, for example for OS ”El Capitan” and Xcode 7.2, Kristjan Haule, 2016 –3– KH Computational Physics- 2016 Introduction you need Command Line Tools OS X 10.11 for Xcode 7.2 Apple’s Xcode contains many libraries and compilers for Mac systems.
    [Show full text]
  • Fulltext PDF 3,1 MB
    alpaka Parallel Programming – Online Tutorial Lecture 00 – Getting Started with alpaka Lesson 04: Installation www.casus.science Lesson 04: Installation How to download alpaka ● Install git for your operating system: ● Linux: sudo dnf install git (RPM) or sudo apt install git (DEB) ● macOS: Enter git --version in your terminal, you will be asked if you want to install git ● Windows: Download the installer from https://git-scm.com/download/win ● Open the terminal (Linux / macOS) or PowerShell (Windows) ● Navigate to a directory of your choice: cd /path/to/some/directory ● Download alpaka: git clone -b release-0.5.0 https://github.com/alpaka-group/alpaka.git alpaka Parallel Programming – Online Tutorial – Lesson 04: Installation | 2 Lesson 04: Installation Install alpaka’s dependencies ● alpaka only requires Boost and a modern C++ compiler (g++, clang++, Visual C++, …) ● Linux: ● sudo dnf install boost-devel (RPM) ● sudo apt install libboost-all-dev (DEB) ● macOS: ● brew install boost (Using Homebrew, https://brew.sh) ● sudo port install boost (Using MacPorts, https://macports.org) ● Windows: vcpkg install boost (Using vcpkg, https://github.com/microsoft/vcpkg) ● Depending on your target platform you may need additional packages ● NVIDIA GPUs: CUDA Toolkit (https://developer.nvidia.com/cuda-toolkit) ● AMD GPUs: ROCm / HIP (https://rocmdocs.amd.com/en/latest/index.html) alpaka Parallel Programming – Online Tutorial – Lesson 04: Installation | 3 Lesson 04: Installation Preparing alpaka for installation, Part 1 ● CMake is the preferred system
    [Show full text]
  • About Basictex-2021
    About BasicTeX-2021 Richard Koch January 2, 2021 1 Introduction Most TeX distributions for Mac OS X are based on TeX Live, the reference edition of TeX produced by TeX User Groups across the world. Among these is MacTeX, which installs the full TeX Live as well as front ends, Ghostscript, and other utilities | everything needed to use TeX on the Mac. To obtain it, go to http://tug.org/mactex. 2 Basic TeX BasicTeX (92 MB) is an installation package for Mac OS X based on TeX Live 2021. Unlike MacTeX, this package is deliberately small. Yet it contains all of the standard tools needed to write TeX documents, including TeX, LaTeX, pdfTeX, MetaFont, dvips, MetaPost, and XeTeX. It would be dangerous to construct a new distribution by going directly to CTAN or the Web and collecting useful style files, fonts and so forth. Such a distribution would run into support issues as the creators move on to other projects. Luckily, the TeX Live install script has its own notion of \installation packages" and collections of such packages to make \installation schemes." BasicTeX is constructed by running the TeX Live install script and choosing the \small" scheme. Thus it is a subset of the full TeX Live with exactly the TeX Live directory structure and configuration scripts. Moreover, BasicTeX contains tlmgr, the TeX Live Manager software introduced in TeX Live 2008, which can install additional packages over the network. So it will be easy for users to add missing packages if needed. Since it is important that the install package come directly from the standard TeX Live distribution, I'm going to explain exactly how I installed TeX to produce the install package.
    [Show full text]
  • The TEX Live Guide TEX Live 2012
    The TEX Live Guide TEX Live 2012 Karl Berry, editor http://tug.org/texlive/ June 2012 Contents 1 Introduction 2 1.1 TEX Live and the TEX Collection...............................2 1.2 Operating system support...................................3 1.3 Basic installation of TEX Live.................................3 1.4 Security considerations.....................................3 1.5 Getting help...........................................3 2 Overview of TEX Live4 2.1 The TEX Collection: TEX Live, proTEXt, MacTEX.....................4 2.2 Top level TEX Live directories.................................4 2.3 Overview of the predefined texmf trees............................5 2.4 Extensions to TEX.......................................6 2.5 Other notable programs in TEX Live.............................6 2.6 Fonts in TEX Live.......................................7 3 Installation 7 3.1 Starting the installer......................................7 3.1.1 Unix...........................................7 3.1.2 MacOSX........................................8 3.1.3 Windows........................................8 3.1.4 Cygwin.........................................9 3.1.5 The text installer....................................9 3.1.6 The expert graphical installer.............................9 3.1.7 The simple wizard installer.............................. 10 3.2 Running the installer...................................... 10 3.2.1 Binary systems menu (Unix only).......................... 10 3.2.2 Selecting what is to be installed...........................
    [Show full text]
  • Teamcity 7.1 Documentation.Pdf
    1. TeamCity Documentation . 4 1.1 What's New in TeamCity 7.1 . 5 1.2 What's New in TeamCity 7.0 . 14 1.3 Getting Started . 26 1.4 Concepts . 30 1.4.1 Agent Home Directory . 31 1.4.2 Agent Requirements . 32 1.4.3 Agent Work Directory . 32 1.4.4 Authentication Scheme . 33 1.4.5 Build Agent . 33 1.4.6 Build Artifact . 34 1.4.7 Build Chain . 35 1.4.8 Build Checkout Directory . 36 1.4.9 Build Configuration . 37 1.4.10 Build Configuration Template . 38 1.4.11 Build Grid . 39 1.4.12 Build History . 40 1.4.13 Build Log . 40 1.4.14 Build Number . 40 1.4.15 Build Queue . 40 1.4.16 Build Runner . 41 1.4.17 Build State . 41 1.4.18 Build Tag . 42 1.4.19 Build Working Directory . 43 1.4.20 Change . 43 1.4.21 Change State . 43 1.4.22 Clean Checkout . 44 1.4.23 Clean-Up . 45 1.4.24 Code Coverage . 46 1.4.25 Code Duplicates . 47 1.4.26 Code Inspection . 47 1.4.27 Continuous Integration . 47 1.4.28 Dependent Build . 47 1.4.29 Difference Viewer . 49 1.4.30 Guest User . 50 1.4.31 History Build . 51 1.4.32 Notifier . 51 1.4.33 Personal Build . 52 1.4.34 Pinned Build . 52 1.4.35 Pre-Tested (Delayed) Commit . 52 1.4.36 Project . 53 1.4.37 Remote Run . ..
    [Show full text]
  • The Apple Ecosystem
    APPENDIX A The Apple Ecosystem There are a lot of applications used to manage Apple devices in one way or another. Additionally, here’s a list of tools, sorted alphabetically per category in order to remain vendor agnostic. Antivirus Solutions for scanning Macs for viruses and other malware. • AVG: Basic antivirus and spyware detection and remediation. • Avast: Centralized antivirus with a cloud console for tracking incidents and device status. • Avira: Antivirus and a browser extension. Avira Connect allows you to view device status online. • BitDefender: Antivirus and malware managed from a central console. • CarbonBlack: Antivirus and Application Control. • Cylance: Ransomware, advanced threats, fileless malware, and malicious documents in addition to standard antivirus. • Kaspersky: Antivirus with a centralized cloud dashboard to track device status. © Charles Edge and Rich Trouton 2020 707 C. Edge and R. Trouton, Apple Device Management, https://doi.org/10.1007/978-1-4842-5388-5 APPENDIX A THe AppLe ECOSYSteM • Malware Bytes: Antivirus and malware managed from a central console. • McAfee Endpoint Security: Antivirus and advanced threat management with a centralized server to track devices. • Sophos: Antivirus and malware managed from a central console. • Symantec Mobile Device Management: Antivirus and malware managed from a central console. • Trend Micro Endpoint Security: Application whitelisting, antivirus, and ransomware protection in a centralized console. • Wandera: Malicious hot-spot monitoring, jailbreak detection, web gateway for mobile threat detection that integrates with common MDM solutions. Automation Tools Scripty tools used to automate management on the Mac • AutoCasperNBI: Automates the creation of NetBoot Images (read: NBI’s) for use with Casper Imaging. • AutoDMG: Takes a macOS installer (10.10 or newer) and builds a system image suitable for deployment with Imagr, DeployStudio, LANrev, Jamf Pro, and other asr or Apple Systems Restore-based imaging tools.
    [Show full text]
  • Webroot Secureanywhere® Business – DNS Protection Apache License 2.0 • Aws-Sdk-Net Copyright © Amazon.Com, Inc. Apache
    Webroot SecureAnywhere® Business – DNS Protection Apache License 2.0 • aws-sdk-net Copyright © Amazon.com, Inc. Apache License Version 2.0, January 2004 TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License. “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. “Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
    [Show full text]
  • Building Gplates from Source on Mac OS X Without Package Managers
    Building GPlates from source on Mac OS X without package managers Christian Heine∗ Revision: 1067 Date: 2009-02-26 February 26, 2009 Abstract This article describes how to build the open-source plate tectonic software GPlates on Mac OS X without the need of package managers like MacPorts or Fink. The pro- cedure uses available installer packages for OS X from the net and only requires to compile one single library from source. I have been able to install GPlates smoothly on a Mac Pro and oldish 12” PowerBook using the recipe below. 1 For the impatient This is for the impatient ones which don’t need lengthy explanations: • Install XCode from the Mac Dev Center • Install the GDAL framework and dependancies from William Kyngesbury’s site • Install CMake from the CMake project • Install the Qt framework from Trolltech • Download and compile the ICU libaries from the ICU Project • Download and unarchive the Boost libaries • Download and unarchive the GPlates source • Open CMake.app and point it to the directory where you unarchived the GPlates source code. • Configure GPlates build in CMake.app • Compile GPlates in Terminal.app by typing make in the GPlates source direc- tory. ∗Email: [email protected] 1 Heine BuildingGPlatesOnOSX 20090226.tex 1067 2009-02-26 21:24:04Z christian 2 Prerequisites This build requires that you have basic familiarity with the command line and the Terminal on Mac OS X using Terminal.app. In order to be able to compile some of the components, it is required to have a c++ compiler installed on your machine.
    [Show full text]
  • CDE: Run Any Linux Application On-Demand Without Installation
    CDE: Run Any Linux Application On-Demand Without Installation Philip J. Guo Stanford University [email protected] Abstract with compiling, installing, and configuring software and their myriad of dependencies. For example, the official There is a huge ecosystem of free software for Linux, but Google Chrome help forum for “install/uninstall issues” since each Linux distribution (distro) contains a differ- has over 5800 threads. ent set of pre-installed shared libraries, filesystem layout In addition, a study of US labor statistics predicts that conventions, and other environmental state, it is difficult by 2012, 13 million American workers will do program- to create and distribute software that works without has- ming in their jobs, but amongst those, only 3 million will sle across all distros. Online forums and mailing lists be professional software developers [24]. Thus, there are are filled with discussions of users’ troubles with com- potentially millions of people who still need to get their piling, installing, and configuring Linux software and software to run on other machines but who are unlikely their myriad of dependencies. To address this ubiqui- to invest the effort to create one-click installers or wres- tous problem, we have created an open-source tool called tle with package managers, since their primary job is not CDE that automatically packages up the Code, Data, and to release production-quality software. For example: Environment required to run a set of x86-Linux pro- grams on other x86-Linux machines. Creating a CDE • System administrators often hack together ad- package is as simple as running the target application un- hoc utilities comprised of shell scripts and custom- der CDE’s monitoring, and executing a CDE package re- compiled versions of open-source software, in or- quires no installation, configuration, or root permissions.
    [Show full text]
  • Beginning System Administration Decal
    Review Installing Software Debian GNU/Linux Beginning System Administration DeCal Week 6 March 03, 2009 Week 6 Beginning System Administration DeCal Review Installing Software Debian GNU/Linux Review So Far... (hopefully) History of UNIX Design choices Terminal, shell, and interaction with UNIX Foundation of the Internet Using UNIX Users and Permissions Account management (add/del/disable users) File system layout Week 6 Beginning System Administration DeCal Review Installing Software Debian GNU/Linux Review So Far... (cont.) Software Downloading and extracting packages ( wget, tar, gzip) Configuring and compiling (./configure, make, make install) Configuration (.conf files, /etc) Week 6 Beginning System Administration DeCal Review Considerations Installing Software Package Managers Debian GNU/Linux Software Two options: 1 compile from source 2 download and install from binaries download binaries manually use a package management system How about both? When to choose which? Software release cycle Security and feature patches Week 6 Beginning System Administration DeCal Review Considerations Installing Software Package Managers Debian GNU/Linux What’s the single biggest advancement Linux has brought to the industry? It’s an interesting question, and one that in my opinion has a very simple answer: Package management-or, more specifically, the ability to install and upgrade software over the network in a seamlessly integrated fashion-along with the distributed development model package management enabled. Ian Murdock (founder of Debian) http://ianmurdock.com/2007/07/21/how-package-management-changed-everything/
    [Show full text]
  • Running Digital Micrograph on Linux and Mac OSX
    Downloaded from Running Digital Micrograph on Linux and Mac OSX https://www.cambridge.org/core Robert Hovden School of Applied and Engineering Physics, Cornell University, Ithaca, NY 14853 [email protected] Introduction that allows Unix-like operating systems to execute . IP address: Gatan Digital Micrograph (DM) software is considered programs written for Microsoft Windows. Wine provides a an industry standard among microscopists. The offline DM compatibility layer that allows Windows system calls to be run on a substitute operating system. As stated by internal application is freely available from Gatan [1]. Unfortunately, 170.106.202.58 DM software has been designed to run only on Microsoft Wine admins, “You can start your Windows application Windows operating systems, thus distancing the microscopy straight from your regular desktop environment, place that community from popular Unix-based systems, such as Linux application’s window side by side with native applications, or Mac OSX. An ad hoc solution to this problem has required copy/paste from one to the other, and run it all at full speed” , on a virtualized Windows operating system running on top [2]. After installing Wine and the necessary Microsoft 28 Sep 2021 at 14:01:56 of the user’s native operating system. This is not only slow, components, DM runs readily on Linux or OSX. The software having to emulate each processor instruction, but also requires has been tested using the offline DM V2.01 demo provided installation and licensing of Windows and the virtualization by Gatan. software. However, with the aid of open-source resources, it The steps for a Linux system are nearly identical and is possible to run DM natively on Linux and Mac OSX (Figure simpler than OSX, so the remainder of this guide is addressed , subject to the Cambridge Core terms of use, available at 1).
    [Show full text]