Lars Roland wrote:
Hello Guy,
Guy Harris wrote:
(snip)
Perhaps it should work, but, for me, it's not working. I get a dialog
box with the title
Tethereal.exe: Unable To Locate...
and no text in it when nmake tries to do the "tethereal.exe -G | perl
...".
I don't know what was supposed to come after "Unable To Locate"" -
perhaps it's "DLL".
Hmm, I haven't ever seen this error message. It is also possible that
nmake cannot find tethereal.exe, perl or the perl script? I am just
guessing.
Are you using cygwin's perl or ActiveState's perl Windows port? It may
help to change the PERL variable in config.nmake using the absolute
path to perl.
Note for Glib and GTK+: extract the binary packages and the
development packages into the same directories (one directory for Glib
and another one for GTK).
I did that (it's "C:\ethereal-win32-libs", with GLib extracted into
"C:\ethereal-win32-libs\glib" and GTK+ extracted into
"C:\ethereal-win32-libs\gtk+") - but that directory is *NOT* in my path
setting.
Does it have to be?
No, it doesn't. Tethereal shouldn't need the GTK dlls.
That's true, it doesn't need the GTK dlls, but it needs the GLIB dlls
when I remember this correctly, so that might be the problem here.
One pro for a COMMON_FILES_GNU directory is the small and clean "PATH"
setting. At the moment we have lots of directories in the PATH
variable. This increases the chances that the wrong files are included
or used during the build process.
I would copy all necessary dlls into a "COMMON_FILE_GNU" directory and
add only this to PATH. We can do this as a part of the build process.
It would work in the same way as the creation "gtk2.tmp".
That's almost what I had in mind with the "install" target! Copying all
required DLLs to one directory, where the exe's can run in. (see also
comment below about the naming)
I haven't tested the recent changes of Ulf Lamping yet.
However, I know that the NSIS makefile is not working currently.
Ulf, can you take a look at it? I won't have the time to work on it in
this week.
OOOOPS, simply forgotten that, as I'm usually not calling this target on
my daily builds. I will have look at this topic soon.
Suggestion for an Install target on Win32: Invoke the makefile in the
nsis directory and call the installer. There might be a "silent"
option in nsis available to do the installation automatically.
That's not what I had in mind, but you're right, that's what an
"install" target should really do. So the one I had in mind should
better be named "debug" or "test" or such (is there a common name for
this?), as the name "install" is a bit misleading here.
Regards, ULFL