Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: [Ethereal-dev] Win32: add test target(s) to the Makefile.nmake

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Ulf Lamping" <ulf.lamping@xxxxxx>
Date: Tue, 13 Apr 2004 14:41:24 +0200
Hi List!

Quite a while ago, I've made a personal makefile (like a wrapper around Makefile.nmake), which solves an issue with the testing of Ethereal.

Currently, after compiling the Ethereal from source, no test environment is available. One must make sure, that all DLL's and other such dependencies are available in the PATH, to start the newly generated Ethereal successfully (and some people reported problems with this), as this might make problems when using together with other GTK apps, like the Gimp.

I've made a personal makefile, which solves this topic, by copying all required files into a directory below the root sourcedir (seperated for GTK1 and GTK2).

So the newly generated Ethereal can be started from that dir, and it will be running without changing the PATH :-)

I'm using this for quite a while now, and it works ok for me. What do other's think of this approach? Should I merge the targets into the current Makefile.nmake?

Regards, ULFL

P.S: I've included my current pn.make to get an idea what it's doing, but it will need a little work to be somewhat more general, e.g. removing the vcvars32 calls, renaming things, ....

_______________________________________________________________________
... and the winner is... WEB.DE FreeMail! - Deutschlands beste E-Mail
ist zum 39. Mal Testsieger (PC Praxis 03/04) http://f.web.de/?mc=021191

Attachment: pn.nmake
Description: Binary data