Legacy ImageMagick Discussions Archive

but that might be because I deleted project heic.

and the fuzz projects fail as well

i downloaded and tried to open the configure.sln in vs2010 cannot, because of: const vector<wstring> validSrcFiles = {L".c", L".cpp", L".cc"}; which does not compile in vs2010 so I used vs2015 to build the 2010 sln. which, when I tried to build, failed due to this: #if !defined(INFINITY) # define ...

Thanks, I will try this today; moving all of our stuff to 2013 is proving to be a pain.

which visual studio do you use to build the windows binary release?

visual studio 2010 is what is failing for me.
do you know what Visual Studio versions do work?

I am trying to build in VisualStudio 2010 the latest download of source. Fails in flif and MagickCore projects. Any thoughts on how to accomplish a 2010 build? first failure is in flif: 17>------ Rebuild All started: Project: CORE_flif, Configuration: Debug Win32 ------ 17>Build started 09/05/2016 1 ...

more details: seems to work as a command line calling convert but not from the MagickCore::ConvertImageCommand API I have compiled 6.9.3.1 in visual studio 2010, copied all the VisualMagick/bin files to c:\telescope\IMBin I have path set to c:\Telescope\IMBin // we use image magick thus to convert a ...

my workflow uses dlls built with visual studio 2010. I need the latest imagemagick to get the ability to turn off auto grayscaling (see my other topic:rgb converted to grayscale by imagemagick ) The dll's I build to use the imagemagick do not work with the latest window 6.9.3 installer, which I ...

- seems they are generated after memory gets filled...

these temp files filled 14GB after processing about 1000 jpgs...

I recompiled everything with 6.9.3.1 and deployed the imagemagick installer on my test machine. Processing a 1000+ jpgs has resulted in memory filling up and a huge number of files in my windows temp dir, with name like magick_xxxxx, see examples below. None of this happens with 6.9.0.x version I ...

I create and use a Magick::Image* thus: Magick::Image * pImage = NULL; try { pImage = new Magick::Image(lszOrgfilePath.c_str()); } catch (...) { .. do some catchy stuff return; } if(pImage) { do stuff with the pImage... get info such as colorspace etc. } //finish up //delete pImage; return; } this ...

Hi, your suggestion works fine on the command line. But, I cannot get it working with 6.9.3.1 source and installer. We build our ImageMagick components in visual studio 2010 MT dynamic mode Q16, and then run the IM installer to get the right bits on the customer machines. When I build against 6.9.0 ...

Thanks. I really did not see the scrollbar. Seems the older I get, the dumber I get. I hope to have a brain cell left in a year or two.

g