Of course there's one, I posted a patch about 1.5 years ago for the formerly Ethereal to successfully compiled with Visual > 6. I have always successfully used this patched Ethereal/Wireshark compiled with VS 2003 and have just checked when compiled with Visual C++ 2005 Express --> No problem if we include the .exe/dll.manifest to the distribution.
I do not understand why this patch was not applied but it's maybe because I do not know glib (or because the macro does not work on VS6/Unices -> not tested on these environments). The "spirit" of the patch is very simple: Do not use glib API for file handling whilst glib is compiled with visual studio 6.
Regards
Laurent
Caution: if you test, DO NOT FORGET to compile "zlib" to ensure RT lib consistency.
-----Message d'origine-----
De : wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] De la part de Ulf Lamping
Envoyé : mercredi 20 décembre 2006 01:51
À : Developer support list for Wireshark
Objet : Re: [Wireshark-dev] Microsoft Visual C Version 6 support isa bitoutdated ...
Gerald Combs wrote:
> Ulf Lamping wrote:
>
>> The biggest hurdle seems to be the different msvcrt.dll (C runtime
>> library) versions for the libs we use, as Gerald already mentioned - I'm
>> still thinking about the possibilities to solve this.
>>
>
> If we need to we can split the packages subdirectory in
> wireshark-win32-libs into packages/msvcrt and packages/msvcr71.
>
Sounds like an approach to it.
I would like to avoid compiling libs "on our own" where possible -
especially compiling GTK/GLib on Win32 "from scratch" doesn't sound like
a task I would really love to work on ;-)
However, if there's no other way ...
Regards, ULFL
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Attachment:
to_compile_with_VS_more_than_6.0_patch
Description: to_compile_with_VS_more_than_6.0_patch
