I was having difficulty running my ImageMagick (6.4.1) application built with Visual Studio 2003 .Net on target machines that had binary (6.4.5) installs. I read that the binaries were built using Visual C++ 7.0 .Net and that is most likely the issue.
Since I don't own Visual C++ 7.0 on the development machine I am lost as what to do next. My target machines do not have development systems.
Would it be possible for me to build installation binaries with my compiler from source?
Are there binaries out there built with different versions of Visual C++ I could download?
Any other solutions?
Thanks.
Target system installations
Re: Target system installations
ImageMagick binaries are built with Visual Studio 2003 so they should be compatible with your application.
Re: Target system installations
I have tried several combinations and yet the
" ... could not be located in the dynamic link library CORE_RL_Magick++.dll"
persists with the supplied examples and my application on a couple of laptops.
Are there any hints on what could cause this message?
" ... could not be located in the dynamic link library CORE_RL_Magick++.dll"
persists with the supplied examples and my application on a couple of laptops.
Are there any hints on what could cause this message?
Re: Target system installations
Launch the button VS workspace in c:\Program Files\ImageMagick-6.4.5-Q16\Magick_Demos. Compile and execute the project. Assuming it works, use the button workspace as a model for your own application.
Re: Target system installations
That is how I started my project and everything went well. I also built some demos that ran well on the development machine and then tried them on the target machine. same problem.
If I understood what could cause the message I could dig deeper. Since its finding the DLL is confusing that it has problems with the entry.
If I understood what could cause the message I could dig deeper. Since its finding the DLL is confusing that it has problems with the entry.
Re: Target system installations
I did not solve the problem, however I was able to get around it by doing the same binary install on all machines and building it locally. I am obviously not happy with the resolution. If anybody out there knows anything about this please share.