Legacy ImageMagick Discussions Archive

I have Windows 8.1 and Visual Studio 2013.

Since the provided binaries seems to be not compatible with vc 2013, I'm recompiling ImageMagick from source

The readme file says to compile a VisualMagick project first, which seems some odd build system, that will generate Visual Studio 2010 (!!) soution files (which I could eventually import into 2013).

Problem is, this VisualMagick project seems to use MFC that I didn't even install. As you can see, latest MFC release was 1 and a half year ago (june 2013), and the entire project seems to be abandoned and used less and less in favor of .NET

BTW, after installing the MFC libraries from the visual studio DVD, I tried to build the project "VisualMagick" but visual studio complained that multi-byte support for MFC is discontinued, and I entire switch to Unicode or download the linked library. Since switching to Unicode isn't practicable (casting errors etc...) i had to download the library


I really think that this old and outdated VisualMagick system has simply to gone in favour of something like CMake

I know nothing about Visual Studio, but IM can be easily built with Cygwin tools on Windows. See my http://im.snibgo.com/compim.htm . (However, I don't link-in the various delegates.)

It is not necessary to recompile the 'configure' project. You can just execute the supplied binary that will create the solution for you. The only project that uses MFC is IMDisplay. You could remove that from the solution or just delete the IMDisplay folder in the VisualMagick folder.

You might consider VS 2010 outdated but the configure.exe solution has only been upgraded from VS 2002 recently

dlemstra wrote:It is not necessary to recompile the 'configure' project. You can just execute the supplied binary that will create the solution for you.

so there was a configure.exe file already there? I didn't know it, the documentation said to compile the VisualMagick project.

I still think that this entire VisualMagick + automake thing has to gone in favor of something like CMake. This was it's a mess, with 2 different build system and I think you are the only project that uses a "VisualMagick" like thing. While with CMake everyone will know the steps without even reading a line of documentation.

Honestly I don't know if Cygwin libraries can be used inside VisualStudio

You might be right that we are one of the few project that does it like this. Switching to CMake could be an option but the current solution works for most of our users. I will take a look at it when I have a couple of days spare time.