From: Andrew Feren
|
| From: Biot Olivier
|
| > |From: Andrew Feren
| > |
| > |It's been a while and I'm in the process of setting up a
| > |Windows build again. I am getting a couple of problems I
| > |don't recall having before.
| > |
| > |nmake (Version 1.50) is complaining about the following rule
| > |(line 23 of the top level Makefile.nmake).
| >
| > Mmh... I strongly suspect you're trying to build Ethrereal with
the
| recently
| > released MSVC++ 2003 Toolkit and an old nmake found on the
Microsoft
| support
| > site. I have to disappoint you: this won't work (I have tried it).
|
| Good instincts and bummer!
It looked too familiar to me :)
| Out of curiousity, was the problem just nmake or did you have
problems
| compiling too? Or did you never get past the nmake problem?
After some editing of the Makefile.nmake files I got compilation to
work. Compiling was OK, but the final linkage failed. It seems that
the root cause is MSVCRT which is dynamically linked with the
depending libraries that we don't build with Ethereal (like zlib,
Gtk+, GLib etc) while the MSVC++ Toolkit only provides a statical C
Runtime library.
However, there seems to be a non-technical reason why we can't use
MSVC++ 7: the C Runtime library (MSVCRT70.dll) must not be used
together with GPLed code (MS does probably not want to disclose the
source code of MSVCRT70).
| > You really need MSVC++ 6 (definitely not a more recent version,
because of
| > mainly licensing reasons).
|
| Yeah saw that in one of the README files. Oh well. It seemed
promising at
| the time.
The problem with statically linking the CRT library is that you might
encounter memory problems as the program does not expect different
CRT's in it.
Regards,
Olivier
