[Insight-users] Re: volview plugin DLL post-build error
(clarification)
Karthik Krishnan
karthik.krishnan at kitware.com
Wed Dec 5 15:18:57 EST 2007
Rex:
If you are moving the plugins onto another machine, please ensure that you
include the C runtime libraries.
They depend on the compiler that you use. For instance with MSVC 71 (or
visual studio 2003), it is : msvcr71.dll and msvcp71.dll (or msvcrtd.dll if
you built in Debug mode).
You can find them somewhere in c:\Program Files\Visual Studio.. Your plugins
will depend on these libraries, so please make sure they are present on the
target machine. You should drop these libraries into the VolView folder.
If this doesn't work, please use DependencyWalker to check the runtime
libraries that your plugins depend on. "http://www.dependencywalker.com/"
Thanks
--
karthik
On 12/5/07, mrcheung at mdanderson.org <mrcheung at mdanderson.org > wrote:
>
>
> Hi,
>
> I found out that if I copy the DLL to the Volview plugin folder on the
> same
> machine that I generated the DLL, volview can see the DLL (despite the
> post-build errors).
>
> Now, if I copy the same DLL to the Volview plugin folder on another
> machine, then the volview cannot see it. I also checked that for the
> Volview running on this second machine can see other plugins fine.
>
> I would appreciate any help. This is problem for me because the plugins
> would not be portable then.
>
> Rex
>
>
>
>
>
>
>
> "Karthik Krishnan"
> <karthik.krishnan at kitware.com> To:
> "
> mrcheung at mdanderson.org" <mrcheung at mdanderson.org>
> cc:
>
> insight-users at itk.org
> 12/05/2007 08:46 AM
>
>
>
> Subject:
> Re:
> [Insight-users] Re: volview plugin DLL post-build error
>
>
>
>
>
>
> On 12/4/07, mrcheung at mdanderson.org <mrcheung at mdanderson.org> wrote:
>
> Hi,
>
> I am testing making volview plugin. I used a plugin already available and
> build it. Got this error, although a DLL file was generated. When I
> manually copy the DLL file generated this way into the Volview Plugin
> folder, the Volview does not seem to see it. Any help is appreciated.
>
> Rex
>
> My Cmake setting:
> Where is the source code: C:\Insight2\InsightApplications
> Where to build the binaries: C:\Insight2\InsightApplications-VSNET
> ITK_Dir: C:\Insight2\insight-vc++
> Volview_Binary_Dir:C:\Insight2\InsightApplications-VSNET\VolviewPlugIns
>
>
> Rex:
>
> The specification of VolView_BINARY_DIR is incorrect. This is supposed to
> refer to the binary directory where VolView.exe is present. This is why
> you
> get an error from the PostBuild copy process. There is no "Plugins"
> directory in InsightApplications. The PostBuild Copy is meant to copy the
> DLL for you to VolV I would suggest that you simply wipe this cache entry
> out. (You can do that by rightclicking on this cache entry and selecting
> Delete).
>
> In any case, VolView should've been able to load the DLL if you dropped it
> into its Plugins folder. Could you please verify if you dropped it in the
> right place as shown below.
>
> VolView.exe
> |
> ---- Plugins/
> |
> ----- vvITKSigmod.dll (should be dropped here).
>
>
> ------ Build started: Project: vvITKSigmoid, Configuration: Debug Win32
> ------
>
> Compiling...
> vvITKSigmoid.cxx
> Linking...
> Creating library Debug\vvITKSigmoid.lib and object
> Debug\vvITKSigmoid.exp
> Performing Post-Build Event...
> Error copying file "/.\Debug/vvITKSigmoid.dll" to
> "C:/Insight2/InsightApplications-VSNET/VolviewPlugIns/.
> \Debug/Plugins/vvITKSigmoid.dll".
> Project : error PRJ0019: A tool returned an error code from "Performing
> Post-Build Event..."
>
> Build log was saved at "file://c:
> \Insight2\InsightApplications-VSNET\VolviewPlugIns\Debug\BuildLog.htm"
> vvITKSigmoid - 1 error(s), 0 warning(s)
>
>
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/insight-users/attachments/20071205/35cff5c3/attachment-0001.htm
More information about the Insight-users
mailing list