Getting Started with Perl on Mac OS X Preparing for Perl. All you will need for this primer is a text editor, the terminal, and Perl (of course!). Your First Perl Command. Before we start writing code, let's take a look at the version of Perl we have installed. Creating a Perl. Mac OS X already has Perl installed. Open a Terminal application (in the Utilities folder of your Applications folder) and run perl -v to find out which version. ActiveState Perl has binary distributions of Perl for Mac OS X. This is the simplest way to install the latest version of Perl. Download ActivePerl.
Unix Binary Release • Mac OS X Binary Release • iOS Binary Release • Windows Binary Release
You can install ImageMagick from source. However, if you don't have a proper development environment or if you're anxious to get started, download a ready-to-run Unix or Windows executable. Before you download, you may want to review recent changes to the ImageMagick distribution.
ImageMagick source and binary distributions are available from a variety of FTP and Web mirrors around the world.
Unix Binary Release
Perl Macos Catalina
These are the Unix variations that we support. If your system is not on the list, try installing from source. Although ImageMagick runs fine on a single core computer, it automagically runs in parallel on multi-core systems reducing run times considerably.
| Version | Description |
|---|---|
| magick | Complete portable application on Linux, no installation required. Just download and run. AppImages require FUSE to run. Many distributions have a working FUSE setup out-of-the-box. However if it is not working for you, you may need to install and configure FUSE manually. |
| ImageMagick-7.0.10-34.x86_64.rpm | Redhat / CentOS 7.1 x86_64 RPM |
| ImageMagick-libs-7.0.10-34.x86_64.rpm | Redhat / CentOS 7.1 x86_64 RPM |
| ImageMagick RPM's | Development, Perl, C++, and documentation RPM's. |
| ImageMagick-i386-pc-solaris2.11.tar.gz | Solaris Sparc 2.11 |
| ImageMagick-i686-pc-cygwin.tar.gz | Cygwin |
| ImageMagick-i686-pc-mingw32.tar.gz | MinGW |
Verify its message digest.
ImageMagick RPM's are self-installing. Simply type the following command and you're ready to start using ImageMagick:
You'll need the libraries as well:
Note, if there are missing dependencies, install them from the EPEL repo.
For other systems, create (or choose) a directory to install the package into and change to that directory, for example:
Next, extract the contents of the package. For example:
Set the MAGICK_HOME environment variable to the path where you extracted the ImageMagick files. For example:
If the bin subdirectory of the extracted package is not already in your executable search path, add it to your PATH environment variable. For example:
On Linux and Solaris machines add $MAGICK_HOME/lib to the LD_LIBRARY_PATH environment variable:
Finally, to verify ImageMagick is working properly, type the following on the command line:
Congratulations, you have a working ImageMagick distribution under Unix or Linux and you are ready to use ImageMagick to convert, compose, or edit your images or perhaps you'll want to use one of the Application Program Interfaces for C, C++, Perl, and others.
Mac OS X Binary Release
We recommend Homebrew which custom builds ImageMagick in your environment (some users prefer MacPorts). Download HomeBrew and type:
ImageMagick depends on Ghostscript fonts. To install them, type:
The brew command downloads ImageMagick and many of its delegate libraries (e.g. JPEG, PNG, Freetype, etc.) and configures, builds, and installs ImageMagick automagically. Alternatively, you can download the ImageMagick Mac OS X distribution we provide:
| Version | Description |
|---|---|
| ImageMagick-x86_64-apple-darwin19.6.0.tar.gz | macOS High Sierra |
Verify its message digest.
Create (or choose) a directory to install the package into and change to that directory, for example:
Next, extract the contents of the package. For example:
Set the MAGICK_HOME environment variable to the path where you extracted the ImageMagick files. For example:
If the bin subdirectory of the extracted package is not already in your executable search path, add it to your PATH environment variable. For example:
Set the DYLD_LIBRARY_PATH environment variable:
Finally, to verify ImageMagick is working properly, type the following on the command line:
Note, the display program requires the X11 server available on your Mac OS X installation DVD. Once that is installed, you will also need to set export DISPLAY=:0.
The best way to deal with all the exports is to put them at the end of your .profile file
Congratulations, you have a working ImageMagick distribution under Mac OS X and you are ready to use ImageMagick to convert, compose, or edit your images or perhaps you'll want to use one of the Application Program Interfaces for C, C++, Perl, and others.
iOS Binary Release
~Claudio provides iOS builds of ImageMagick.
Download iOS Distribution
You can download the iOS distribution directly from ImageMagick's repository.
There are always 2 packages for the compiled ImageMagick:
- iOSMagick-VERSION-libs.zip
- iOSMagick-VERSION.zip
The first one includes headers and compiled libraries that have been used to compile ImageMagick. Most users would need this one.
ImageMagick compiling script for iOS OS and iOS Simulator
To run the script:
where VERSION is the version of ImageMagick you want to compile (i.e.: 7.0.10-34, svn, ...)
This script compiles ImageMagick as a static library to be included in iOS projects and adds support for
- png
- jpeg
- tiff
Upon successful compilation a folder called IMPORT_ME is created on your ~/Desktop. You can import it into your Xcode project.
Xcode project settings
After including everything into Xcode please also make sure to have these settings (Build tab of the project information):
- Other Linker Flags: -lMagickCore-Q16 -lMagickWand-Q16 -ljpeg -lpng -lbz2 -lz
- Header Search Paths: $(SRCROOT) - make it Recursive
- Library Search Paths: $(SRCROOT) - make it Recursive
On the lower left click on the small-wheel and select: Add User-Defined Setting
- Key: OTHER_CFLAGS
- Value: -Dmacintosh=1
Sample project
A sample project is available for download. It is not updated too often, but it does give an idea of all the settings and some ways to play around with ImageMagick in an iOS application.
Windows Binary Release
ImageMagick runs on Windows 10 (x86 & x64), Windows 8 (x86 & x64), Windows 7 (x86 & x64), Windows Server 2012, Windows Vista (x86 & x64) with Service Pack 2, Windows Server 2008 (x86 & x64) with Service Pack 2, and Windows Server 2008 R2 (x64).
The amount of memory can be an important factor, especially if you intend to work on large images. A minimum of 512 MB of RAM is recommended, but the more RAM the better. Although ImageMagick runs well on a single core computer, it automagically runs in parallel on multi-core systems reducing run times considerably.
The Windows version of ImageMagick is self-installing. Simply click on the appropriate version below and it will launch itself and ask you a few installation questions. Versions with Q8 in the name are 8 bits-per-pixel component (e.g. 8-bit red, 8-bit green, etc.), whereas, Q16 in the filename are 16 bits-per-pixel component. A Q16 version permits you to read or write 16-bit images without losing precision but requires twice as much resources as the Q8 version. Versions with dll in the filename include ImageMagick libraries as dynamic link libraries. Unless you have a Windows 32-bit OS, we recommend this version of ImageMagick for 64-bit Windows:
| Version | Description |
|---|---|
| ImageMagick-7.0.10-34-Q16-HDRI-x64-dll.exe | Win64 dynamic at 16 bits-per-pixel component |
Or choose from these alternate Windows binary distributions:
| Version | Description |
|---|---|
| ImageMagick-7.0.10-34-Q16-x64-static.exe | Win64 static at 16 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q8-x64-dll.exe | Win64 dynamic at 8 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q8-x64-static.exe | Win64 static at 8 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q16-x64-dll.exe | Win64 dynamic at 16 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q16-HDRI-x64-dll.exe | Win64 dynamic at 16 bits-per-pixel component with high dynamic-range imaging enabled |
| ImageMagick-7.0.10-34-Q16-HDRI-x64-static.exe | Win64 static at 16 bits-per-pixel component with high dynamic-range imaging enabled |
| ImageMagick-7.0.10-34-Q16-x86-dll.exe | Win32 dynamic at 16 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q16-x86-static.exe | Win32 static at 16 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q8-x86-dll.exe | Win32 dynamic at 8 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q8-x86-static.exe | Win32 static at 8 bits-per-pixel component |
| ImageMagick-7.0.10-34-Q16-HDRI-x86-dll.exe | Win32 dynamic at 16 bits-per-pixel component with high dynamic-range imaging enabled |
| ImageMagick-7.0.10-34-Q16-HDRI-x86-static.exe | Win32 static at 16 bits-per-pixel component with high dynamic-range imaging enabled |
| ImageMagick-7.0.10-34-portable-Q16-x64.zip | Portable Win64 static at 16 bits-per-pixel component. Just copy to your host and run (no installer, no Windows registry entries). |
| ImageMagick-7.0.10-34-portable-Q16-x86.zip | Portable Win32 static at 16 bits-per-pixel component. Just copy to your host and run (no installer, no Windows registry entries). |
| ImageMagick-7.0.10-34-portable-Q8-x64.zip | Portable Win64 static at 8 bits-per-pixel component. Just copy to your host and run (no installer, no Windows registry entries). |
| ImageMagick-7.0.10-34-portable-Q8-x86.zip | Portable Win32 static at 8 bits-per-pixel component. Just copy to your host and run (no installer, no Windows registry entries). |
| ImageMagick-7.0.10-34-portable-Q16-HDRI-x64.zip | Portable Win64 static at 16 bits-per-pixel component with high dynamic-range imaging enabled. Just copy to your host and run (no installer, no Windows registry entries). |
| ImageMagick-7.0.10-34-portable-Q16-HDRI-x86.zip | Portable Win32 static at 16 bits-per-pixel component with high dynamic-range imaging enabled. Just copy to your host and run (no installer, no Windows registry entries). |
I Verify its message digest.
To verify ImageMagick is working properly, type the following in an Command Prompt window:
If you have any problems, you likely need vcomp120.dll. To install it, download Visual C++ Redistributable Package.
Note, use a double quote (') rather than a single quote (') for the ImageMagick command line under Windows:
Use two double quotes for VBScript scripts:
Congratulations, you have a working ImageMagick distribution under Windows and you are ready to use ImageMagick to convert, compose, or edit your images or perhaps you'll want to use one of the Application Program Interfaces for C, C++, Perl, and others.
File::Spec::MacFile::Spec::Mac - File::Spec for Mac OS (Classic)
Methods for manipulating file specifications.
On Mac OS, there's nothing to be done. Returns what it's given.
Concatenate two or more directory names to form a path separated by colons (':') ending with a directory. Resulting paths are relative by default, but can be forced to be absolute (but avoid this, see below). Automatically puts a trailing ':' on the end of the complete path, because that's what's done in MacPerl's environment and helps to distinguish a file path from a directory path.
IMPORTANT NOTE: Beginning with version 1.3 of this module, the resulting path is relative by default and not absolute. This decision was made due to portability reasons. Since File::Spec->catdir() returns relative paths on all other operating systems, it will now also follow this convention on Mac OS. Note that this may break some existing scripts.
The intended purpose of this routine is to concatenate directory names. But because of the nature of Macintosh paths, some additional possibilities are allowed to make using this routine give reasonable results for some common situations. In other words, you are also allowed to concatenate paths instead of directory names (strictly speaking, a string like ':a' is a path, but not a name, since it contains a punctuation character ':').
So, beside calls like
calls like the following
are allowed.
Perl For Mac Os
Here are the rules that are used in catdir(); note that we try to be as compatible as possible to Unix:
The resulting path is relative by default, i.e. the resulting path will have a leading colon.
A trailing colon is added automatically to the resulting path, to denote a directory.
Generally, each argument has one leading ':' and one trailing ':' removed (if any). They are then joined together by a ':'. Special treatment applies for arguments denoting updir paths like '::lib:', see (4), or arguments consisting solely of colons ('colon paths'), see (5).
When an updir path like ':::lib::' is passed as argument, the number of directories to climb up is handled correctly, not removing leading or trailing colons when necessary. E.g.
Adding a colon ':' or empty string ' to a path at any position doesn't alter the path, i.e. these arguments are ignored. (When a ' is passed as the first argument, it has a special meaning, see (6)). This way, a colon ':' is handled like a '.' (curdir) on Unix, while an empty string ' is generally ignored (see 'canonpath()' in File::Spec::Unix ). Likewise, a '::' is handled like a '..' (updir), and a ':::' is handled like a '../..' etc. E.g.
If the first argument is an empty string ' or is a volume name, i.e. matches the pattern /^[^:]+:/, the resulting path is absolute.
Passing an empty string ' as the first argument to
catdir()is like passingFile::Spec->rootdir()as the first argument, i.e.This is true on Unix, where
catdir(','a','b')yields '/a/b' androotdir()is '/'. Note thatrootdir()on Mac OS is the startup volume, which is the closest in concept to Unix' '/'. This should help to run existing scripts originally written for Unix.For absolute paths, some cleanup is done, to ensure that the volume name isn't immediately followed by updirs. This is invalid, because this would go beyond 'root'. Generally, these cases are handled like their Unix counterparts:
However, this approach is limited to the first arguments following 'root' (again, see 'canonpath()' in File::Spec::Unix. If there are more arguments that move up the directory tree, an invalid path going beyond root can be created.
As you've seen, you can force catdir() to create an absolute path by passing either an empty string or a path that begins with a volume name as the first argument. However, you are strongly encouraged not to do so, since this is done only for backward compatibility. Newer versions of File::Spec come with a method called catpath() (see below), that is designed to offer a portable solution for the creation of absolute paths. It takes volume, directory and file portions and returns an entire path. While catdir() is still suitable for the concatenation of directory names, you are encouraged to use catpath() to concatenate volume names and directory paths. E.g.
yields
Concatenate one or more directory names and a filename to form a complete path ending with a filename. Resulting paths are relative by default, but can be forced to be absolute (but avoid this).
IMPORTANT NOTE: Beginning with version 1.3 of this module, the resulting path is relative by default and not absolute. This decision was made due to portability reasons. Since File::Spec->catfile() returns relative paths on all other operating systems, it will now also follow this convention on Mac OS. Note that this may break some existing scripts.
The last argument is always considered to be the file portion. Since catfile() uses catdir() (see above) for the concatenation of the directory portions (if any), the following with regard to relative and absolute paths is true:
but
This means that catdir() is called only when there are two or more arguments, as one might expect.
Note that the leading ':' is removed from the filename, so that
give the same answer.
To concatenate volume names, directory paths and filenames, you are encouraged to use catpath() (see below).
Returns a string representing the current directory. On Mac OS, this is ':'.
Returns a string representing the null device. On Mac OS, this is 'Dev:Null'.
Returns the empty string. Mac OS has no real root directory.
Returns the contents of $ENV{TMPDIR}, if that directory exits or the current working directory otherwise. Under MacPerl, $ENV{TMPDIR} will contain a path like 'MacintoshHD:Temporary Items:', which is a hidden directory on your startup volume.
Returns a string representing the parent directory. On Mac OS, this is '::'.
Takes as argument a path and returns true, if it is an absolute path. If the path has a leading ':', it's a relative path. Otherwise, it's an absolute path, unless the path doesn't contain any colons, i.e. it's a name like 'a'. In this particular case, the path is considered to be relative (i.e. it is considered to be a filename). Use ':' in the appropriate place in the path if you want to distinguish unambiguously. As a special case, the filename ' is always considered to be absolute. Note that with version 1.2 of File::Spec::Mac, this does no longer consult the local filesystem.
E.g.
Returns the null list for the MacPerl application, since the concept is usually meaningless under Mac OS. But if you're using the MacPerl tool under MPW, it gives back $ENV{Commands} suitably split, as is done in :lib:ExtUtils:MM_Mac.pm.
Splits a path into volume, directory, and filename portions.
On Mac OS, assumes that the last part of the path is a filename unless $no_file is true or a trailing separator ':' is present.
The volume portion is always returned with a trailing ':'. The directory portion is always returned with a leading (to denote a relative path) and a trailing ':' (to denote a directory). The file portion is always returned without a leading ':'. Empty portions are returned as empty string '.
The results can be passed to catpath() to get back a path equivalent to (usually identical to) the original path.
The opposite of catdir().
$directories should be only the directory portion of the path on systems that have the concept of a volume or that have path syntax that differentiates files from directories. Consider using splitpath() otherwise.
Unlike just splitting the directories on the separator, empty directory names (') can be returned. Since catdir() on Mac OS always appends a trailing colon to distinguish a directory path from a file path, a single trailing colon will be ignored, i.e. there's no empty directory name after it.
Hence, on Mac OS, both
yield:
while
yields:
Takes volume, directory and file portions and returns an entire path. On Mac OS, $volume, $directory and $file are concatenated. A ':' is inserted if need be. You may pass an empty string for each portion. If all portions are empty, the empty string is returned. If $volume is empty, the result will be a relative path, beginning with a ':'. If $volume and $directory are empty, a leading ':' (if any) is removed form $file and the remainder is returned. If $file is empty, the resulting path will have a trailing ':'.
Takes a destination path and an optional base path and returns a relative path from the base path to the destination path:
Perl For Mac Osx
Note that both paths are assumed to have a notation that distinguishes a directory path (with trailing ':') from a file path (without trailing ':').
If $base is not present or ', then the current working directory is used. If $base is relative, then it is converted to absolute form using rel2abs(). This means that it is taken to be relative to the current working directory.
If $path and $base appear to be on two different volumes, we will not attempt to resolve the two paths, and we will instead simply return $path. Note that previous versions of this module ignored the volume of $base, which resulted in garbage results part of the time.
If $base doesn't have a trailing colon, the last element of $base is assumed to be a filename. This filename is ignored. Otherwise all path components are assumed to be directories.
If $path is relative, it is converted to absolute form using rel2abs(). This means that it is taken to be relative to the current working directory.
Based on code written by Shigio Yamaguchi.
Converts a relative path to an absolute path:
Note that both paths are assumed to have a notation that distinguishes a directory path (with trailing ':') from a file path (without trailing ':').
If $base is not present or ', then $base is set to the current working directory. If $base is relative, then it is converted to absolute form using rel2abs(). This means that it is taken to be relative to the current working directory.
If $base doesn't have a trailing colon, the last element of $base is assumed to be a filename. This filename is ignored. Otherwise all path components are assumed to be directories.
If $path is already absolute, it is returned and $base is ignored.
Based on code written by Shigio Yamaguchi.
See the authors list in File::Spec. Mac OS support by Paul Schinder <schinder@pobox.com> and Thomas Wegner <wegner_thomas@yahoo.com>.
Copyright (c) 2004 by the Perl 5 Porters. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
See File::Spec and File::Spec::Unix. This package overrides the implementation of these methods, not the semantics.