> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Christian
> Kreibich
> Sent: luned́ 6 giugno 2005 23.33
> To: tcpdump workers
> Subject: Re: [tcpdump-workers] pcap_dump_file & CO
>
>
> Hi Loris,
>
> On Fri, 2005-06-03 at 10:10 -0700, Loris Degioanni wrote:
> > Guy,
> >
> > Guy Harris wrote:
> > >
> > > However, it sounds as if that only applies if the DLL is using a
> > > different version, or different instance, of the C runtime:
> >
> > Yes, but this doesn't solve the problem. You just cannot force the many
> > libpcap users on windows to use a specific runtime, telling them that
> > otherwise some of the API will not work.
>
> I don't understand -- all that is required is that both lib and app
> developers pick the shareable CRT (CRTDLL.LIB/MSVCRT.LIB). Why is that a
> difficult requirement? To put it another way, why would you *not* want
> to use the shareable CRT always, especially with these kinds of issues
> presumably well known in the Windows community?
Personally, I never use CRTDLL.LIB/MSVCRT.LIB, because in this case I'm
forced to distribute my application with tons of DLL (MSVC*.DLL), which are
far bigger than the application itself.
Therefore, I'm always using the standard C library.
Loris is absolutely right: you cannot presume users will always use the
"default" libraries.
Cheers,
fulvio
> Sorry if that's naive; I'm a very un*x type of guy and my Windows
> development experience is limited to a little bit of mingw.
>
> Thanks,
> Christian.
> --
> ________________________________________________________________________
> http://www.cl.cam.ac.uk/~cpk25
> http://www.whoop.org
>
>
> -
> This is the tcpdump-workers list.
> Visit https://lists.sandelman.ca/ to unsubscribe.
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.
