GraphicsMagick Windows Installation

Prerequisites
Retrieve Install Package
Start Installation Wizard
Read Installation Information
Select Destination Directory
Select Start Menu Folder
Select Additional Tasks
Ready to Install
Installation Progress
Final Information
Finishing Up
Testing The Installation
Uninstall
Use From Another Package or Program
Installing Using Installer Package
+

Applicability
Important Notes
Windows XP, Vista, 7 Visual C++ 6.0 through 19.0 Compilation
Environment Variables
Windows Distribution Build Procedure
Installing From Source Code
+

@@ -70,12 +75,13 @@

Installing Using Installer Package

-This section provides information specific to GraphicsMagick installed +
This section 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 Installing From Source Code -section.

+section.

Prerequisites

@@ -94,8 +100,7 @@ Fonts") to support the standard set of Adobe Postscript fonts like "Helvetica" and "Times Roman" if these fonts are not available as TrueType fonts. The Ghostscript fonts need to manually installed with administrator privileges in the Ghostscript installation -directory (e.g. as C:\Program Files\gs\fonts or C:Program -Files\gs\gs9.27\fonts).
+directory (e.g. as C:\Program Files\gs\fonts or C:Program Files\gs\gs9.27\fonts).

The algorithm used to find the fonts consults the Windows registry to learn Ghostscript installation paths, and then looks for a "fonts/n019003l.pfb" file in each path until it finds a match.
@@ -115,12 +120,10 @@ of the ftp sites listed at the -GraphicsMagick-1.3-Q8-win32-dll.exe +
GraphicsMagick-1.3-Q8-win32-dll.exe GraphicsMagick-1.3-Q16-win32-dll.exe GraphicsMagick-1.3-Q8-win64-dll.exe -GraphicsMagick-1.3-Q16-win64-dll.exe -
+GraphicsMagick-1.3-Q16-win64-dll.exe

Note that the QuantumDepth=8 version (Q8) which provides industry standard 24/32 bit pixels consumes half the memory and about 30% less @@ -140,35 +143,38 @@ access is 1000 times faster than disk access.

Start Installation Wizard

-Execute the downloaded file from your browser or by double-clicking on +
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.

+Wizard will appear. Click on "Next>" to continue.

Read Installation Information

-An informational screen is presented which provides a summary of things +
An informational screen is presented which provides a summary of things you should know before you proceed. Please take care to read this -information. Once you have finished, Click on "Next>" to continue.

+information. Once you have finished, Click on "Next>" to continue.

Select Destination Directory

-Specify what drive and directory to install GraphicsMagick into. +
Specify what drive and directory to install GraphicsMagick into. Approximately 15MB of free disk space is required to install all of GraphicsMagick (you may choose to install a subset to save space). A message at the bottom of the screen will tell you exactly how much space is required to install the complete package. The default -installation directory is similar to C:\Program -Files\GraphicsMagick-1.3-Q8. Once you have entered the desired -installation directory, then select "Next>" to continue.

+installation directory is similar to C:\Program Files\GraphicsMagick-1.3-Q8. Once you have entered the desired +installation directory, then select "Next>" to continue.

Select Additional Tasks

@@ -176,9 +182,9 @@ to continue.

A screen is displayed which presents some (or all) of the following options:

Create a desktop icon
Update executable search path
Associate supported file extensions with GraphicsMagick
Create a desktop icon
Update executable search path
Associate supported file extensions with GraphicsMagick

"Creating a desktop icon" and "Update the executable search path" are selected by default. The remaining options default to @@ -196,35 +202,39 @@ native formats (such as MIFF)

Ready to Install

-A screen is displayed which displays the selected options. If you are +
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".

+"Install". To abort the installation entirely, select "Cancel".

Installation Progress

-While the install program is performing the installation, it will -display what it is doing in an installation progress window.

While the install program is performing the installation, it will +display what it is doing in an installation progress window.

Final Information

-A summary of post-install steps is provided. These steps include some +
A summary of post-install steps is provided. These steps include some commands you can execute to make sure that GraphicsMagick is working, as well as some notes about what has been installed on your system, and where to find additional information. Once you have read this -information, click on "Next>" to continue.

+information, click on "Next>" to continue.

Finishing Up

-By default "View GraphicsMagick.html" is check-marked. This causes the +
By default "View GraphicsMagick.html" is check-marked. This causes the GraphicsMagick web pages to be displayed in your web 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.

+installation program.

Testing The Installation

@@ -232,10 +242,8 @@ installation program.

Select "Command Prompt" from the Windows Start menu. Within the window type

-gm convert logo: logo.miff
-gm convert logo.miff win:
-

gm convert logo: logo.miff
+gm convert logo.miff win:

and the GraphicsMagick logo should be displayed in a window.

@@ -272,50 +280,50 @@ source code.

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.

+under the registry path HKEY_LOCAL_MACHINE\SOFTWARE\GraphicsMagick\Current.

These registry keys are currently available:

- +

---+++ - - - - + + + + - - - - + + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + +

Key Name	Key Type	Description
Key Name	Key Type	Description
BinPath	REG_SZ	Directory where GraphicsMagick executables -are installed
BinPath	REG_SZ	Directory where GraphicsMagick executables +are installed
ConfigurePath	REG_SZ	Directory where configuration files are -installed
ConfigurePath	REG_SZ	Directory where configuration files are +installed
LibPath	REG_SZ	Directory where GraphicsMagick core DLLs -are installed
LibPath	REG_SZ	Directory where GraphicsMagick core DLLs +are installed
CoderModulesPath	REG_SZ	Directory where GraphicsMagick loadable -coder modules are installed
CoderModulesPath	REG_SZ	Directory where GraphicsMagick loadable +coder modules are installed
FilterModulesPath	REG_SZ	Directory where GraphicsMagick loadable -filter modules are installed
FilterModulesPath	REG_SZ	Directory where GraphicsMagick loadable +filter modules are installed
SharePath	REG_SZ	Directory where configuration files are -installed
SharePath	REG_SZ	Directory where configuration files are +installed

@@ -327,32 +335,34 @@ installed

Applicability

-This section provides instructions for building GraphicsMagick +
This section provides instructions for building GraphicsMagick Microsoft Windows using the Visual C++ (Visual Studio, etc.) IDE. For building using the free Cygwin or MinGW compilers (e.g. as part of MSYS2), follow the instructions -in INSTALL-unix.txt.

+in INSTALL-unix.txt.

Important Notes

-On some platforms Visual C++ may fail with an internal compiler +
On some platforms Visual C++ may fail with an internal compiler error. If this happens to you, then make sure that your compiler is updated with the latest fixes from the Microsoft web site and the problem will hopefully go away. If the problem does not go away, then adjust the settings for the module which failed and disable optimization, and the problem is likely to go away (but with less -performance).

+performance).

Windows XP, Vista, 7 Visual C++ 6.0 through 19.0 Compilation

Windows XP, Vista, 7 Visual C++ 6.0 through 17.6.5 Compilation

The Visual C++ distribution targeted at Windows 2000 through Windows 10 does not provide any stock workspace (DSW) or project files (DSP) except for those included with third party libraries. Instead, there is a "configure" program that must run to create build environments to satisfy various requirements.
-
The configure program resides in VisualMagick\configure in the +
The configure program resides in VisualMagick\configure in the GraphicsMagick source tree. A pre-compiled configure.exe is provided, as well as Visual Studio project files to recompile it from source code if needed.
@@ -361,17 +371,22 @@ dialog after proceeding past the initial notifications screen:

In addition to (or as a replacement to) the above dialog, the configure.exe program supports these command-line options:
-
+

/Q8 /Q16 /Q32
-
Set quantum depth
+
Set quantum depth
+

/x64
-
Add x64 configuration
+
Add x64 configuration
+

/mtd /sts /mts /mtsd
-
Set project type
+
Set project type
+

/noWizard
-
Do not show the wizard
+
Do not show the wizard
+

/openMP
-
Enable openMP
+
Enable openMP
+

The Visual C++ system provides three different types of "runtimes" that must match across all application, library, and DLL code that is @@ -379,10 +394,10 @@ built. The "configure" program creates a set of build files that are consistent for a specific runtime selection.

The three options for runtime support are:

-
Dynamic Multi-threaded DLL runtimes (VisualDynamicMT), /mtd option
-
Static Single-threaded runtimes (VisualStaticST), /sts option
-
Static Multi-threaded runtimes (VisualStaticMT), /mts option
-
Static Multi-threaded DLL runtimes (VisualStaticMTDLL), /mtsd option
+
Dynamic Multi-threaded DLL runtimes (VisualDynamicMT), /mtd option
+
Static Single-threaded runtimes (VisualStaticST), /sts option
+
Static Multi-threaded runtimes (VisualStaticMT), /mts option
+
Static Multi-threaded DLL runtimes (VisualStaticMTDLL), /mtsd option

In addition to these runtimes, the VisualMagick build environment allows you to select whether to include the X11 libraries in the build or not. @@ -400,18 +415,20 @@ directory under VisualMagick and open the configure.dsw workspace (for Visual C++ 6.0) or configure.sln (for Visual C++ 7.X through 9.X). Set the build configuration to "Release" under the

-"Build..., Set Active Configuration..." menu.
+
"Build..., Set Active Configuration..." menu.
+

Build and execute the configure program and follow the on-screen instructions. You should not change any of the defaults unless you have a specific reason to do so.

The configure program provides a button entitled

-Edit "magick_config.h"

Edit "magick_config.h"

Clicking this button brings up magick_config.h in Windows notepad for optionally changing any preprocessor defines in GraphicsMagick's magick_config.h file. This file is copied to -magick\magick_config.h. You may safely open -magick\magick_config.h, modify it, and recompile without +magick\magick_config.h. You may safely open +magick\magick_config.h, modify it, and recompile without re-running the configure program. In fact, using Visual Studio to edit the copied file may be preferable since it preserves the original magick_config.h file.

@@ -419,28 +436,32 @@ original magick_config.h file.

QuantumDepth (default 8)

-Specify size of PixelPacket color Quantums (8, 16, or 32) A value of +
Specify size of PixelPacket color Quantums (8, 16, or 32) A value of 8 uses half the memory than 16 and may run 30% faster, but provides -256 times less color resolution than a value of 16.
+256 times less color resolution than a value of 16.
+

UseInstalledMagick (default undefined)

-Define to build a GraphicsMagick which uses registry settings or +
Define to build a GraphicsMagick which uses registry settings or embedded paths to locate installed components (coder modules and configuration files). The default is to look for all files in the -same directory as the executable.

+same directory as the executable.

ProvideDllMain (default undefined)

-Define to include a DllMain() function ensures that the GraphicsMagick +
Define to include a DllMain() function ensures that the GraphicsMagick DLL is properly initialized without participation from dependent applications. This avoids the requirement to invoke IntializeMagick() -from dependent applications but only works for DLL builds.

+from dependent applications but only works for DLL builds.

EnableBrokenCoders (default undefined)

-Define to enable broken/dangerous file format support. Only +
Define to enable broken/dangerous file format support. Only enable this if you have complete control over the input files and not for arbitrary files such as uploaded from untrusted sources via the Internet. Currently this must be enabled to -enable Adobe Photoshop Format (PSD).

+enable Adobe Photoshop Format (PSD).

After creating your build environment you can proceed to open the DSW (or SLN) file that was generated in the VisualMagick directory and build @@ -452,11 +473,11 @@ the "active" project. Set the build configuration to the desired one do the build in a specific way:

-
Make the "All" project the active project (Bold) -Right click on the All project and select "Set As Active Project"
-
Select "Build..., Clean"
-
Select "Build..., Build"
-
Go get some coffee unless you have a very fast machine!.
+
Make the "All" project the active project (Bold) +Right click on the All project and select "Set As Active Project"
+
Select "Build..., Clean"
+
Select "Build..., Build"
+
Go get some coffee unless you have a very fast machine!.

The "Clean" step is needed in order to make sure that all of the target @@ -471,22 +492,24 @@ system installation.

Note #1:

The Visual C++ distribution of GraphicsMagick comes with the Magick++ C++ wrapper by default. This add-on layer has a large number of demo -and test files that can be found in GraphicsMagick\Magick++\demo, and -GraphicsMagick\Magick++\tests. There are also a variety of tests that -use the straight C API as well in GraphicsMagick\tests.

+and test files that can be found in GraphicsMagick\Magick++\demo, and +GraphicsMagick\Magick++\tests. There are also a variety of tests that +use the straight C API as well in GraphicsMagick\tests.

All of these programs are NOT configured to be built in the default workspace created by the configure program. You can cause all of these demos and test programs to be built by checking the box in configure that says:

-"Include all demo and test programs"

"Include all demo and test programs"

In addition, there is another related checkbox (checked by default) that causes all generated project files to be created standalone so that they can be copied to other areas of you system.

This is the checkbox:

-"Generate all utility projects with full paths rather then relative -paths"

"Generate all utility projects with full paths rather then relative +paths"

WOW - that a mouthfull - eh?

Visual C++ uses a concept of "dependencies" that tell it what other components need to be build when a particular project is being build. This @@ -502,10 +525,11 @@ and can actually be copied and used as templates to get a particular custom application compiling with little effort.

With this feature enabled, you should be able to nab a copy of...

-
VisualMagick\utilities\UTIL_gm_xxx_exe.dsp (for C)
+
VisualMagick\utilities\UTIL_gm_xxx_exe.dsp (for C)

--or-
-
VisualMagick\Magick++\demo\UTIL_demo_xxx_exe.dsp (for C++)
+
-or-
+

VisualMagick\Magick++\demo\UTIL_demo_xxx_exe.dsp (for C++)

... and pop it into notepad, modify it (carefully) to your needs and be on your way to happy compiling and linking.

@@ -515,20 +539,20 @@ and the source and hacking away.

The choice of what to use as a starting point is very easy...

For straight C API command line applications use something from

-
GraphicsMagick\tests or GraphicsMagick\utilities (source code)
-
GraphicsMagick\VisualMagick\tests or GraphicsMagick\Visualmagick\utilities +
GraphicsMagick\tests or GraphicsMagick\utilities (source code)
+
GraphicsMagick\VisualMagick\tests or GraphicsMagick\Visualmagick\utilities (project - DSP)

For C++ and Magick++ command line applications use something from

-
GraphicsMagick\Magick++\tests or GraphicsMagick\Magick++\demo (source code)
-
GraphicsMagick\VisualMagick\Magick++\tests or -GraphicsMagick\VisualMagick\Magick++\demo (project - DSP)
+
GraphicsMagick\Magick++\tests or GraphicsMagick\Magick++\demo (source code)
+
GraphicsMagick\VisualMagick\Magick++\tests or +GraphicsMagick\VisualMagick\Magick++\demo (project - DSP)

For C++ and Magick++ and MFC windows applications use

-
GraphicsMagick\win2k\IMDisplay (source code)
-
GraphicsMagick\VisualMagick\win32\NtMagick (project - DSP)
+
GraphicsMagick\win2k\IMDisplay (source code)
+
GraphicsMagick\VisualMagick\win32\NtMagick (project - DSP)

Note #2:

The GraphicsMagick distribution is very modular. The default @@ -541,20 +565,20 @@ components may be copied to another folder (such as to another computer).

following files:

-
colors.mgk
-
delegates.mgk
-
log.mgk
-
magic.mgk
-
modules.mgk
-
type.mgk
-
type-ghostscript.mgk (if Ghostscript is used)
+
colors.mgk
+
delegates.mgk
+
log.mgk
+
magic.mgk
+
modules.mgk
+
type.mgk
+
type-ghostscript.mgk (if Ghostscript is used)

The "bin" folder should contains all EXE's and DLL's as well as the very important "modules.mgk" file.

With this default setup, you can use any of the command line tools and run scripts as normal. You can actually get by quite nicely this -way by doing something like pushd e:\xxx\yyy\bin in any scripts you +way by doing something like pushd e:\xxx\yyy\bin in any scripts you write to execute "out of" this directory.

By default the core of GraphicsMagick on Win32 always looks in the place were the exe program is run from in order to find all of the files as @@ -575,7 +599,8 @@ DLL's. Windows CMD shell seems to look in the "current" directory firs you wish to run any of utilities from another location then you must add the path to your "bin" directory in. For instance, you might add:

-D:\Devel\GraphicsMagick\VisualMagick\bin

D:\Devel\GraphicsMagick\VisualMagick\bin

to do this for the default build environment like I do.

MAGICK_HOME

@@ -593,7 +618,8 @@ to leave the modules in the same place as the EXE's (a good idea) then you can simply set this to the same place as you did the PATH variable. In my case:

-D:\\GraphicsMagick\coders

D:\\GraphicsMagick\coders

This is also the place were GraphicsMagick expects to find the "colors.mgk", "delegates.mgk", "magic.mgk", "modules.mgk", and "type.mgk" files.

@@ -608,10 +634,12 @@ purposes.

way. Two #defines are applicable.

defines.h has

-#define MagickConfigurePath "c:\\GraphicsMagick\\"

#define MagickConfigurePath "c:\\GraphicsMagick\\"

To view any image in a Microsoft window, type

-gm convert image.ext win:

gm convert image.ext win:

Make sure Ghostscript is installed, otherwise, you will be unable to convert or view a Postscript document, and Postscript standard fonts will not be available.

@@ -629,103 +657,97 @@ Professional. This is the same procedure used to produce the release packages. The PerlMagick steps are skipped as of GraphicsMagick 1.3.26):

Install prerequisite software:
Install prerequisite software:

-
Install Microsoft Visual Studio.
-
Download and install Inno Setup 6 -<"http://www.jrsoftware.org/isinfo.php">.
-
Download and install ActiveState ActivePerl (optional) -<"http://www.activestate.com/activeperl/downloads/">.
+
Install Microsoft Visual Studio.
+
Download and install Inno Setup 6 +<"http://www.jrsoftware.org/isinfo.php">.
+
Download and install ActiveState ActivePerl (optional) +<"http://www.activestate.com/activeperl/downloads/">.

Disable automatic indexing and virus scanning for the +
Disable automatic indexing and virus scanning for the GraphicsMagick source tree. In particular, "Windows Defender" in Windows 10 (and similar software in earlier Windows releases) has been observed to cause Visual Studio builds to fail since the virus scanner opens built libraries and executables to inspect whem while Visual Studio is still using them. Indexing and scanning also cause significant slowdowns since there are many -megabytes of files to index.
-
Build GMVisualMagickconfigureconfigure.exe (if +megabytes of files to index.
Build GMVisualMagickconfigureconfigure.exe (if missing/outdated)
1. Open workspace GMVisualMagickconfigureconfigure.dsp by -double-clicking from Windows Explorer.
2. Upgrade Visual Studio project (as required)
3. Select Rebuild All to build configure.exe
4. Close the project.
5. Open workspace GMVisualMagickconfigureconfigure.dsp by +double-clicking from Windows Explorer.
6. Upgrade Visual Studio project (as required)
7. Select Rebuild All to build configure.exe
8. Close the project.
Configure Initial GraphicsMagick Visual Studio Workspace
+
Configure Initial GraphicsMagick Visual Studio Workspace
1. Use Windows Explorer to navigate to GMVisualMagickconfigure.
2. Double-click on configure.exe to run configure program.
3. Select desired build options: DLL build, Quantum Depth, 64-bit, OpenMP)
4. Check Build demo and test programs.
5. Finish remaining configure wizard screens to complete.
6. File -> Close Workspace.
7. Use Windows Explorer to navigate to GMVisualMagickconfigure.
8. Double-click on configure.exe to run configure program.
9. Select desired build options: DLL build, Quantum Depth, 64-bit, OpenMP)
10. Check Build demo and test programs.
11. Finish remaining configure wizard screens to complete.
12. File -> Close Workspace.
Open Workspace, set build configuration, build GraphicsMagick software.
+
Open Workspace, set build configuration, build GraphicsMagick software.
1. Open workspace GMVisualMagickconfigureconfigure.sln by -double-clicking from Windows Explorer.
2. Build -> "Set Active Configuration" -> "All - Win32 Release" -> OK
3. Optionally enable 64-bit (WIN64) compilation. "Build / +
4. Open workspace GMVisualMagickconfigureconfigure.sln by +double-clicking from Windows Explorer.
5. Build -> "Set Active Configuration" -> "All - Win32 Release" -> OK
6. Optionally enable 64-bit (WIN64) compilation. "Build / Configuration Manager... / Active Solution Platform / -New / x64".
7. Open CORE_magickmagickmagick_config.h and edit any +New / x64".
8. Open CORE_magickmagickmagick_config.h and edit any configuration settings you would like to change. For example, -you might change QuantumDepth to 16 for a"Q:16" build.
9. If using Visual Studio Professional Edition, and OpenMP +you might change QuantumDepth to 16 for a"Q:16" build.
10. If using Visual Studio Professional Edition, and OpenMP support is desired, then select CORE_magick in the Solution Explorer pane and use the right mouse button menu to select Properties. In Configuration Properties / C/C++ / -Language set OpenMP support to 'yes'.
11. Select "Rebuild All"
12. Click on '!' icon to run configure program
13. Select DLL build
14. Check Build demo and test programs.
15. Click on Edit magick_config.h and verify desired settings +Language set OpenMP support to 'yes'.
16. Select "Rebuild All"
17. Click on '!' icon to run configure program
18. Select DLL build
19. Check Build demo and test programs.
20. Click on Edit magick_config.h and verify desired settings such as QuantumDepth. You can also defer this step to later by opening the header file -CORE_magick\include\magick_config.h in the Visual Studio -project.
21. Finish remaining configure wizard screens to complete.
22. File -> Close Workspace
23. Finish remaining configure wizard screens to complete.
24. File -> Close Workspace
Build ImageMagickObject
+
Build ImageMagickObject
1. Open Visual Studio Command Shell Window for WIN32 or WIN64
2. Change to GraphicsMagick project directory GM
3. cd GM\contrib\win32\ATL7\ImageMagickObject
4. BuildImageMagickObject clean
5. BuildImageMagickObject release
6. cd ..\..\..\..
7. Open Visual Studio Command Shell Window for WIN32 or WIN64
8. Change to GraphicsMagick project directory GM
9. cd GM\contrib\win32\ATL7\ImageMagickObject
10. BuildImageMagickObject clean
11. BuildImageMagickObject release
12. cd ..\..\..\..
Build PerlMagick extension (optional and now rarely done)
+
Build PerlMagick extension (optional and now rarely done)
1. Open Visual Studio Command Shell Window for WIN32 or WIN64
  -
2. Change to GraphicsMagick project directory GM
  -
3. cd GM\PerlMagick
  -
4. nmake clean (only if this is a rebuild)
  -
5. C:\Perl32\bin\perl.exe Makefile.nt (or Perl64)
  +
6. Open Visual Studio Command Shell Window for WIN32 or WIN64
7. Change to GraphicsMagick project directory GM
8. cd GM\PerlMagick
9. nmake clean (only if this is a rebuild)
10. C:\Perl32\bin\perl.exe Makefile.nt (or Perl64)
  
  Note that if multiple Perl's are installed, then it may be necessary to specify the full path to perl.exe in order to use the correct Perl.
11. nmake release
  -
12. nmake release

@@ -734,58 +756,63 @@ how the install of Visual Studio was done, this may not be the case. Visual Studio provides a batch script in VC98Bin called VCVARS32.BAT that can be used to do this manually after you open up a command prompt.

Open GMVisualMagickinstallergm-win32-Q8-dll-full.iss (or +
Open GMVisualMagickinstallergm-win32-Q8-dll-full.iss (or gm-win32-Q16-dll-full.iss if QuantumDepth=16) by -double-clicking from Windows Explorer.
1. File -> Compile
2. Test install by clicking on green triangle
3. Test PerlMagick (optional).
  1. cd PerlMagick
  2. nmake test (All tests must pass!)
  3. Test PerlMagick (optional).
    +
    1. cd PerlMagick
    2. nmake test (All tests must pass!)
  4. Test file format read and write.
  5. Test file format read and write.
  1. cd VisualMagick\tests
  2. run_rwfile.bat (All tests must pass!)
  3. run_rwblob.bat (All tests must pass!)
  4. cd VisualMagick\tests
  5. run_rwfile.bat (All tests must pass!)
  6. run_rwblob.bat (All tests must pass!)
  1. Run Magick++ test programs.
  2. Run Magick++ test programs.
  1. cd Magick++/tests
  2. run_tests.bat (All tests must pass!)
  3. cd Magick++/tests
  4. run_tests.bat (All tests must pass!)
  1. Run Magick++ demo programs.
  2. Run Magick++ demo programs.
  1. cd Magick++/demo
  2. run_demos.bat
  3. Use gmdisplay to visually inspect all output files.
  4. cd Magick++/demo
  5. run_demos.bat
  6. Use gmdisplay to visually inspect all output files.
  1. Distribution package is available named similar to -GM\VisualMagick\bin\GraphicsMagick-1.3-Q8-dll.exe
  2. Distribution package is available named similar to +GM\VisualMagick\bin\GraphicsMagick-1.3-Q8-dll.exe

-- cgit v1.2.3