We are hoping to use IM via Magick++ in a project that will process very large images (10^10 pixels) on a windows based system. As such we ultimately want to compile a 64bit version of IM with all possible multi-core support.
I'm trying to compile v6.7.9-10 as downloaded from ftp://mirror.checkdomain.de/imagemagick ... .7.9-10.7z, with Visual Studio 2010. These are the configure settings I used:
I changed the configuration to x64 release and cleaned the build as described in the instructions then build the solution.
The build initially spits out 6 errors like
Error 261 error RC1110: could not open ..\..\magick\ImageMagick.rc ..ImageMagick-6.7.9\VisualMagick\utilities\RC UTIL_composite
then I get over 300 errors like
Error 1627 error LNK2001: unresolved external symbol XSync ..ImageMagick-6.7.9\VisualMagick\magick\xwindow.obj CORE_magick
At a guess I think that some setting is pointing at ..\..\magick\ImageMagick.rc when it should be pointing at ..\magick\ImageMagick.rc, but I don't really know, and have no idea how to change the setting if it exists.
Any help is greatly appreciated
[RESOLVED] Another windows compilation problem
-
- Posts: 20
- Joined: 2012-10-08T13:42:11-07:00
- Authentication code: 67789
[RESOLVED] Another windows compilation problem
Last edited by spongemonkey on 2012-10-11T10:39:57-07:00, edited 1 time in total.
Re: Another windows compilation problem
We have this problem fixed in the 6.8.0-0 Beta release. Try building against http://www.imagemagick.org/download/bet ... windows.7z.
-
- Posts: 20
- Joined: 2012-10-08T13:42:11-07:00
- Authentication code: 67789
Re: Another windows compilation problem
Thanks for the response.
Have just tried the same procedure with the beta source. The first lot of errors is now replaced with errors of the form
error LNK1181: cannot open input file 'CORE_RL_magick_.lib' ..ImageMagick-6.8.0\VisualMagick\utilities\LINK UTIL_composite
plus the other errors.
The file CORE_RL_magick_.lib does exist in the folder ..VisualMagick\lib
Have just tried the same procedure with the beta source. The first lot of errors is now replaced with errors of the form
error LNK1181: cannot open input file 'CORE_RL_magick_.lib' ..ImageMagick-6.8.0\VisualMagick\utilities\LINK UTIL_composite
plus the other errors.
The file CORE_RL_magick_.lib does exist in the folder ..VisualMagick\lib
-
- Posts: 20
- Joined: 2012-10-08T13:42:11-07:00
- Authentication code: 67789
Re: Another windows compilation problem
The 32bit version (of the beta) compiles fine without the utility projects full path options. Still no luck with the 64 version though
Re: Another windows compilation problem
We just built the 64-bit version of ImageMagick 6.8.0-0 beta and it built without complaint. Are you getting a compile error? If so, post the error here so we can figure out why its failing to compile for you.
-
- Posts: 20
- Joined: 2012-10-08T13:42:11-07:00
- Authentication code: 67789
Re: Another windows compilation problem
Build was attempted with configuration as above but without the "Generate all utility projects with full paths..." option.
I don't know what the most useful format to give the errors in is, but here they are splattered into a text file: http://textuploader.com/?p=6&id=sdtdd
I'll just reiterate this is using Visual Studio 2010 in case that is important. Thanks again.
I don't know what the most useful format to give the errors in is, but here they are splattered into a text file: http://textuploader.com/?p=6&id=sdtdd
I'll just reiterate this is using Visual Studio 2010 in case that is important. Thanks again.
Re: Another windows compilation problem
We can reproduce the problem you reported and have a patch. Look for it by sometime tomorrow in the 6.8.0-0 Beta distribution. Also be sure to undef the MAGICKCORE_X11_DELEGATE define in magick/magick-config.h. That should allow the 64-bit version of ImageMagick to build.
-
- Posts: 20
- Joined: 2012-10-08T13:42:11-07:00
- Authentication code: 67789
Re: Another windows compilation problem
It works, fantastic. Thanks a lot.
Next question, how on earth do I mark the thread as solved?
Next question, how on earth do I mark the thread as solved?
- fmw42
- Posts: 25562
- Joined: 2007-07-02T17:14:51-07:00
- Authentication code: 1152
- Location: Sunnyvale, California, USA
Re: Another windows compilation problem
Edit the title of your first post at the top of this topic and put in the word [RESOLVED] at the beginning of the title, then save it