CRT files are the MS C runtimes libraries and are installed with MSVC.
You should ensure that your customer has those dlls installed so that
he can uses your plugin. That's why Microsoft provides free MSVC
runtimes installers. mt.exe is part of your MSVC installation and
allows to embed a manifest file in your dll (see Makefile.nmake files
for examples).
AFAIK next major Wireshark release (based on the 1.1.X source code) is
expected around June and should be built with MSVC2008 SP1. While
waiting for it, you can build your own installer. Once it is released,
you should be able to copy the dll in the official plugins directory.
Pascal.
2009/1/30 <gogrady@xxxxxxxxx>:
> Ahh alright. Well if wireshark is going towards MSVC2008, then I might as well use that. I don't understand what these CRT dlls are and where I put them though. Also, whats the mt.exe? Do i need to send out these CRT dll's if everyone at the company has 2008? Also, do you think my best bet for compatibility is to use the 1.1.* source and MSVC2008 to build my plugin, then create an installer of my wireshark build to use until the stable releases are in the 1.1.* where my plugin .dll and manifest files should just be able to be copy pasted into the stable version?
>
> Thanks for all your help,
>
> Greg
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Pascal Quantin
> Sent: Friday, January 30, 2009 10:35 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] MSVC variant problem in v1.0.5
>
> So far, 1.0.X versions are built with MSVC6 and 1.1.X are built with MSVC2008. You have 2 solutions:
> - build 2 versions of your plugin
> - try to build your custom plugin with MSVC2008 and ensure you embed the manifest and distribute the CRT dlls with it. It should work (there is already an ongoing discussion on this topic on the mailing
> list: http://www.wireshark.org/lists/wireshark-dev/200901/msg00155.html)
>
> Pascal.
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
