Ignore:
Timestamp:
2017-09-29T17:08:38+13:00 (7 years ago)
Author:
ak19
Message:
  1. Shifting the imagemagick windows binary to within trunk where the unix binaries are. 2. Updating the README to indicate that the windows imagemagick binary was a mere zip up of the bin\windows\imagemagick folder on trac.
Location:
gs2-extensions/imagemagick/trunk
Files:
1 edited
1 moved

Legend:

Unmodified
Added
Removed
  • gs2-extensions/imagemagick/trunk/README

    r31379 r32016  
    33
    44If making an imagemagick binary tarball, here are the steps to go through and the things to check
     5
     6WINDOWS IMAGEMAGICK BINARY
     7This was merely a zip up of the bin\windows\imagemagick folder checked out from http://trac.greenstone.org/browser/main/trunk/binaries/windows/bin/imagemagick
     8I then removed the .svn subfolder, zipped it up and put it here. The purpose is for people working with GS2 source distributions to grab a quick copy, as the compilation process doesn't compile up imagemagick.
     9For GS2's unix systems, if "imagemagick" is passed in as parameter to the makegs2.sh script, it will now download the appropriate imagemagick binary tarball for the unix flavour from http://trac.greenstone.org/browser/gs2-extensions/imagemagick after compilation has succeeded.
    510
    611
Note: See TracChangeset for help on using the changeset viewer.