From: Ulf Lamping
| Olivier Biot wrote:
|
| >From: Ulf Lamping
| >
| >| Well, there are other problems reported: licensing and DLL
| >conflicts.
| >
| >Regarding the licensing issues, this is no longer an issue with the
| >MSVC++ Toolkit 2003 but it was with MSVC.NET since distributing a
| >GPLed program compiled with MSVC.NET requires Microsoft to open up
the
| >source code of some libraries like MSVCRT since this C runtime
library
| >must now be shipped with the binaries (as opposed to earlier
versions
| >of the MSVC++ compiler).
| >
| >
| Sorry, don't get the point, why it's no longer an issue. I don't see
any
| difference regarding this point between the MSVC++ Toolkit 2003 and
| MSVC.NET.
The MSVC++ Tooklit does *not* ship DLL versions of the C runtime
libraries. I have read the license for the MSVC++ toolkit and have
posted my findings on ethereal-dev some months ago. There was no GPL
incompatibility from what I could make of the license file. This
obviously is *not true* for MSVC++.NET.
| >| See Readme.win32 for some details. There are earlier reported
| >problems
| >| that some DLLs
| >| will conflict (e.g. when opening files). Please report, if you
can
| >| compile a completely working Ethereal :-)
| >
| >Did you recompile all depending libraries with MSVC++ Toolkit 2003?
| >
| >
| No, and I really don't want to!
Ulf, that was not a question directed to you :) I removed too much
from the original mail so that was not clear, I agree.
| My personal preference for the long term would be using the cygwin
or
| mingw gcc compiler to be able to compile everything and use win32
native
| libraries, without requiring an X server or such.
I agree, but believe me, if you want to use CygWin to build Ethereal
today, it takes ages (about 1 hour on a P4 running at 2.6GHz with
hyperthreading and half a gigabyte of memory). This slowness is
inherent to cygwin as the shell interprets the commands and then looks
up the different binaries (e.g., test, rm, cd) which often depend on
cygwin shared libraries (which also require their PATH lookup and time
to load etc).
Regards,
Olivier
