Legacy ImageMagick Discussions Archive

Now is a good time to do that, since it doesn't work (at least on the 6.xx version). Thanks for reminding me to follow instructions.

Thanks dlemstra. Simply deleting the configure.exe and rebuilding (after converting the project to vs2013) fixed the issue. First time in a long while the configure.exe that comes in the bundle didn't work for me.

Yep. I agree. I have tried searching for intermediate bundles, but can only find the unix source for those (via the git repo's tagged release). But since none of those bundles contain the VisualMagick directory, I am stuck (unless I can just copy the one from -10 over... *shrug*).

for what it's worth, -1 built just fine. -9 also had this issue, but I noticed that -10 had been released, so thought to try it instead. I don't know where to find the windows versions of the build source for 6.9.4-2 through 6.9.4-8 so I cannot say when the error was introduced.

It has to be 32 bit. I cannot run 64 bit software on 32bit windows.

The machine I am building on is windows 7 32 bit. And the logs show Configuration Release Win32. I have tried to build with the GUI as well. Command line I am using: MSBuild VisualDynamicMT.sln /target:Clean /property:Configuration=Release MSBuild VisualDynamicMT.sln /property:Configuration=Release

The jsimdext.inc file does exist in C:\third_party\sandbox\ImageMagick-win32-6.9.4-10\jpeg\simd. Not sure why the build can't find it.

CUSTOMBUILD : fatal error A1000: cannot open file : "jsimdext.inc" [C:\third_party\sandbox\ImageMagick-win32-6.9.4-10\VisualMagick\jpeg\CORE_jpeg_DynamicMT.vcxproj]


I keep getting that over and over. I have tried doing a clean, etc. But it never gets past that point.

the .sln opens in vs2013 just fine and doesn't prompt to upgrade after running the vs2012 script. The only part that doesn't compile is the analyze_mt bit. The rest compiles fine. And all of it compiles fine in vs2013 if I open the .sln and use the configuration manager to build a release build. Jus...

Sorry, that was a typo, the script does indeed do /Q8.

And yes, I do call vsvars32.bat...

configure.exe doesn't crash, it just exits with non zero exit status. Which gets caught as Inappropriate IO control or something like that.

Sorry to revive an old thread... I am also having trouble compiling using VS2013. I am testing version 6.9.0-0. I am trying to compile using command line tools in order to automate building ImageMagick as a part of a much larger build process. The commands I am using are: From the VisualMagick/confi...

Just to update, I tested 6.8.4-2 and it did not have this issue either. I don't have any other 6.8.4 builds available to test. Where can I find the ones between -2 and -10?

Just to update, I tested 6.8.4-2 and it did not have this issue either.

I'm also getting this error. I do not have any previous versions of ImageMagick installed. I am compiling perl and ImageMagick using visual studio 2010: 1) download perl source code and extract it 2) cd to perl-5.14.4\win32 3) edit makefile so that it references the correct version of visual studio ...

I'm also getting this error. I do not have any previous versions of ImageMagick installed. I am compiling perl and ImageMagick using visual studio 2010: 1) download perl source code and extract it 2) cd to perl-5.14.4\win32 3) edit makefile so that it references the correct version of visual studio ...