This page provides information specific to GraphicsMagick installed via a "setup.exe" style installation wizard under Microsoft Windows. It applies only to the pre-built "binaries" package, and not to versions compiled from source code. If you would like to install GraphicsMagick from source code, then please refer to the GraphicsMagick installation guide .
|
While multiple versions of GraphicsMagick may be
installed at one time, if your intention is to replace a prior
installation of GraphicsMagick with a newer version, then it may be
wise to uninstall the existing GraphicsMagick (see uninstall
procedure) prior to installing the newer version.
While it is
not a requirement, it is strongly recommended that the Ghostscript
package (version 7.05 preferred) be installed. GraphicsMagick uses
Ghostscript to render Postscript and PDF files, as well as formats
where a translator to Postscript is available. GraphicsMagick will
also use the fonts delivered with Ghostscript to support the standard
set of Postscript fonts.
The installation package includes
the GraphicsMagick Perl extension ( PerlMagick)
as an installation option. If you would like to use this extension,
then you must install ActiveState
ActivePerl prior to commencing with installation of
GraphicsMagick.
Retrieve the GraphicsMagick Windows binary install package from a one of the ftp sites listed at the GraphicsMagick Download Sites page. The available install packages are as follows
Windows Dynamic-Multithread (DLL-based) install package with utilities, PerlMagick, API headers, DLLs, link libraries, and web pages. NOTE: the ImageMagickObject COM object is included in the -utils package, *not* this package.
GraphicsMagick-1.0-Q8-windows.exe GraphicsMagick-1.0-Q16-windows.exe
Windows Static-Multithread package including the utilities (gm.exe, gmdisplay.exe, and MagickCMD.exe), the ImageMagickObject COM object, and the GraphicsMagick web pages.
GraphicsMagick-1.0-Q8-windows-utils.exe GraphicsMagick-1.0-Q16-windows-utils.exe
Note that the QuantumDepth=8 version (Q8) consumes half the memory and about 30% less CPU than the QuantumDepth=16 version (Q16), but provides less color resolution. A Q8 version is fine for processing typical photos. If you are dealing with scientific or medical images or deal with images that have limited contrast, then the Q16 version is recommended. It is also possible to build a Q32 version which has enough resolution to deal with the latest reconnaissance images. Please let us know if there is any demand for the Q32 versions.
Execute the downloaded file from your browser or by double-clicking on the filename from within Windows Explorer. The GraphicsMagick Setup Wizard will appear. Click on “Next>” to continue.
Specify what drive and directory to install GraphicsMagick into. Approximately 14MB of free disk space is required to install GraphicsMagick. The default installation directory is similar to “C:\Program Files\GraphicsMagick-1.0-Q16”. Once you have entered the desired installation directory, then select “Next>” to continue.
Select the folder where you would like the program's shortcuts to appear. The default should normally be satisfactory. Click on “Next>” to continue.
A screen is displayed which provides the option to create a desktop shortcut icon to the gmdisplay program and to update the executable search path so that GraphicsMagick is available without specifying the full path to the programs. The default is to enable both of these. Once you have made your selections, click on “Next>” to continue.
A screen is displayed which displays the selected options. If you are not satisfied with a selected option, then click on “<Back” to go back to a previous screen so that the option may be adjusted. If you are satisfied with the options and are ready to install, then select “Install”. To abort the installation entirely, select “Cancel”.
While the install program is performing the installation, it will display what it is doing in an installation progress window.
By default “View GraphicsMagick.html”
is check-marked. This causes the GraphicsMagick web pages to be
displayed in a browser when “Finish” is selected. If you
do not want to view the web pages, then de-select “View
GraphicsMagick.html”. Select “Finish” to exit the
installation program.
Under Windows '95 and Windows '98 it will
be necessary to reboot the system in order for some settings to take
effect (such as executable search path) since these are set in
autoexec.bat. Please verify that autoexec.bat is updated correctly.
We have received some reports that the path in autoexec.bat is not
updated correctly.
Select “Command Prompt” from the Windows Start menu. Within the window type
gm
convert logo: logo.miff
gmdisplay logo.miff
and the GraphicsMagick logo should be displayed in a window.
|
[ The following is transcribed from the Inno Setup documentation. Inno Setup is used to create the binary install package. This information may be of value if the GraphicsMagick installation must be automated (e.g. If it is installed as part of another package). ]
The Setup program accepts optional command line parameters. These can be useful to system administrators, and to other programs calling the Setup program.
|
The GraphicsMagick package incorporates its own uninstall functionality. Always remove an installed GraphicsMagick via its uninstall function since manually removing it (such as by removing its installation directory) will leave behind the registry entries and path settings established at install time.
Under Windows '95 and Windows '95, use the “Uninstall” entry in the GraphicsMagick portion of the Windows start menu to initiate the uninstall.
On NT 4.0 and 5.X -based systems, GraphicsMagick should be removed via the “Add or Remove Programs” area of the Windows Control Panel. Select the GraphicsMagick package from the list, and click on “Change/Remove” to uninstall it.
|
The GraphicsMagick gm utility may be executed as a sub-process by other programs. If gm utility is not in the systems executable search path (it should be since the GraphicsMagick install extends the path), then the utility should be executed via the complete path to the executable.
A COM object included with the "utils" package and known as ImageMagickObject may be used to execute the gm subfunctions (e.g. "convert") without spawning a new process.
A package which is linked against the GraphicsMagick core DLLs may use the DLLs from an installed DLL-based GraphicsMagick, provided that the GraphicsMagick release versions are identical, and the value of QuantumDepth matches the value used when building the package. One way to ensure this is to include a matching GraphicsMagick installation package along with your own package.
In order to facilitate building C and C++ programs that use GraphicsMagick without requiring building GraphicsMagick from source code, the header files and link libraries required to build programs using Visual C++ 7.0 are provided in “include” and “lib” subdirectories under the installation directory. Using these headers and libraries to build your dependent application ensures that they will be compatible with the release DLLs.
Note that the DLLs and libraries are built using Visual C++ 7.0 (.net). In order to use Magick++, you must either use the same compiler version used to build the distribution, or download the Windows source package and build everything yourself. While it should be possible to use the MinGW gcc compiler with the CORE_RL_magick_.dll (GraphicsMagick C library), it will certainly not be possible to use it with CORE_RL_Magick++_.dll (GraphicsMagick C++ library) due to name mangling differences.
The following project build options (change “C:\GraphicsMagick” to whever you have chosen to install) should ensure compatibility with the headers and libraries as delivered:
Key Name |
Key Type |
Preprocessor Definitions |
NDEBUG,WIN32,_CONSOLE,_VISUALC_,NeedFunctionPrototypes,_DLL,_MAGICKMOD_ |
Compilation Options |
/nologo /MD /W3 /GX /Zi /O2 /I "." /I "C:\\GraphicsMagick\include" /D "NDEBUG" /D "WIN32" /D "_CONSOLE" /D "_VISUALC_" /D "NeedFunctionPrototypes" /D "_DLL" /D "_MAGICKMOD_" /FD /c |
Linker Options |
CORE_RL_magick_.lib CORE_RL_Magick++_.lib X11.lib kernel32.lib user32.lib gdi32.lib odbc32.lib odbccp32.lib ole32.lib oleaut32.lib winmm.lib dxguid.lib wsock32.lib advapi32.lib /nologo /subsystem:console /incremental:no /debug /machine:I386 /libpath:"C:\GraphicsMagick\lib\" |
Resource Options |
/l 0x409 /d "NDEBUG" |
When GraphicsMagick is installed, entries are added to the Windows Registry so that other programs may obtain information regarding the most recently installed GraphicsMagick. These entries are available under the registry path
HKEY_LOCAL_MACHINE\SOFTWARE\GraphicsMagick\Current
These keys are currently available:
Key Name |
Key Type |
Description |
BinPath |
REG_SZ |
Directory where GraphicsMagick executables are installed |
ConfigurePath |
REG_SZ |
Directory where configuration files are installed |
LibPath |
REG_SZ |
Directory where GraphicsMagick core DLLs are installed |
CoderModulesPath |
REG_SZ |
Directory where GraphicsMagick loadable coder modules are installed |
FilterModulesPath |
REG_SZ |
Directory where GraphicsMagick loadable filter modules are installed |
QuantumDepth |
REG_DWORD |
Number of bits in a pixel quantum. A pixel quantum is used to store part of a color (e.g. red component) |
Version |
REG_SZ |
GraphicsMagick version |
In addition to registry entries which provide information on the most recently installed GraphicsMagick (which is not necessarily the newest version installed), registry entries are available for specific versions of installed GraphicsMagick packages. These registry entries are available under a registry path of the form:
HKEY_LOCAL_MACHINE\SOFTWARE\GraphicsMagick\VERSION\Q:DEPTH
where VERSION represents the GraphicsMagick version and DEPTH (which may have the values 8 or 16) represents the number of bits per pixel quantum. Packages which require a particular version of GraphicsMagick built with a specific QuantumDepth may find a matching installation via these registry entries.
These keys are currently available:
Key Name |
Key Type |
Description |
BinPath |
REG_SZ |
Directory where GraphicsMagick executables are installed |
ConfigurePath |
REG_SZ |
Directory where configuration files are installed |
LibPath |
REG_SZ |
Directory where GraphicsMagick core DLLs are installed |
CoderModulesPath |
REG_SZ |
Directory where GraphicsMagick loadable coder modules are installed |
FilterModulesPath |
REG_SZ |
Directory where GraphicsMagick loadable filter modules are installed |
SharePath |
REG_SZ |
Directory where configuration files are installed |